Boolean Type: Support also cases when a number/string value are passed #33
Labels
Comments
|
Boolean Type: Support also cases when a number/string value are passed, closed by 4806df4. |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Closes #33. (cherry picked from commit fd508b8)
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Closes #33. (cherry picked from commit bc45a89)
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
We need to simplify a bit our tests. Also, we need to mark as `@Ignore` tests as they break now due to some cluster controls after each test in elasticsearch test infra. See [org.elasticsearch.test.ElasticsearchIntegrationTest#ensureClusterSizeConsistency()](https://github.com/elasticsearch/elasticsearch/blob/v1.3.1/src/test/java/org/elasticsearch/test/ElasticsearchIntegrationTest.java#L974-L979) Closes #33.
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
Apr 24, 2018
A soak test run yielded some failures: - The randomly-drop-messages mechanism also dropped messages-to-self. If a publication succeeds but the `ApplyCommit` that the master sends itself is lost then it gets stuck. - Messages-to-self were always scheduled to happen after the current message handler, whereas in the actual system a message-to-self may be handled inline. - It was possible to deliver messages to the ghost of a rebooted node, which resurrected it and caused confusion. Also the `HeartbeatScheduler` was started in its constructor rather than with a separate `start()` method. This change fixes these issues.
|
not working es 6.1 |
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Add retry to ensure service is reachable
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we force-merge the index that is used in the frozen challenge to a single segment. We also set the refresh interval to its default value to ensure an optimization in Elasticsearch can kick in that disables refreshes if no searches are performed. This should improve indexing speed a bit (we don't care about indexing speed in that challenge as this only there to generate a decently sized corpus for the query benchmark). Relates elastic#33
|
Not working in ES v7.10, also in v7.11 |
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we embed Kibana dashboards for nightly and release benchmarks. As we want to gather further feedback we did not yet remove the old functionality based on dygraphs (this will happen in elastic#33). Closes elastic#23 Closes elastic#9 Closes elastic#11 Closes elastic#12
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
stu-elastic
pushed a commit
to stu-elastic/elasticsearch
that referenced
this issue
Nov 2, 2023
…n_test Parse messages in APMIT
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even though there is an explicit boolean type in JSON, support also cases when a number or string are passed. 0 meaning false, any other meaning true. "false" string meaning false, any other string meaning true.
Note, the boolean type will have to be explicitly defined, otherwise, a number will be defined as a number, and a string as a string.
The text was updated successfully, but these errors were encountered: