Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#40,048 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@nitinware ya está trabajando en esto.

Desde el 7/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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
Lenguaje dominante
Java
Estrellas
8.7k
Forks
4.7k
Merge medio
2 d 8 h
PR fusionados (30 d)
246

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/beam

Todos los issues de apache/beam

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.