-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
catalog: add Index.InvertedColumnKeyType #75427
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @RaduBerinde and @rytaft)
pkg/sql/catalog/table_elements.go, line 157 at r1 (raw file):
// InvertedColumnID returns the ColumnID of the inverted column of the // inverted index. InvertedColumnID() descpb.ColumnID
Comment about the panic if it's not an inverted index
pkg/sql/catalog/table_elements.go, line 161 at r1 (raw file):
// InvertedColumnName returns the name of the inverted column of the inverted // index. InvertedColumnName() string
Comment about the panic if it's not an inverted index
pkg/sql/catalog/table_elements.go, line 165 at r1 (raw file):
// InvertedColumnKeyType returns the type of the data element that is encoded // as the inverted index key. This is currently always Bytes. InvertedColumnKeyType() *types.T
Comment about the panic if it's not an inverted index
rebase to fix the flake |
In an inverted index, the encoded key is treated as a Bytes datum. This is currently hardcoded in the opt catalog. This commit moves this into the index descriptor. Release note: None
948765b
to
dee8e2b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TFTR!
Reviewable status: complete! 0 of 0 LGTMs obtained (and 1 stale) (waiting on @ajwerner and @rytaft)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TFTR!
Reviewable status: complete! 0 of 0 LGTMs obtained (and 1 stale) (waiting on @ajwerner and @rytaft)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 3 of 4 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (and 1 stale) (waiting on @RaduBerinde)
TFTRs! bors r+ |
Build failed (retrying...): |
Build succeeded: |
In an inverted index, the encoded key is treated as a Bytes datum.
This is currently hardcoded in the opt catalog.
This commit moves this into the index descriptor.
Release note: None