-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Another numbers-as-strings error #56
Labels
Comments
Hey, fixed this for all queries / filters json. |
fix confirmed++ |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Library stax-api is added twice in final ZIP file. It's due to the dependency tree. ``` [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ elasticsearch-cloud-azure --- [INFO] org.elasticsearch:elasticsearch-cloud-azure:jar:2.5.2-SNAPSHOT [INFO] +- org.hamcrest:hamcrest-core:jar:1.3.RC2:test [INFO] +- org.hamcrest:hamcrest-library:jar:1.3.RC2:test [INFO] +- com.carrotsearch.randomizedtesting:randomizedtesting-runner:jar:2.1.10:test [INFO] | \- junit:junit:jar:4.10:test [INFO] +- org.apache.lucene:lucene-test-framework:jar:4.10.2:test [INFO] | +- org.apache.lucene:lucene-codecs:jar:4.10.2:test [INFO] | +- org.apache.lucene:lucene-core:jar:4.10.2:compile [INFO] | +- com.carrotsearch.randomizedtesting:junit4-ant:jar:2.1.6:test [INFO] | \- org.apache.ant:ant:jar:1.8.2:test [INFO] +- org.elasticsearch:elasticsearch:jar:1.4.2:compile [INFO] | +- org.apache.lucene:lucene-analyzers-common:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-queries:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-memory:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-highlighter:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-queryparser:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-sandbox:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-suggest:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-misc:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-join:jar:4.10.2:compile [INFO] | +- org.apache.lucene:lucene-grouping:jar:4.10.2:compile [INFO] | \- org.apache.lucene:lucene-spatial:jar:4.10.2:compile [INFO] | \- com.spatial4j:spatial4j:jar:0.4.1:compile [INFO] +- com.microsoft.windowsazure:microsoft-windowsazure-api:jar:0.4.6:compile [INFO] | +- com.sun.jersey:jersey-client:jar:1.13:compile [INFO] | | \- com.sun.jersey:jersey-core:jar:1.13:compile [INFO] | +- javax.inject:javax.inject:jar:1:compile [INFO] | +- com.sun.jersey:jersey-json:jar:1.13:compile [INFO] | | +- org.codehaus.jettison:jettison:jar:1.1:compile [INFO] | | | \- stax:stax-api:jar:1.0.1:compile [INFO] | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile [INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile [INFO] | | | \- javax.xml.stream:stax-api:jar:1.0-2:compile [INFO] | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.2:compile [INFO] | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.2:compile [INFO] | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.2:compile [INFO] | | \- org.codehaus.jackson:jackson-xc:jar:1.9.2:compile [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile [INFO] | +- javax.mail:mail:jar:1.4.5:compile [INFO] | | \- javax.activation:activation:jar:1.1:compile [INFO] | \- org.apache.commons:commons-lang3:jar:3.1:compile [INFO] +- log4j:log4j:jar:1.2.17:compile [INFO] \- org.elasticsearch:elasticsearch:test-jar:tests:1.4.2:test ``` We should exclude `javax.xml.stream:stax-api:jar:1.0-2:compile` from `com.microsoft.windowsazure:microsoft-windowsazure-api:jar:0.4.6:compile` Closes #56. (cherry picked from commit 68efe93) (cherry picked from commit 68f25d1)
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
Closes elastic#56.
StefanGor
pushed a commit
to StefanGor/elasticsearch
that referenced
this issue
Mar 17, 2017
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
May 24, 2018
Faulty nodes cease to be faulty when a cluster state is published in which they have been removed. However, today, a faulty node may learn it is considered to be faulty and send another join request to the master before its removal can be published. In this case, the next publication will not remove it and so its faultiness persists for longer than expected. This change fixes this by removing joining nodes from the known-faulty set.
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Restart on Change, Cleanup + better restart
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we introduce the track parameter `query_index_prefix` which determines the prefix of indices which are used in query benchmarks and set its default to the former value `elasticlogs_q`. Relates elastic#56
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
Update elasticsearch-benchmarks.elastic.co overview page to detail the switch to `always` for THP enabled/defrag Linux kernel settings. Also update the history of changes for the kernel security updates. Relates elastic#56
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hiya
Returns:
The text was updated successfully, but these errors were encountered: