[
https://issues.apache.org/jira/browse/CASSANDRA-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290180#comment-13290180
]
Sylvain Lebresne commented on CASSANDRA-4018:
---------------------------------------------
Yes, actually there is a bunch of info a node have on it's peer that we don't
write in the system table (the ring_id, but things like other nodes version,
shema version etc...). We don't need to persist them per-se internally, but
doing it would allow to expose it to the user (for example, for the schema
version, that would give a very simple way for client to check the cluster is
fully up to date on the schema).
I could typically imagine changing peers and local a bit to have peers store
all the things we know about our peers (including the local node) that we deem
useful to expose, and then maybe have a 'configuration' table (or 'local' but I
like 'configuration :)) for whatever make sense only for the local node.
That being said, maybe it's worth committing what we have (maybe without my
last patch for now), and open a separate ticket to see if we want to go a step
further.
> Add column metadata to system columnfamilies
> --------------------------------------------
>
> Key: CASSANDRA-4018
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4018
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.2
>
>
> CASSANDRA-3792 adds this to the schema CFs; we should modernize the other
> system CFs as well
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
