Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request]: Add read() support to Java ClickHouseIO (currently write-only)

Aperta
  • Qualcosa non va?
#40,048 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@nitinware ci sta già lavorando.

Dal 7/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

io java new feature P2
What would you like to happen?

Motivation

The Java ClickHouseIO connector at sdks/java/io/clickhouse/ currently supports only writes. Reading from ClickHouse in a Beam pipeline requires falling back to JdbcIO with the ClickHouse JDBC driver, which loses ClickHouse-specific schema fidelity (LowCardinality, Array(T), Nullable(T), Nested, tuples) and native columnar transport.

Proposal

Add ClickHouseIO.read() and ClickHouseIO.readAll() PTransforms symmetric to the existing write path:

  • Native Row output using the ClickHouse client's native format
  • Query/projection via user-supplied SELECT template
  • Splittable reader for parallel reads across partitions / shards,
    modeled on JdbcIO's splitting pattern
  • Reuse the existing connection configuration builder from the writer

Benefits

  • Closes an obvious read/write asymmetry — every other major DB IO in
    Beam (JDBC, Cassandra, Mongo, HBase, Spanner, BigQuery, Snowflake)
    supports both directions
  • ClickHouse is increasingly common as an analytics source; users
    currently work around this with JdbcIO at the cost of type fidelity

Testing plan

  • Unit tests mirroring the existing writer test file
  • Integration test using the module's existing testcontainers-based
    ClickHouse setup (ClickHouseContainer is already wired in build.gradle)
  • No new dependencies required
Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components
  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Prism Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Lingua principale
Java
Stelle
8.7k
Fork
4.7k
Merge medio
2g 8h
PR unite (30g)
246

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/beam

Tutte le issue di apache/beam

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.