-
Notifications
You must be signed in to change notification settings - Fork 216
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
feat(planner): match vector indexes #874
base: main
Are you sure you want to change the base?
Conversation
e2a0a9e
to
bf8b849
Compare
Signed-off-by: Alex Chi <[email protected]>
bf8b849
to
8b422e3
Compare
Signed-off-by: Alex Chi <[email protected]>
Co-authored-by: Runji Wang <[email protected]> Signed-off-by: Alex Chi Z. <[email protected]>
Co-authored-by: Runji Wang <[email protected]> Signed-off-by: Alex Chi Z. <[email protected]>
Co-authored-by: Runji Wang <[email protected]> Signed-off-by: Alex Chi Z. <[email protected]>
Actually, vector index scan is different from index scan. The vector index scan operator has an However, I just realized that the op type can be inferred from the index type stored so we can remove it and make it generic. |
Signed-off-by: Alex Chi <[email protected]>
ready for review :) |
but there's still difference between index scan and vector index scan: for vector index scans, we need to provide a constant vector; for normal index scan, it's just the order by column |
let's use a single |
Signed-off-by: Alex Chi <[email protected]>
This patch adds support for create index statements on vector columns and produces vector_index_scan plans. The executors are not implemented yet.