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

[client-v2, jdbc-v2] Add MultiPoint type support

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

I maintainer di solito rispondono entro 1 giorno

@polyglotAI-bot ci sta già lavorando.

Dal 13/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

area:data-type enhancement

Follow-up to #2577. At the time it was noted that ClickHouse has no MultiPoint type:

ClickHouse doesn't support GeometryCollection, MultiPoint. Here is link for supported types https://clickhouse.com/docs/sql-reference/data-types/geo

There is a Ring what may be a MultiPoint.

Originally posted by @chernser in #2577

That has since changed on the server side. MultiPoint is now a first-class geo type documented on that same page, defined as Array(Point), and Geometry is documented as a common type for all the geo types listed there.

Note on versions: this is a heads-up, not a regression report. MultiPoint is not in 26.7 or earlier — I'm testing against a master/head build (26.8.1.146), so it should land in the next release. Filing now so client support can be in place before then.

The client already ships Geometry support (#2815) for CH 25.11+, where Geometry became Variant(Point, Ring, LineString, MultiLineString, Polygon, MultiPolygon). MultiPoint appears to be the one geo type left out of both the concrete-type path and that variant list.

GeometryCollection remains correctly out of scope — Geometry is the ClickHouse equivalent.

Reproduction

CREATE TABLE geo_multipoint (mp MultiPoint) ENGINE = Memory();
INSERT INTO geo_multipoint VALUES([(0, 0), (10, 0), (10, 10), (0, 10)]);
SELECT mp, toTypeName(mp) FROM geo_multipoint;

-- via WKT, and through the unified type
SELECT readWKT('MULTIPOINT(0 0, 10 0, 10 10)') AS mp, toTypeName(mp);
CREATE TABLE geo_any (g Geometry) ENGINE = Memory();
INSERT INTO geo_any SELECT readWKT('MULTIPOINT(0 0, 10 0, 10 10)');
SELECT g, toTypeName(g) FROM geo_any;

Expected: MultiPoint is recognised as a geo column type and returned in the same geometry-aware representation the other geo types got after #2581, and it round-trips on insert.

Actual: reading a MultiPoint column via jdbc-v2 gives:

Caused by: java.lang.IllegalArgumentException: Unsupported data type: MultiPoint

Proposed changes

  • Add MultiPoint to the ClickHouse data-type enum / type parser.
  • Read path: map MultiPoint to the same geometry representation used for Ring / LineString (both are also Array(Point)).
  • Write path: support inserting MultiPoint, including via readWKT / WKB round-trip.
  • JDBC metadata: getColumnType / getColumnTypeName / getColumnClassName for MultiPoint columns, so v2 doesn't NPE the way the types in #2711 did.
  • Extend Geometry variant handling if the server includes MultiPoint in it.

Environment

  • clickhouse-java: 0.9.8
  • Driver: jdbc-v2 / client-v2
  • ClickHouse server: 26.8.1.146 (master/head build — not a stable release)
Lingua principale
Java
Stelle
1.6k
Fork
638
Merge medio
2g 46m
PR unite (30g)
46

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 ClickHouse/clickhouse-java

Tutte le issue di ClickHouse/clickhouse-java

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.