Query: support negative queries #44
Labels
Comments
|
Query: support negative queries, closed by e0c3bb5. |
|
The current support for negative queries is only working for very simple use cases, but not for all possible queries containing possible negative subqueries. As an example, see:
Currently we preprocess the query before sending it to ES, by changing it to something like Apart from the examples above, I would reopen this issue, but since I do not have permission :-) |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
We don't have to explicitly define `commons-codec` in our assembly file.
When removing it, the content is still exactly the same:
```
Archive: target/releases/elasticsearch-analysis-phonetic-2.4.4-SNAPSHOT.zip
Length Date Time Name
-------- ---- ---- ----
17193 05-07-15 09:08 elasticsearch-analysis-phonetic-2.4.4-SNAPSHOT.jar
23098 03-17-15 00:28 lucene-analyzers-phonetic-4.10.4.jar
263965 11-09-14 14:02 commons-codec-1.9.jar
-------- -------
304256 3 files
```
See https://github.com/elastic/elasticsearch-analysis-phonetic/issues/40
Closes #44.
(cherry picked from commit 6fa3fb8)
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
Based on PR elastic#45, we add a new language detection option using Language detection feature available in Tika: https://tika.apache.org/1.4/detection.html#Language_Detection By default, language detection is disabled (`false`) as it could come with a cost. This default value can be changed by setting the `index.mapping.attachment.detect_language` setting. It can also be provided on a per document indexed using the `_detect_language` parameter. Closes elastic#45. Closes elastic#44.
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we use the correct property `index` in the `bulk-update` challenge instead of the outdated property name `index_name`. This is a leftover from elastic#36 Relates elastic#44
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we get one step closer to removing the challenges "append-no-conflicts-index-only-1-replica" by using track parameters. Relates elastic#44
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow negative queries such as all the documents that do not match something. This can be expressed by a boolean query with a mustNot clause or in the query string.
The text was updated successfully, but these errors were encountered: