-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
JSON object properties are not positional #27
Comments
In all the places where JSON is handled, location is not relevant. This problem is not actually related to the location of the filter and the query (there is support for placing them where you want) but with the fact the range query did not behaved correctly when used as inner query. I pushed a fix for it, can you give it a go? |
Perfect! that works - thanks |
Great, closing. |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Works also with Elasticsearch 0.90.0. Closes #27.
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Closes #27. (cherry picked from commit 5effcce)
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Closes #27. (cherry picked from commit d43d4df)
johtani
added a commit
that referenced
this issue
Jun 5, 2015
Included ICUNormalizer2Charfilter in Lucene 4.8.0. Add CharFilterFactory. Now, char_filter name is "icu_normalizer", however token_filter name is same name. Closes #27. (cherry picked from commit 0cbf1b3)
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
According to [Containers naming guide](http://msdn.microsoft.com/en-us/library/dd135715.aspx): > A container name must be a valid DNS name, conforming to the following naming rules: > > * Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character. > * Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted in container names. > * All letters in a container name must be lowercase. > * Container names must be from 3 through 63 characters long. We need to fix the documentation and control that before calling Azure API. The validation will come with issue #27. Closes #21. (cherry picked from commit 6531165)
dadoonet
added a commit
that referenced
this issue
Jun 9, 2015
Closes #27. (cherry picked from commit 1eb2352)
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
Apr 24, 2018
Miscellaneous fixes/clarifications to log messages that arose in tracking down elastic#26.
rjernst
pushed a commit
that referenced
this issue
Apr 24, 2018
A few files had their first comment removed even though it did not contain a license. This re-adds those comments.
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Add tests for new feature
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
Add index sorting challenges to nightly Closes elastic#27
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hiya
It looks like you are parsing JSON as a stream, where position matters, instead of parsing the whole objects before analysing them. For instance, this works:
But this fails:
curl -XGET 'http://127.0.0.2:9200/_all/_search' -d '
{ query:
{
"filteredQuery" : {
"filter" : {
"range" : {
"num" : {
"to" : 20,
"from" : 10
}
}
},
"query" : {
"term" : {
"text" : "foo"
}
}
}
}
}
'
A JSON parser should consider these two structures to be identical, which is also the thing that rules out having non-unique property names.
thanks
Clint
(Edited to correct JSON)
The text was updated successfully, but these errors were encountered: