FrankChen021 commented on PR #20286:
URL: https://github.com/apache/druid/pull/20286#issuecomment-5585194288

   Exact-head dependency compatibility receipt for base 
`33f7f778dfc2d8b06ca7c1d7a93f54f162526cee` and head 
`92b56de668c77a012741dae3f7cc2a729d5b3092`.
   
   Release inventory: the only actually published transition is KCL `v3.5.1` 
(2026-07-22) -> `v3.5.2` (2026-09-04); there are no published intermediate 
releases. Evidence: 
[v3.5.1](https://github.com/awslabs/amazon-kinesis-client/releases/tag/v3.5.1), 
[v3.5.2](https://github.com/awslabs/amazon-kinesis-client/releases/tag/v3.5.2), 
and the [upstream 
compare](https://github.com/awslabs/amazon-kinesis-client/compare/v3.5.1...v3.5.2).
   
   The prior PR-local finding was the stale `licenses.yaml` KCL version; the 
current exact head contains the minimal fix in `92b56de668` and records KCL 
`3.5.2` as Apache License 2.0. The carried-forward KCL 3.5 single-table 
migration/coordinator history is Druid-irrelevant: this extension imports only 
`software.amazon.kinesis.retrieval.KinesisClientRecord` and `AggregatorUtil` 
for KPL deaggregation, not the KCL scheduler, coordinator, lease, or migration 
components. The upstream 3.5.1 -> 3.5.2 file diff contains no retrieval-class 
changes, and the public `KinesisClientRecord` and `AggregatorUtil` signatures 
match at both artifacts.
   
   Compatibility assessment for this exact head:
   
   | Area | Result | Evidence |
   | --- | --- | --- |
   | API/ABI | SAFE | Druid-imported KCL retrieval classes have unchanged 
public signatures; no removed or changed Druid API. |
   | Runtime | SAFE | Release changes coordinator/migration/stream-cleanup 
paths unused by Druid; `KinesisRecordSupplier` continues the same AWS SDK 
Record -> KinesisClientRecord -> AggregatorUtil flow. |
   | Configuration | SAFE | Only the Maven KCL version and license inventory 
changed; no Druid or KCL runtime configuration is introduced. |
   | Serialization/wire | SAFE | No `AggregatorUtil`/record serialization 
change; no Kinesis wire-format or Druid JSON format change. |
   | Persistence | SAFE | Druid does not persist KCL coordinator/lease state or 
KinesisClientRecord objects. |
   | Clients | SAFE | Druid still uses the managed AWS SDK v2 Kinesis client; 
no client/service contract changed. |
   | Transitive dependencies | SAFE | Published 3.5.1 and 3.5.2 POMs differ 
only in parent version; exact-head resolution selects KCL 3.5.2 with 
Druid-managed AWS SDK 2.54.10, Guava 33.7.1, protobuf 4.36.1, and commons-lang3 
3.20.0, with existing exclusions intact. |
   | Licenses | SAFE | KCL POM remains Apache-2.0 and `licenses.yaml` now 
records 3.5.2. |
   | Extension/plugin SPI | SAFE | No Druid Java, service-loader, extension, or 
plugin SPI files changed. |
   
   Validation carried forward and rechecked: `git diff --check` passed; focused 
Maven dependency resolution passed; the prior exact-head focused run passed 31 
Kinesis tests. No additional PR-local failure is present.
   
   CI is non-terminal at the exact head: 25 reported CheckRuns, 4 
COMPLETED/SUCCESS, 10 IN_PROGRESS, 10 QUEUED, and 1 COMPLETED/NEUTRAL aggregate 
CodeQL; no status contexts. PR state is OPEN/MERGEABLE/UNSTABLE with no 
approval. Leaving the PR open and unapproved; no rerun, approval, or merge is 
justified until the required checks complete successfully.


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to