[
https://issues.apache.org/jira/browse/CASSSIDECAR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078540#comment-18078540
]
Yifan Cai commented on CASSSIDECAR-443:
---------------------------------------
+1
Could you please share the CircleCI link?
> 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
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> 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. Adding new component makes it easy to remove, once Sidecar
> upgrades Java driver.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
