-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
String based parser: Non-latin characters are not supported in field names. #4467
Comments
➤ Jørgen Edelbo commented: [~james.stone] I don't think this was ever supported? |
➤ James Stone commented: This was not supported by the PEGTL implementation, so it is a new feature request. [~clemente.tort] does that information impact the priority of this ticket? |
There is a very clear and easy workaround, and as this hasn't been supported for other SDK's I would consider this very low priority. |
I strongly disagree. This is a pretty severe breaking change for Java. We have many users which use local languages in their model classes like Chinese. This worked out of the box when using the Core API's directly which was what we did in the old query API, but we replaced all of the internal representation with the String parser. |
Ahh sorry. I had missed that you migrated the existing typed queries to the new parser as well! Yeah, then I agree. |
The new query parser crashes when field names with non-latin characters are used.
Example
델타 = $0
Stacktrace
The text was updated successfully, but these errors were encountered: