Skip to content

[Data] Support Ray 2.59 and set 1.3.dev0 - #9

Merged
jiangxt2 merged 1 commit into
masterfrom
ray-259-compatibility
Oct 13, 2026
Merged

jiangxt2 merged 1 commit into
masterfrom
ray-259-compatibility

Conversation

@jiangxt2

Copy link
Copy Markdown
Owner

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 to 1.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.
  • Ruff, mypy, workflow/documentation checks, strict Sphinx and spelling checks, Wheel/sdist builds, Twine checks and isolated artifact installations passed.

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.

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]>
@greptile-apps

greptile-apps Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Extends Ray support to >=2.49.2,<2.60 and sets the development version to 1.3.dev0.

  • ray-doris now supports Ray releases through 2.59.
  • The slow cluster runs Ray 2.59.0 with updated addresses and resource limits.
  • Master package builds now identify as version 1.3.dev0.

Reviews (1) · Last reviewed commit: "[Data] Support Ray 2.59 and set 1.3.dev0" · Reviewed by Greptile

@jiangxt2
jiangxt2 merged commit d324220 into master Oct 13, 2026
11 checks passed
@jiangxt2
jiangxt2 deleted the ray-259-compatibility branch October 13, 2026 13:07
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.

1 participant