-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
78295: sql: use IndexFetchSpec for zigzag join r=RaduBerinde a=RaduBerinde #### rowexec: follow-up cleanup for EncodedKey in zigzagjoiner The zig-zag joiner code still uses `Bytes` instead of `EncodedKey` for the encoded key. This works because the fixed values are encoded using VALUE encoding, and the value encodings are the same for `DBytes` and `DEncodedKey`. This commit updates the zigzag joiner to use the correct `EncodedKey` type. The code no longer needs to special case inverted indexes - with the addition of support for `EncodedKey` in `keyside.Encode`, the general code path can now be used. Release note: None #### sql: clean up ZigZagJoinerSpec This change cleans up the zig-zag joiner spec: we move the per-side information into a Side sub-message and use a list of Sides instead of many parallel lists. Other misc cleanup in the zigzag joiner code is included. Release note: None #### sql: use IndexFetchSpec for zigzag join This commit changes the zigzag joiner to use IndexFetchSpec for the two sides instead of table and index descriptors. The internal schema of the zigzag joiner is changed to match the fetched columns, simplifying the execution code. This change necessitates fixes on the planning side - we weren't determining the necessary scan columns correctly (this wasn't a problem when the internal schema had all table columns and we were relying on the execution layer to figure out what is needed). Release note: None Co-authored-by: Radu Berinde <[email protected]>
- Loading branch information
Showing
28 changed files
with
764 additions
and
933 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.