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

[Subtask]: Scan with ordering, and interesting order in general #20654

Open
fengttt opened this issue Dec 9, 2024 · 0 comments
Open

[Subtask]: Scan with ordering, and interesting order in general #20654

fengttt opened this issue Dec 9, 2024 · 0 comments
Assignees
Labels
kind/subtask priority/p0 Critical feature that should be implemented in this version
Milestone

Comments

@fengttt
Copy link
Contributor

fengttt commented Dec 9, 2024

Parent Issue

#20650

Detail of Subtask

When scan a table, if the scan order is the same as (or a subset prefix of) the clustering or primary key, we should be able to scan the table from many S3 objects and MERGE them, producing a stream of ordered records. It should be very efficient and use very little of memory.

The optimizer MUST know such an interesting order from scan -- v.s the cost using a real sort (could be external sort).

Describe implementation you've considered

No response

Additional information

No response

@fengttt fengttt added priority/p0 Critical feature that should be implemented in this version kind/subtask labels Dec 9, 2024
@fengttt fengttt added this to the 2.1.0 milestone Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/subtask priority/p0 Critical feature that should be implemented in this version
Projects
None yet
Development

No branches or pull requests

2 participants