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

Remove explicit type definition in percolator queries #13

Closed
danielmitterdorfer opened this issue Feb 9, 2017 · 0 comments
Closed

Remove explicit type definition in percolator queries #13

danielmitterdorfer opened this issue Feb 9, 2017 · 0 comments

Comments

@danielmitterdorfer
Copy link
Member

The type definition on match queries has been deprecated in Elasticsearch 6:

[2017-02-09T14:35:27,735][WARN ][o.e.d.c.ParseField       ] Deprecated field [type] used, replaced by [match_phrase and match_phrase_prefix query]

The cause of these deprecation warnings are percolator queries like these:

{
   "query": {
      "match": {
         "body": {
            "query": "yard bushes",
            "type": "boolean"
         }
      }
   }
}

We need to remove the type from all queries and will provide a new data file.

danielmitterdorfer added a commit that referenced this issue Feb 10, 2017
With this commit we switch to a new percolator corpus that contains
queries that do not define an explicit `type` in match queries
(which is deprecated with Elasticsearch 6.0 and is harmless to
remove for earlier versions).

Closes #13
danielmitterdorfer added a commit that referenced this issue Feb 10, 2017
With this commit we switch to a new percolator corpus that contains
queries that do not define an explicit `type` in match queries
(which is deprecated with Elasticsearch 6.0 and is harmless to
remove for earlier versions).

Closes #13
danielmitterdorfer added a commit that referenced this issue Feb 10, 2017
With this commit we switch to a new percolator corpus that contains
queries that do not define an explicit `type` in match queries
(which is deprecated with Elasticsearch 6.0 and is harmless to
remove for earlier versions).

Closes #13
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

1 participant