Skip to content
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

Combine multiple indexes when it's likely to improve performance #5734

Open
rbasralian opened this issue Jul 8, 2024 · 0 comments
Open

Combine multiple indexes when it's likely to improve performance #5734

rbasralian opened this issue Jul 8, 2024 · 0 comments
Assignees
Labels
core Core development tasks feature request New feature or request query engine

Comments

@rbasralian
Copy link
Contributor

When a table has multiple independent data indexes, the query engine does not leverage them in situations where it may be beneficial to do so.

For example, if you have a PartitionAwareSourceTable (partitioned by Date), where each partition has hundreds of millions of rows and several thousand distinct Syms, and data indexes are available for the Sym column, then an operation like t.partitionBy("Date", "Sym") should probably 'combine' the index by Date and the index by Sym into an index by Date/Sym.

@rbasralian rbasralian added feature request New feature or request triage labels Jul 8, 2024
@rcaudy rcaudy removed the triage label Jul 8, 2024
@rcaudy rcaudy added this to the 4. Unscheduled milestone Jul 8, 2024
@rcaudy rcaudy added query engine core Core development tasks labels Jul 8, 2024
@rcaudy rcaudy self-assigned this Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Core development tasks feature request New feature or request query engine
Projects
None yet
Development

No branches or pull requests

2 participants