Closed
Description
We are using ascii_lowercase and string.digits for the scan_id field right now, which does provide us a lot of options but since it's random we have potential to generate collisions. The reason it's only using string. ascii_lowercase + string.digits is because elasticsearch is filtering that token as lowercase. In order to allow scan_id to be case sensitive, we would need to implement a custom elasticsearch filter for scan_id such that it doesn't lowercase all the characters. Then we can add string.ascii_uppercase to our ID character set.
If this can be done entirely programmatically then I'll do it. Otherwise nah.