In the interests of placing an upper bound on the length of the primary key used for longitudinal analysis, it may be better to use a hash of the raw clientId instead of the clientId itself. I filed this bug because I noticed a few crash submissions with the following: "clientId":"593836 8c-ddc6-4cfa-91b2-24614767c823" With all kinds of extra spaces. Is the tradeoff in complexity and indirection worthwhile?
As discussed in today's triage, it would be better to validate that the client is sending well-formed UUIDs for the "clientId" field and then non-UUID values to the error stream on the server.
Based on the discussion, should we close this as invalid?
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.