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

SQL: Selecting qualified nested field throws NPE #30054

Closed
elasticmachine opened this issue Feb 5, 2018 · 4 comments
Closed

SQL: Selecting qualified nested field throws NPE #30054

elasticmachine opened this issue Feb 5, 2018 · 4 comments
Labels

Comments

@elasticmachine
Copy link
Collaborator

Original comment by @bpintea:

The following statment:
"SELECT dep.dep_id FROM test_emp"
will lead to a NPE.
"SELECT dep.* FROM test_emp" will work, though.

@elasticmachine
Copy link
Collaborator Author

Original comment by @bpintea:

Stacktrace attached: LINK REDACTED

@elasticmachine
Copy link
Collaborator Author

Original comment by @costin:

The bug has been reported to @martijnvg who confirmed it seems to be a bug in ES rather than the query itself.

@elasticmachine
Copy link
Collaborator Author

Original comment by @bpintea:

Sanitizing picked this issue up: is there a peer issue to track the defect in ES?

@astefan
Copy link
Contributor

astefan commented Oct 29, 2018

This one doesn't reproduce anymore. Most likely, fixed by the PR referenced in #32941. CC @bpintea

@astefan astefan closed this as completed Oct 29, 2018
astefan added a commit that referenced this issue Oct 30, 2018
Added a test for a bug in Elasticsearch (#32941) that had implications in SQL and activated another test that didn't work in the past
astefan added a commit that referenced this issue Oct 30, 2018
Added a test for a bug in Elasticsearch (#32941) that had implications in SQL and activated another test that didn't work in the past
astefan added a commit that referenced this issue Oct 30, 2018
Added a test for a bug in Elasticsearch (#32941) that had implications in SQL and activated another test that didn't work in the past
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants