Skip to content

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Oct 8, 2024

The doc values don't preserve nulls in a list so ESQL doesn't either.

Closes #114324

The doc values don't preserve `null`s in a list so ESQL doesn't either.
Copy link
Contributor

github-actions bot commented Oct 8, 2024

Documentation preview:

@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) labels Oct 8, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@nik9000 nik9000 added auto-backport Automatically create backport pull requests when merged auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) and removed auto-backport Automatically create backport pull requests when merged labels Oct 8, 2024
@elasticsearchmachine elasticsearchmachine merged commit f633148 into elastic:main Oct 8, 2024
6 checks passed
@nik9000 nik9000 deleted the esql_no_null_storage_doc branch October 8, 2024 16:18
@nik9000 nik9000 added the auto-backport Automatically create backport pull requests when merged label Oct 8, 2024
nik9000 added a commit to nik9000/elasticsearch that referenced this pull request Oct 8, 2024
The doc values don't preserve `null`s in a list so ESQL doesn't either.

Closes elastic#114324
nik9000 added a commit to nik9000/elasticsearch that referenced this pull request Oct 8, 2024
The doc values don't preserve `null`s in a list so ESQL doesn't either.

Closes elastic#114324
@nik9000
Copy link
Member Author

nik9000 commented Oct 8, 2024

Backporting with #114339 and #114338

@nik9000
Copy link
Member Author

nik9000 commented Oct 8, 2024

I screwed up the tags on this one - I mean to use the backporting tag not the auto-merge-without-approval tag. But I got confused. I manually backported. I don't think it's a big deal to have auto-merged, but that wasn't my intention. But I think it's fine. We can modify in a follow up if we feel the need.

elasticsearchmachine pushed a commit that referenced this pull request Oct 8, 2024
The doc values don't preserve `null`s in a list so ESQL doesn't either.

Closes #114324
elasticsearchmachine pushed a commit that referenced this pull request Oct 8, 2024
* Docs: ESQL doesn't preserve `null`s in a list (#114335)

The doc values don't preserve `null`s in a list so ESQL doesn't either.

Closes #114324

* Update
matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this pull request Oct 10, 2024
The doc values don't preserve `null`s in a list so ESQL doesn't either.

Closes elastic#114324
davidkyle pushed a commit to davidkyle/elasticsearch that referenced this pull request Oct 13, 2024
The doc values don't preserve `null`s in a list so ESQL doesn't either.

Closes elastic#114324
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL auto-backport Automatically create backport pull requests when merged auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) >docs General docs changes Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Docs Meta label for docs team v8.15.3 v8.16.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

null values stripped out from docvalues and ES|QL

2 participants