gnodet commented on code in PR #25034: URL: https://github.com/apache/camel/pull/25034#discussion_r3638500279
########## docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc: ########## @@ -978,6 +978,25 @@ The `io.vavr:vavr` and `io.vavr:vavr-match` runtime dependencies have been remov `camel-resilience4j`. The single internal usage of Vavr's `Try` monad has been replaced with a plain try-catch. This eliminates two transitive runtime JARs. No user-facing behavior change. +=== camel-clickhouse (new component) + +A new `camel-clickhouse` producer component has been added. It integrates with +https://clickhouse.com/[ClickHouse], the high-performance columnar OLAP database, using the official +ClickHouse Java client (client-v2). It exposes ClickHouse's native capabilities as first-class endpoint +options: native format streaming inserts (`RowBinary`, `JSONEachRow`, `CSV`, `TSV`, `Parquet`), +server-side asynchronous inserts, OLAP queries and health checks. + +[source,java] +---- +from("direct:events") + .to("clickhouse://analytics.events?operation=insert&format=JSONEachRow"); +---- + +The component supports the `insert` (default), `query` and `ping` operations, and can either use a shared +autowired `com.clickhouse.client.api.Client` bean or build its own client from the `serverUrl`, `username`, +`password` and `ssl` endpoint options. See the xref:next@components:clickhouse-component.adoc[ClickHouse component] Review Comment: **CI-blocking xref syntax error.** The single colon between `components` and the page name causes the `XRefCheckMojo` to misparse this as module `next@components` within the `manual` component (which doesn't exist). Cross-component xrefs require a double colon. All existing cross-component xrefs in the user manual use the double-colon pattern (e.g., `xref:components::validator-component.adoc`). ```suggestion `password` and `ssl` endpoint options. See the xref:next@components::clickhouse-component.adoc[ClickHouse component] ``` -- 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]
