You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have now intrroduced TileDBWriteOptions, a platform config used for tuning write options for SOMAArrays. This was motivated by the addition of optional global-order writes where the user is now able to specify whether the coordinates they've passed in are pre-sorted (global order writes) or not (unordered writes).
The write function was already taking in a TileDBCreateOptions platform config where the user could toggle whether to consolidate and vacuum fragments after the array was written. consolidate_and_vacuum has now also been moved into TileDBWriteOptions.
In order to not break existing code, consolidate_and_vacuum will temporarily remain in TileDBCreateOptions and write will also temporarily continue to also take in TileDBCreateOptions. However, this will be completely removed in 1.13.
The text was updated successfully, but these errors were encountered:
nguyenv
changed the title
Remove consolidate_and_vacuum from TileDBCreateOptions in 1.13
[python] Remove consolidate_and_vacuum from TileDBCreateOptions in 1.13
May 17, 2024
We have now intrroduced
TileDBWriteOptions
, a platform config used for tuning write options forSOMAArray
s. This was motivated by the addition of optional global-order writes where the user is now able to specify whether the coordinates they've passed in are pre-sorted (global order writes) or not (unordered writes).The
write
function was already taking in aTileDBCreateOptions
platform config where the user could toggle whether to consolidate and vacuum fragments after the array was written.consolidate_and_vacuum
has now also been moved intoTileDBWriteOptions
.In order to not break existing code,
consolidate_and_vacuum
will temporarily remain inTileDBCreateOptions
andwrite
will also temporarily continue to also take inTileDBCreateOptions
. However, this will be completely removed in 1.13.The text was updated successfully, but these errors were encountered: