-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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: _id field made available as column to drivers #39739
Comments
Pinging @elastic/es-search |
I think this one is a duplicate of #39738. |
I'm investigating. |
Additional clarification: the issue in original interpretation (=as the field being listed) is still there. But the error returned when selecting the fields is now different ( |
@bpintea the second error message is correct, that's how it's supposed to happen imo. But, after this PR we will display one value and not issue an error message anymore, for drivers. Regarding the |
@astefan Sounds good. I'm, fine with having this issue closed then. |
@astefan With a fresh build, for:
I now get back an(other) error:
and stacktrace:
|
Hm, this seems to happen for |
This seems to be a separate issue, so I created #40296. Closing this one. |
If a mapping defines an
_id
[sub]field, this is returned inSYS COLUMNS
.When querying this field however, an error is returned.
Example: Kibana's "ecommerce" sample data mapping sample:
being listed as
and triggering the exception on query:
The text was updated successfully, but these errors were encountered: