-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
SQL API VerificationException when index contains rank_feature or rank_features field mapping #44320
Comments
Relates: elastic/elasticsearch#44320 This commit skips the SQL integration tests for the moment. (cherry picked from commit 2490f71)
Relates: elastic/elasticsearch#44320 This commit skips the SQL integration tests for the moment.
Pinging @elastic/es-search |
Fails on master as well. The culprit is the output of |
The Elasticsearch issue was fixed. Closing this one, as a consequence. |
Relates: elastic/elasticsearch#44320 This commit skips the SQL integration tests for the moment. (cherry picked from commit 2490f71)
Relates: elastic/elasticsearch#44320 This commit skips the SQL integration tests for the moment. (cherry picked from commit 2490f71)
Did this make it into |
@codebrain judging by the commit it ended up on 7.3 branch. And by the version labels on the PR itself it should have been included in 7.3.0. |
Elasticsearch version (
bin/elasticsearch --version
):Version: 7.2.0, Build: default/zip/508c38a/2019-06-20T15:54:18.811730Z, JVM: 12.0.1
But tested against 7.0.0, 7.1.0 and 7.2.0
Plugins installed: []
JVM version (
java -version
):java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
OS version (
uname -a
if on a Unix-like system):Windows 10 Professional 64 Bit
Description of the problem including expected versus actual behavior:
When an index contains a
rank_feature
orrank_features
field mapping, and a SQL query is executed using the SQL REST API, the request fails with a 400 Bad Request responseSteps to reproduce:
rank_feature
orrank_features
field mappingproject
index and recreate, this time including arank_feature
orrank_features
field mappingProvide logs (if relevant):
The Elasticsearch logs indicate that the issue may be in the field_caps API call that SQL uses
The text was updated successfully, but these errors were encountered: