(sedona-db) branch jw/copy-into-override-semantics updated (48f8a420a -> 287e9d8ef)

[ja...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

james-willis pushed a change to branch jw/copy-into-override-semantics
in repository https://gitbox.apache.org/repos/asf/sedona-db.git


 discard 48f8a420a test(python): RS_SetBandNoDataValue null value clears the band's nodata
 discard 8b1cde0e8 fix(rust/sedona-raster-functions): RS_SetBandNoDataValue clears nodata on null
 discard e87d8887d feat(rust/sedona-raster): trinary Override for BandOverrides; copy_into stops composing views
 discard 5ddcfb1f5 refactor(rust/sedona-raster): make ViewEntries the interface for passing views
     add 7dd2c1bfa refactor(rust/sedona-raster): make ViewEntries the interface for passing views
     add 0e4cbc2bb feat(rust/sedona-raster): trinary Override for BandOverrides; copy_into stops composing views
     add d0d3f8dbc fix(rust/sedona-raster-functions): RS_SetBandNoDataValue clears nodata on null
     add 287e9d8ef test(python): RS_SetBandNoDataValue null value clears the band's nodata

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (48f8a420a)
            \
             N -- N -- N   refs/heads/jw/copy-into-override-semantics (287e9d8ef)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 python/sedonadb-zarr/src/lib.rs      | 8 ++++----
 python/sedonadb/src/raster_loader.rs | 6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)