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

[Backport release-2.23] Add array uri to tiledb_array_deserialize #5109

Merged
merged 2 commits into from
Jun 19, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 19, 2024

Backport 69028d8 from #4961.


TYPE: IMPROVEMENT
DESC: Add array uri to tiledb_array_deserialize

[sc-47129

](https://app.shortcut.com/tiledb-inc/story/47129/add-array-uri-to-tiledb-array-deserialize
)
Today `tiledb_array_deserialize` is using a hardcoded uri name
(`"deserialized_array"`) , whereas `tiledb_deserialize_query_and_array`
is requiring the actual `array_uri` as an argument. The former is
problematic for wrapping those calls in python, so this ticket is aiming
to unify the two to both receive the `array_uri` as input. (history on
why this is needed here:
https://app.shortcut.com/tiledb-inc/story/47139/investigate-if-core-serialization-apis-could-be-used-externally-to-pass-cache-open-arrays)

There's no backward compatibility issue here as this is a
deserialization function only called by REST Server, so we don't need to
keep both versions of `tiledb_array_deserialize`.

That said, the REST-CI tests that run based on latest dev on Core and
latest master in Cloud-REST will break after this change. We will handle
this by adapting the REST-CI script to patch temporarily Cloud-REST
master with the needed change and remove when 2.24 is released
TileDB-Inc/TileDB-Internal#27 . Another idea was
to maintain both flavors until the release is ready to go out and then
remove but C doesn't support overloading functions.

Future work to track:  #4961

---
TYPE: IMPROVEMENT
DESC: Add array uri to tiledb_array_deserialize
@KiterLuc KiterLuc force-pushed the backport-4961-to-release-2.23 branch from a58edf5 to 6465f0a Compare June 19, 2024 15:12
@KiterLuc KiterLuc merged commit e9d6285 into release-2.23 Jun 19, 2024
58 checks passed
@KiterLuc KiterLuc deleted the backport-4961-to-release-2.23 branch June 19, 2024 19:48
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.

None yet

2 participants