Conversation
Signed-off-by: jiangxt2 <jiangxt2@vip.qq.com>
Signed-off-by: jiangxt2 <jiangxt2@vip.qq.com>
Code Coverage Report
Files
|
Signed-off-by: jiangxt2 <jiangxt2@vip.qq.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This pull request adds a Gravitino-owned Ray Data Iceberg REST integration test to the Python client test suite.
The change:
rayIcebergITGradle task with an isolated Python environment;gravitino/version.inifile before running the client test;The implementation does not modify Java Iceberg REST code, Ray source code, or Ray
Catalog.resolve()behavior.Why are the changes needed?
Gravitino documents Ray Data access through the Iceberg REST endpoint and
catalog_kwargs, but the Python client integration suite did not have a real end-to-end regression test for this contract.The test protects the existing-table read/write path and validates the Gravitino auxiliary service lifecycle using the existing Lance Ray IT as the implementation baseline.
Fix: #13323
Does this PR introduce any user-facing change?
No end-user API or runtime behavior changes are introduced; contributor-facing Python integration-test tooling is added.
How was this patch tested?
Passed:
git diff --checkruff check --no-cache clients/client-python/tests/integration/test_ray_iceberg.pyruff format --check --no-cache clients/client-python/tests/integration/test_ray_iceberg.py:clients:client-python:rayIcebergIT --dry-run./gradlew :clients:client-python:rayIcebergIT --no-daemon --console=plain— passed; 1 test ran and completed successfully.Before running the E2E, build or reuse the Gravitino distribution with
./gradlew compileDistribution -PskipWeb=true -x test.This E2E is currently opt-in/manual and is not wired into the default CI workflow.