Repository navigation
[Data] Support Ray 2.59 and set 1.3.dev0 - #9
Merged
Merged
Conversation
Admit Ray 2.59 within the bounded compatibility window, align CI and runtime evidence, and set the master development identity while keeping formal release validation strict. Signed-off-by: jiangxt2 <[email protected]>
|
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.
Description
Ray 2.59 is rejected by the current dependency and runtime bounds. Extend the supported window to
>=2.49.2,<2.60, align CI, runtime images and release-evidence checks with Ray 2.59.0, and set the master development version to1.3.dev0. Preserve the existing Datasink generations, zero write retries and ambiguous-write handling.Make the distributed fixture usable with Ray 2.59 through non-overlapping addresses and matching TLS identities, explicit object-store budgets, worker readiness checks and a consistent 3 GiB budget per Doris BE. Keep the Python 3.9 runtime baseline while restricting the Twine development dependency to Python 3.10 or newer.
Related issues
None.
How tested
.venv/bin/python -m pytest tests/unit: 320 passed, zero skipped on Python 3.12.12 / Ray 2.59.0. Native Ray Datasink contracts passed on Python 3.11 and 3.13..venv/bin/python -m pytest tests/integration -v: 30 real Doris 4.0.6 read/write cases passed.RAY_DORIS_SLOW_PROFILE=full ./tests/slow_integration/run.sh: all 9 distributed scenarios passed with Ray 2.59.0, Doris 4.0.6, three workers and three BEs at 3 GiB each.Additional information
MySQL and Flight SQL retain their documented maturity and transaction boundaries. Formal releases require two-component versions and exact candidate evidence; the development version is not a formal release identity.