Merge pull request #4756 from ClickHouse/update_java_docs_nov_2025

Update java docs Dec 2025

Author: chernser

docs/integrations/language-clients/java/client/_snippets/_v0_7.mdx

@@ -1,5 +1,6 @@
 ---
 title: 'Java'
+sidebar_position: 1
 keywords: ['clickhouse', 'java', 'jdbc', 'client', 'integrate', 'r2dbc']
 description: 'Options for connecting to ClickHouse from Java'
 slug: /integrations/java
@@ -20,7 +21,7 @@ import CodeBlock from '@theme/CodeBlock';
 
 Java client is a library implementing own API that abstracts details of network communications with ClickHouse server. Currently HTTP Interface is supported only. The library provide utilities to work with different ClickHouse formats and other related functions.
 
-Java Client was developed far back in 2015. Its codebase became very hard to maintain, API is confusing, it is hard to optimize it further. So we have refactored it in 2024 into a new component  `client-v2`. It has clear API, lighter codebase and more performance improvements, better ClickHouse formats support (RowBinary & Native mainly). JDBC will use this client in near feature.  
+Java Client was developed far back in 2015. Its codebase became very hard to maintain, API is confusing, it is hard to optimize it further. So we have refactored it in 2024 into a new component  `client-v2`. It has clear API, lighter codebase and more performance improvements, better ClickHouse formats support (RowBinary & Native mainly). JDBC will use this client in near feature.
 
 ### Supported data types {#supported-data-types}
 
@@ -83,7 +84,7 @@ Java Client was developed far back in 2015. Its codebase became very hard to mai
 - AggregatedFunction - :warning: does not support `SELECT * FROM table ...`
 - Decimal - `SET output_format_decimal_trailing_zeros=1` in 21.9+ for consistency
 - Enum - can be treated as both string and integer
-- UInt64 - mapped to `long` in client-v1 
+- UInt64 - mapped to `long` in client-v1
 :::
 
 ### Features {#features}
@@ -94,7 +95,8 @@ Table of features of the clients:
 |----------------------------------------------|:---------:|:---------:|:---------:|
 | Http Connection                              |✔       |✔      | |
 | Http Compression (LZ4)                       |✔       |✔      | |
-| Server Response Compression - LZ4            |✔       |✔      | | 
+| Application Controlled Compression           |✔       |✗      | |
+| Server Response Compression - LZ4            |✔       |✔      | |
 | Client Request Compression - LZ4             |✔       |✔      | |
 | HTTPS                                        |✔       |✔      | |
 | Client SSL Cert (mTLS)                       |✔       |✔      | |
@@ -109,6 +111,7 @@ Table of features of the clients:
 | Log Comment                                  |✔       |✔      | |
 | Session Roles                                |✔       |✔      | |
 | SSL Client Authentication                    |✔       |✔      | |
+| SNI Configuration                            |✔       |✗      | |
 | Session timezone                             |✔       |✔      | |
 
 JDBC Drive inherits same features as underlying client implementation. Other JDBC features are listed on its [page](/integrations/language-clients/java/jdbc).
@@ -122,7 +125,7 @@ JDBC Drive inherits same features as underlying client implementation. Other JDB
 
 ### Logging {#logging}
 
-Our Java language client uses [SLF4J](https://www.slf4j.org/) for logging. You can use any SLF4J-compatible logging framework, such as `Logback` or `Log4j`. 
+Our Java language client uses [SLF4J](https://www.slf4j.org/) for logging. You can use any SLF4J-compatible logging framework, such as `Logback` or `Log4j`.
 For example, if you are using Maven you could add the following dependency to your `pom.xml` file:
 
 ```xml title="pom.xml"