The GitHub Actions job "Build" on rocketmq-flink.git/main has failed.
Run started by GitHub user lizhimins (triggered by lizhimins).

Head commit for run:
3d803c292059f21a90c578904139e21fa9642f9e / lizhimins <[email protected]>
[ISSUE #133] refactor: restructure to multi-module layout and harden the 
remoting connector (#134)

Split the single-module project into flink-connector-rocketmq +
flink-sql-connector-rocketmq, move legacy classes under
streaming.connectors.rocketmq, and fix a batch of issues found in
review and verified against an Aliyun commercial instance:

- implement the no-op SQL row deserialization (source rows were empty)
- close the producer in RocketMQWriter, rework AT_LEAST_ONCE to async
  send with pending counter and flush barrier, call
  serializationSchema.open() on construction
- propagate fetch()/fetchOffsets failures instead of swallowing them
- add consumer-side fallback for min/max/committed/timestamp offset
  lookup when admin broker-name resolution fails on cloud instances
- implement sanityCheck() in source/sink builders
- apply parameter passthrough fixes (send timeout/retry, batch size,
  namespace, filters, scan.mode auto-infer, transaction timeout unit)
- wire USE_TLS, MQ_CLIENT_API_TIMEOUT, CLIENT_CALLBACK_EXECUTOR_THREADS
  and the pull flow-control options; drop dead options and unused code

Tests: migrate unit tests to the new layout and add manual integration
tests against a real commercial instance (FLIP-27 datastream pipeline,
EXACTLY_ONCE two-phase commit, SQL DDL end-to-end); credentials are
read from the environment.

CI and docs: add GitHub Actions (spotless:check + clean package on a
JDK 11/17 matrix, replacing the stale .travis.yml), rewrite the README
following the official Flink connector layout, split detailed
configuration into docs/ (remoting-connector.md, sql-connector.md,
legacy-connector.md) and add url/licenses/mailing lists to the pom.

Report URL: https://github.com/apache/rocketmq-flink/actions/runs/29889746662

With regards,
GitHub Actions via GitBox

Reply via email to