Fixed
Status Update
No update yet.
Comments
rb...@google.com
Sorry for pinging, but jcenter seems to be causing issues again today for many developers.
[Deleted User] <[Deleted User]>
UAST and intellij-core are licensed under the Apache license which made this easy; trove4j on the other hand is LGPL which makes me more nervous about just repackaging; I'd need to have somebody review what the rules and implications are.
js...@google.com
As an alternative to repackaging could you ask Jetbrains to push trove4j to maven central? I don't know the reasoning for why it isn't on there but maybe that's easier.
Description
index.search('my_field < "2"')
Where my_field is an IntegerField, if I have 2 documents indexed, one with my_field=1 and one with my_field=3, this only returns the first.
But in local dev with SDK >= 1.9.22 this throws an error:
InvalidRequest: Unable to compare "my_field" with "2"
I appreciate inequalities are only designed to work with numbers and dates, but the production implementation clearly coerces "2" to a number before comparing, while the search stub in the SDK does not. They should be consistent where possible.
The stub matches production behaviour if numbers are left unquoted.
Some digging shows that this is caused by recent changes to `_CheckMatch` in google/appengine/api/search/stub/document_matcher.py, specifically the attempted coercion to `float()` on L503, which doesn’t allow for quoted values.