uppercase first letter in property name breaks "_all" queries #178
Comments
|
Ouch!. Found the problem, the case only relates to the internal ordering of the fields in Lucene... . Will push a fix later today. |
|
Nice, that was fast! :-) |
|
uppercase first letter in property name breaks "_all" queries, closed by 23d2799. |
dadoonet
pushed a commit
that referenced
this issue
Jun 5, 2015
Based on PR #178 by @paul-e-cooley. Thanks Paul! In addition to: ```yaml cloud: aws: protocol: https proxy_host: proxy1.company.com proxy_port: 8083 ``` You can also set different proxies for `ec2` and `s3`: ```yaml cloud: aws: s3: proxy_host: proxy1.company.com proxy_port: 8083 ec2: proxy_host: proxy2.company.com proxy_port: 8083 ``` PR rebased on master and lastest changes about component settings removal. Documentation added. Changes in tests. If a proxy is provided we run the tests, otherwise we ignore the test. Closes #177.
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
We are moving back release scripts locally as it's the last repository which is not in elasticsearch repo. Also, we now use generated checksums when we run the `install` phase and we upload them to S3 at the same time we upload the artifact itself. Closes elastic#178. (cherry picked from commit d3324bc) (cherry picked from commit 311a80b) (cherry picked from commit bf898b7)
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
Add Vladimir * add myself to devops repo * Merge branch 'master' into dev/vladimir/add-vladimir * resolve merge conflict * ttang2 ip address changed * add a subnet Approved-by: Can Yildiz
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using an uppercase letter first in a property name breaks queries against the "_all"-field.
For example, the code below doesn't match anything:
curl -XPUT http://localhost:9200/sff/vehicle/1 -d '
{
"make": "Jeep",
"MODEL": "Jeep"
}'
But doing the following works:
curl -XPUT http://localhost:9200/sff/vehicle/1 -d '
{
"make": "Jeep",
"model": "Jeep"
}'
The problem seems to be that the created mapping uses the property name (MODEL in this case) as "index_name". Manually creating a mapping with property name "MODEL" and "index_name" as "model" works. Using "mODEL" also works.
I'm using version v0.7.0.
The text was updated successfully, but these errors were encountered: