Skip to content
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

Query DSL: queryString - allow to escape the string #41

Closed
kimchy opened this issue Feb 24, 2010 · 5 comments
Closed

Query DSL: queryString - allow to escape the string #41

kimchy opened this issue Feb 24, 2010 · 5 comments

Comments

@kimchy
Copy link
Member

kimchy commented Feb 24, 2010

Add an option to the queryString DSL to escape the query string, which should be turned off by default.

@kimchy
Copy link
Member Author

kimchy commented Feb 24, 2010

Query DSL: queryString - allow to escape the string (should be on by default), closed by c7389df.

@clintongormley
Copy link

Could you give an example of how and why you would use escape?

ta

@kimchy
Copy link
Member Author

kimchy commented Mar 2, 2010

actually, the only reason is when knowing you are not going to use any reserve query parser keywords. Its not that common to enable escaping, I just added it as an option.

@clintongormley
Copy link

and it is used as {...., escape: true } ?

@kimchy
Copy link
Member Author

kimchy commented Mar 2, 2010

Yep. or escape : 1 :)

dadoonet added a commit that referenced this issue Jun 5, 2015
Due to this [change](#8018), we need to fix our tests for elasticsearch 1.4.0 and above.

Closes #41.

(cherry picked from commit 75b800f)
dadoonet added a commit that referenced this issue Jun 5, 2015
The UnicastHostsProvider implementation creates DiscoveryNodes that are used as an initial seed for unicast based discovery. At the moment it uses Version.CURRENT for those DiscoveryNode object, which confuses the backwards compatibility layer to think this nodes are of the latest version. This causes new nodes to fail to join old nodes as the ping serialization goes wrong. Instead we should use version.minimumCompatibilityVersion().

Closes #41.

(cherry picked from commit 9ae29c7)
dadoonet added a commit that referenced this issue Jun 5, 2015
…galStateException` in favor of the JDK one

Related to #10794

Closes #41.
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
This is due to `edu.ucar:netcdf` lib which comes from `tika-parsers` dependency.

```
[INFO] +- org.apache.tika:tika-parsers:jar:1.5:compile
[INFO] |  +- edu.ucar:netcdf:jar:4.2-min:compile
[INFO] |  |  \- org.slf4j:slf4j-api:jar:1.5.6:compile
```

We can exclude this library from the generated ZIP artifact.

Closes elastic#41.
njlawton pushed a commit to njlawton/elasticsearch that referenced this issue Mar 15, 2017
Update Coordination.md misspelling my group name
ywelsch added a commit to ywelsch/elasticsearch that referenced this issue Jun 4, 2018
This commit moves Legislator from the simplified fake master service interface to use the actual MasterService implementation to submit and execute cluster state update tasks, supporting batching, listeners etc. The commit also reuses the task implementations from Zen1 by making direct reuse of NodeJoinController.JoinTaskExecutor an ZenDiscovery.NodeRemovalClusterStateTaskExecutor, eliminating the code duplication of an earlier commit.
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we remove some unused parameter sources from the eventdata
track and also cleanup unused imports.

Relates elastic#41
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…lastic#41)

* Add admin-portal to Engageli AMI

Copy admin-portal build artifact from s3 into Engageli AMI.

Install admin-portal into student app sandbox at boot time via rc.local

Add admin-portal to list of repos to tag

Approved-by: Ofri Peretz
Approved-by: Matan Yemini
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
Projects
None yet
Development

No branches or pull requests

2 participants