ESQL: Fix extent reading when missing#140034
Conversation
Fixes a bug while reading spatial extents when the leaf doesn't contain any documents with a shape. These have a `null` `BinaryDocValues` and we can just read them as entirely `null` values like other readers.
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
|
Hi @nik9000, I've created a changelog YAML for you. |
|
Thanks @GalLalouche. |
Fixes a bug while reading spatial extents when the leaf doesn't contain any documents with a shape. These have a `null` `BinaryDocValues` and we can just read them as entirely `null` values like other readers.
💚 Backport successful
|
Fixes a bug while reading spatial extents when the leaf doesn't contain any documents with a shape. These have a `null` `BinaryDocValues` and we can just read them as entirely `null` values like other readers.
|
Thanks @nik9000 ! |
|
Wow! Thanks Nik. Mouhcine and I were also fixing this yesterday, but did not have failing tests in place before you got this done. I now have a failing integration test which this will also fix, and I'll make that PR a test-only PR now since the fix is already merged. |
This test also fails when the indexes have 16 shards before the fix at elastic#140034
This test also fails when the indexes have 16 shards before the fix at elastic#140034
|
Sorry for jumping on this without checking the assignees! Old habit back when we weren't piling on the test failures at the same time. I'll be more careful. |
…stic#140057) This test also fails when the indexes have 16 shards before the fix at elastic#140034
Fixes a bug while reading spatial extents when the leaf doesn't contain any documents with a shape. These have a
nullBinaryDocValuesand we can just read them as entirelynullvalues like other readers.