Not thread safe.
Not thread safe. Assumed to only be called from the journal actor. However, unlike asyncWriteMessages it can be called before the previous Future completes
Execute creation of keyspace and tables is limited to one thread at a time reduce the risk of (annoying) "Column family ID mismatch" exception when write and read-side plugins are started at the same time.
Execute creation of keyspace and tables is limited to one thread at a time reduce the risk of (annoying) "Column family ID mismatch" exception when write and read-side plugins are started at the same time. Those statements are retried, because that could happen across different nodes also but serializing those statements gives a better "experience".
The materialized view for eventsByTag query is not created if maxTagId
is 0.