Target schema refreshes more precisely

Description

The driver triggers schema refreshes on schema change events (see Cluster.Manager#handle) or responses (DefaultResultSetFuture#onSet).

Currently, this is always a full refresh, even when only a single table was created/updated. For keyspace that have lots of tables, querying schema_columnfamilies and schema_columns for all tables can have a non-negligible impact on network usage.

refreshSchemaAndSignal can take a table name as a parameter to target the refresh more precisely, so we should take advantage of that.

Environment

None

Pull Requests

None

Activity

Show:
Michael Nelson
November 21, 2014, 5:37 PM
Edited

Any delivery time estimate for this?

Pierre Laporte
December 14, 2014, 11:07 PM

I have created some additional tests for this ticket, see this pull request for more details.

Fixed

Assignee

Pierre Laporte

Reporter

Olivier Michallat

Labels

None

PM Priority

None

Affects versions

Fix versions

Pull Request

None

Doc Impact

None

Size

None

External issue ID

None

External issue ID

None

Components

Priority

Major
Configure