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

Use unordered layout for aggregate-only read queries on sparse arrays. #5255

Merged
merged 4 commits into from
Sep 2, 2024

Conversation

teo-tsirpanis
Copy link
Member

@teo-tsirpanis teo-tsirpanis commented Aug 23, 2024

SC-53286

If the user has not set a query layout, it will default to row-major, which will use the legacy reader on sparse arrays, and fail if aggregates were specified.

However, if only aggregates are specified and no regular data buffers, the layout doesn't matter and we can transparently switch to the much more efficient unordered layout.


TYPE: IMPROVEMENT
DESC: Fix read queries on sparse arrays where only aggregates are requested and no layout is specified.

@teo-tsirpanis teo-tsirpanis force-pushed the teo/query-aggregate-unordered branch 2 times, most recently from 86c70cb to ad568d7 Compare August 28, 2024 12:31
@teo-tsirpanis teo-tsirpanis changed the title Perform aggregate-only read queries on sparse arrays with unordered layout. Use unordered layout for aggregate-only read queries on sparse arrays. Aug 30, 2024
/**
* Return the layout that will be used to execute the query.
*
* This is usually set by the user but cen be overridden by TileDB in cases
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* This is usually set by the user but cen be overridden by TileDB in cases
* This is usually set by the user but can be overridden by TileDB in cases

@KiterLuc KiterLuc merged commit fd24448 into dev Sep 2, 2024
63 checks passed
@KiterLuc KiterLuc deleted the teo/query-aggregate-unordered branch September 2, 2024 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants