bbiiaaoo opened a new pull request, #10637:
URL: https://github.com/apache/gravitino/pull/10637
### What changes were proposed in this pull request?
- Upgraded Lance dependencies to the new coordinates and versions:
- `org.lance:lance-core:2.0.1`
- `org.lance:lance-namespace-core:0.4.5`
- Migrated Lance-related imports and model usages from `com.lancedb.*` to
`org.lance.*`.
- Adapted code paths to upstream API changes, including mode handling
(`Enum` -> `String`) and updated builder-style APIs.
- Updated Lance namespace/table operations, exception mapping, and
serialization compatibility in Gravitino Lance modules.
- Added internal compatibility utilities (`ObjectIdentifier`, `PageUtil`,
`CommonUtil`, `JsonArrowSchemaConverter`) to align with the new Lance namespace
SDK behavior.
- Updated Lance REST service docs and examples to match new dependencies and
request fields.
- Updated related unit/integration tests to cover the new APIs.
### Why are the changes needed?
- Lance upstream migrated artifacts/packages from `com.lancedb` to
`org.lance` and introduced breaking API changes in newer versions.
- Without this upgrade, Gravitino Lance modules may face dependency
incompatibility and runtime/API mismatch issues.
- This patch keeps Gravitino Lance integrations compatible with the latest
Lance ecosystem while preserving expected REST behaviors.
Fix: #10445
### Does this PR introduce _any_ user-facing change?
- Documentation/examples are updated to use `org.lance` dependencies and the
new request style (for example, lowercase mode values such as `create`).
- No new Gravitino public API is introduced.
### How was this patch tested?
- Ran unit tests and integration tests for `catalog-lakehouse-generic`,
`lance-common`, and `lance-rest-server`.
- Completed end-to-end verification with `curl -> Gravitino` requests,
covering Lance namespace and table workflows on the upgraded dependencies.
- This round focused on the impacted modules; the full-repo test matrix was
not executed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
