ray-doris 1.1

ray-doris 1.1

Highlights

• Support final Ray releases from 2.49.2 through the 2.58.x line, including tested Ray 2.57.0 and
  2.58.0 compatibility points.
• Publish the direct typing-extensions dependency needed by the Python 3.13 installation
  contract.
• Reject non-finite Doris write connection and request timeouts before any network I/O.
• Use versioned release-note files and GitHub Releases as the single public release history.
• Align the distributed slow suite with Ray 2.58.0 and provide infrastructure to bind future
  enterprise evidence to one exact candidate commit, workflow run, image set, topology, and
  scenario manifest.
• Keep this release at Alpha maturity: the Linux x64 runner and exact-SHA distributed full evidence
  remain deferred, so this release makes no enterprise or stable/production claim.

Versioning and compatibility

• Keep the package version format at exactly two components: major.minor.
• Cover Python 3.9 with Ray 2.49.2 as the Alpha legacy lower-bound profile.
• Cover Python 3.10 with Ray 2.57.0 and Python 3.12/3.13 with Ray 2.58.0.
• Keep Doris 4.0.6 as the required real-infrastructure target.
• Keep MySQL as the production-candidate read transport. Flight SQL and automatic transport
  selection remain experimental.
• Keep write task retries disabled. Stream Load requests don't provide whole-Dataset atomicity or
  exactly-once semantics.

1.0 release-note correction

The 1.0 release notes described the package as read-only, but the 1.0 tag and artifacts also
included bounded Doris HTTP Stream Load writes through Ray's public Datasink API. Version 1.0
supported load, Unique Key upsert, and Merge-on-Write Unique Key partial_update, with Ray task
retries disabled and ambiguous post-send failures reported without automatic replay.

Version 1.0 also included the read-path hardening previously recorded as unreleased work: balanced
tablet splits, bounded MySQL cleanup, MySQL/Flight schema consistency checks, driver-side option
serialization validation, credential references, private-CA query planning, redacted errors, and
exact-SHA slow-evidence infrastructure. This correction doesn't modify the immutable 1.0 tag or
published artifacts. The pre-1.0 alpha's tablet-aware read capabilities are subsumed by version 1.0.

Validation and release scope

• Complete static, unit, public contract, documentation, package, and isolated install checks.
• Complete the Ray 2.58 / Doris 4.0.6 required read/write integration profile.
• This Alpha release does not include exact-candidate full slow-suite evidence; the enterprise
  release profile continues to require it.
• Review these notes against the release commit before creating tag v1.1.

ray-doris 1.0

ray-doris 1.0

Highlights

• Initial public release of the independent, community-maintained Apache Doris read connector for
  Ray Data.
• Read exact Doris internal-catalog tables through tablet planning and streamed MySQL transport.
• Keep Flight SQL available as an explicitly selected experimental read transport.
• Provide explicit configuration, schema validation, credential redaction, and fail-closed error
  classification for the read path.

Compatibility and limitations

• Python 3.9, 3.10, and 3.12 are covered by the release compatibility matrix.
• Ray 2.49.2, 2.55.1, and 2.56.1 are the tested matrix points.
• Doris 4.0.6 is the fixed real-infrastructure target for required and distributed integration
  tests.
• MySQL is the production-candidate read transport. Flight SQL and automatic transport selection
  remain experimental.
• The read connector does not provide DDL, arbitrary SQL queries, cross-task snapshot isolation, or
  automatic replay of failed reads.

Validation

• Ruff, mypy, pre-commit, documentation, package, and Twine checks.
• Python/Ray unit and public contract tests, required Doris integration tests, and the exact-SHA
  distributed slow evidence required by the release workflow.