NPE connecting to a cluster which is undergoing schema changes

Description

I encountered the following exception connecting to a cluster on which a client was adding keyspaces and tables.

Environment

None

Pull Requests

None

Activity

Show:
Sylvain Lebresne
May 2, 2014, 3:34 PM

The NPE means we have a table definition but no columns for it (which, in C* 2.0, is nonsensical). Since we fetch table and columns definitions in parallel during schema refresh, we can definitively end up in that case however if our queries "race" with a new table being persisted. So pushed a fix to detect that situation. If you had an easy way to reproduce and can confirm it fixes it for your that'd be great, but If I'm right on the cause it might not at all be easy to reproduce, so I'm going to optimistically close it as resolved and we can re-open if someone reproduce on 2.0.2.

Assignee

Sylvain Lebresne

Reporter

Nicolas Favre-Felix

Labels

None

PM Priority

None

Reproduced in

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