You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Lukasz Antoniak (Jira)" <ji...@apache.org> on 2026/04/24 06:44:00 UTC

[jira] [Updated] (CASSSIDECAR-443) Support column types not parseable by Java 3.x driver

     [ https://issues.apache.org/jira/browse/CASSSIDECAR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukasz Antoniak updated CASSSIDECAR-443:
----------------------------------------
    Description: 
Sidecar uses schema metadata functionality of Java driver 3.x extensively. It is very convenient, because:
 # Keyspace schema is already parsed.
 # Metadata is updated asynchronously as soon as {{SCHEMA_CHANGE}} events are published.

{{SchemaParser}} from Java 3.x driver does not store {{TableMetadata}} if the schema of a given table could not be parsed ([source|https://github.com/apache/cassandra-java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/SchemaParser.java#L313-L320]). Since 3.x driver does not support vector type, Sidecar will assume that all tables with vector column do not exist.

There is already a ticket CASSSIDECAR-421 to upgrade Java driver to version 4.x. This is an extensive task, so purpose of hereby ticket is to find a workaround to the issue. Proposed approach introduces another component that caches schema of tables not supported by driver's metadata feature. The schema is looked up using CQL {{DESCRIBE}} statement. Cache is periodically refreshed.

  was:
Sidecar uses schema metadata functionality of Java driver 3.x extensively. It is very convenient, because:
 # Keyspace schema is already parsed.
 # Metadata is updated asynchronously as soon as {{SCHEMA_CHANGE}} events are published.

{{SchemaParser}} from Java 3.x driver does not store {{TableMetadata}} if the schema of a given table could not be parsed ([source|https://github.com/apache/cassandra-java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/SchemaParser.java#L313-L320]). Since 3.x driver does not support vector type, Sidecar will assume that all tables with vector column do not exist.

There is already a ticket CASSSIDECAR-421 to upgrade Java driver to version 4.x. This however is an extensive task, so purpose of hereby ticket is to find a workaround to the issue. Proposed approach introduces another component that caches schema of tables not supported by driver's metadata feature. The schema is looked up using CQL {{DESCRIBE}} statement. Cache is periodically refreshed.


> Support column types not parseable by Java 3.x driver
> -----------------------------------------------------
>
>                 Key: CASSSIDECAR-443
>                 URL: https://issues.apache.org/jira/browse/CASSSIDECAR-443
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Improvement
>            Reporter: Lukasz Antoniak
>            Assignee: Lukasz Antoniak
>            Priority: Major
>
> Sidecar uses schema metadata functionality of Java driver 3.x extensively. It is very convenient, because:
>  # Keyspace schema is already parsed.
>  # Metadata is updated asynchronously as soon as {{SCHEMA_CHANGE}} events are published.
> {{SchemaParser}} from Java 3.x driver does not store {{TableMetadata}} if the schema of a given table could not be parsed ([source|https://github.com/apache/cassandra-java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/SchemaParser.java#L313-L320]). Since 3.x driver does not support vector type, Sidecar will assume that all tables with vector column do not exist.
> There is already a ticket CASSSIDECAR-421 to upgrade Java driver to version 4.x. This is an extensive task, so purpose of hereby ticket is to find a workaround to the issue. Proposed approach introduces another component that caches schema of tables not supported by driver's metadata feature. The schema is looked up using CQL {{DESCRIBE}} statement. Cache is periodically refreshed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org