|
Ah I forgot about that, thought that the regex was a special case within EqualityMatchExpression. Agreed there's nothing extra needed and closing this ticket.
|
|
That will be parsed as a RegexMatchExpression not as an EqualityMatchExpression. I agree that we cannot support this predicate if ssn is encrypted, but I don't think we will have to special-case an EqualityMatchExpression which is checking equality against a regex. Does that make sense?
|
|
david.storch How could we answer a regex equality on an encrypted field? I was thinking something like
db.coll.find({ssn: /^1234/})
|
where 'ssn' is an encrypted string. Or are you referring to a different query?
|
|
nicholas.zolnierz, on what basis will this be disallowed? We have to ban $in with a regex, but I don't think we need to ban $eq with a regex, right?
|
Generated at Thu Feb 08 04:51:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.