Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Warn users using dense arrays with sparse fragments. #5116

Merged
merged 2 commits into from
Jul 9, 2024

Conversation

KiterLuc
Copy link
Contributor

@KiterLuc KiterLuc commented Jun 19, 2024

Support for reading sparse fragments in dense arrays will be removed in TileDB version 2.27 to be released in September 2024. To make sure these arrays continue to work after an upgrade to version 2.27 or later, please consolidate the sparse fragments using a TileDB version 2.26 or earlier.

For now, this adds a warning to user using dense arrays with sparse fragment. Support for writing sparse fragments in dense arrays was removed in TileDB 2.5 and as the user can easily consolidate to get rid of sparse fragments, the decision was made to remove support for reading these arrays.

[sc-47348]


TYPE: DEPRECATION
DESC: Warn users using dense arrays with sparse fragments.

This adds a warning to user using dense arrays with sparse fragments that support will be removed in TileDB 2.27. Support for writing sparse fragments in dense arrays was removed in TileDB 2.5 and as the user can easily consolidate to get rid of sparse fragments, the decision was made to remove support for reading these arrays.

---
TYPE: DEPRECATION
DESC: Warn users using dense arrays with sparse fragments.
@KiterLuc KiterLuc marked this pull request as draft June 19, 2024 16:02
@KiterLuc KiterLuc marked this pull request as ready for review June 21, 2024 08:46
Copy link
Member

@teo-tsirpanis teo-tsirpanis left a comment

Choose a reason for hiding this comment

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

The PR's DESC should be something like Support for reading sparse fragments in dense arrays will be removed in TileDB version 2.27 to be released in September 2024. To make sure these arrays continue to work after an upgrade to version 2.27 or later, please consolidate the sparse fragments using a TileDB version 2.26 or earlier..

@KiterLuc KiterLuc merged commit 7b88c3e into dev Jul 9, 2024
61 of 62 checks passed
@KiterLuc KiterLuc deleted the lr/warn-sparse-frag-dense-array-deprecation/ch47348 branch July 9, 2024 18:10
github-actions bot pushed a commit that referenced this pull request Jul 9, 2024
Support for reading sparse fragments in dense arrays will be removed in
TileDB version 2.27 to be released in September 2024. To make sure these
arrays continue to work after an upgrade to version 2.27 or later,
please consolidate the sparse fragments using a TileDB version 2.26 or
earlier.

For now, this adds a warning to user using dense arrays with sparse
fragment. Support for writing sparse fragments in dense arrays was
removed in TileDB 2.5 and as the user can easily consolidate to get rid
of sparse fragments, the decision was made to remove support for reading
these arrays.

[sc-47348]

---
TYPE: DEPRECATION
DESC: Warn users using dense arrays with sparse fragments.

(cherry picked from commit 7b88c3e)
KiterLuc added a commit that referenced this pull request Jul 9, 2024
Support for reading sparse fragments in dense arrays will be removed in
TileDB version 2.27 to be released in September 2024. To make sure these
arrays continue to work after an upgrade to version 2.27 or later,
please consolidate the sparse fragments using a TileDB version 2.26 or
earlier.

For now, this adds a warning to user using dense arrays with sparse
fragment. Support for writing sparse fragments in dense arrays was
removed in TileDB 2.5 and as the user can easily consolidate to get rid
of sparse fragments, the decision was made to remove support for reading
these arrays.

[sc-47348]

---
TYPE: DEPRECATION
DESC: Warn users using dense arrays with sparse fragments.
KiterLuc added a commit that referenced this pull request Jul 9, 2024
…gments. (#5173)

Backport 7b88c3e from #5116.

Co-authored-by: KiterLuc <67824247+KiterLuc@users.noreply.github.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants