[
https://issues.apache.org/jira/browse/CASSANDRA-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145196#comment-16145196
]
Sylvain Lebresne commented on CASSANDRA-13812:
----------------------------------------------
bq. When we do update them in Core, we'd bump the timestamp too so that the new
default would override the old default, but still not affect the overrides by
the user - if any.
Fair enough. I can see this working if we do do that. That said, I have never
been privy to this intention and while I may have missed it, I haven't seen any
comment in the code documenting such intention/expected process, so maybe it's
at least worth documenting this.
> Missing system keyspace tables are not created
> ----------------------------------------------
>
> Key: CASSANDRA-13812
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13812
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
> Reporter: ZhaoYang
>
> Auth/Trace/Distributed Keyspaces or Tables dropped are not created on startup
> although a log message {{MigrationManager.java:220 - Create new table:
> TableMetadata...}} appears.
> Steps to reproduce:
> # Start node
> # {{DROP TABLE system_distributed.view_build_status;}}
> # {{DROP TABLE system_distributed.repair_history;}}
> # Stop node
> # Start node
> # Tables are *not* created, but log messages appear
> Cause:
> System's keyspaces or tables are created with timestamp 0 in CASSANDRA-13441
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
