[CASSANDRA-9449] Running ALTER TABLE cql statement asynchronously results in failure

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate

Environment

Singe cluster environment

• Severity: Normal
• Assignee: Unassigned
• Reporter: Paul Praet
• Created: 21/May/15 09:42
• Updated: 16/Apr/19 09:31
• Resolved: 04/Jun/15 12:08

Description

When running 'ALTER TABLE' cql statements asynchronously, we notice that often certain columns are missing, causing subsequent queries to fail.
The code snippet below can be used to reproduce the problem.

cassandra is a com.datastax.driver.core.Session reference.
We construct the table synchronously and then alter it (adding five columns) with the cassandra async API. We synchronize to ensure the table is properly altered before continuing. Preparing the statement at the bottom of the code snippet often fails:

 com.datastax.driver.core.exceptions.InvalidQueryException: Unknown identifier columnf 

 @Test
    public void testCassandraAsyncAlterTable() throws Exception {
        ResultSet rs = cassandra.execute("CREATE TABLE device ( columnA text, columnB text, columnC timestamp, PRIMARY KEY ((columnA, columnB)));");

        List<ResultSetFuture> futures = new ArrayList<>();
        futures.add(cassandra.executeAsync("ALTER TABLE device ADD columnD text;"));
        futures.add(cassandra.executeAsync("ALTER TABLE device ADD columnE text;"));
        futures.add(cassandra.executeAsync("ALTER TABLE device ADD columnF text;"));
        futures.add(cassandra.executeAsync("ALTER TABLE device ADD columnG text;"));
        futures.add(cassandra.executeAsync("ALTER TABLE device ADD columnH text;"));

        for(ResultSetFuture resultfuture : futures){ resultfuture.get(); }
          
        /* discard the result; only interested to see if it works or not */
        cassandra.prepare("INSERT INTO device (columnA, columnB, columnC,columnD,columnE,columnF,columnG,columnH) VALUES (?,?,?,?,?,?,?,?);");

    }

Issue Links

• duplicates: CASSANDRA-9425 Make node-local schema fully immutable