cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Tolbert (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14655) Upgrade C* to use latest guava (26.0)
Date Fri, 31 Aug 2018 16:40:00 GMT


Andy Tolbert commented on CASSANDRA-14655:

Ah - curious about the missing {{system_virtual_schema}} errors.  The way our schema resolution
logic works for the driver is if any of tables we query for schema don't exist, we bail out
(unless you use {{setSchemaMetadataEnabled(false)}} in your {{Cluster.builder}}).   We had
assumed that {{system_virtual_schema}} would be present for C* 4.0 always, which I believe
should be the case, but maybe in the context of the tests, the Cassandra server code is not
completely loaded?   We could consider silenty skipping parsing of virtual tables in this
case in the driver, although I think it's reasonable to expect that they should always be
there (just like we assume {{system_schema}} is).

With regards to the NPE, is there an associated stack trace?  Curious to know if the {{NPE}}
is raised by the driver or C* code.

> Upgrade C* to use latest guava (26.0)
> -------------------------------------
>                 Key: CASSANDRA-14655
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Libraries
>            Reporter: Sumanth Pasupuleti
>            Assignee: Sumanth Pasupuleti
>            Priority: Minor
>             Fix For: 4.x
> C* currently uses guava 23.3. This JIRA is about changing C* to use latest guava (26.0).
Originated from a discussion in the mailing list.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message