[
https://issues.apache.org/jira/browse/ACCUMULO-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15485864#comment-15485864
]
Josh Elser commented on ACCUMULO-4050:
--------------------------------------
It's not clear to me what a "configuration container" means. Can one of you
describe this in more detail, maybe include an example that would outline how
the existing set of properties in ZK would appear with this suggested design?
Similarly, what defines a snapshot WRT the data stored in ZK? Using ZK
transaction id, maybe ZNode Version?
https://zookeeper.apache.org/doc/r3.1.2/zookeeperProgrammers.html#sc_timeInZk.
Any thought on how these snapshots could be used to enable follow-on work which
enables us to build a client API that can guarantee that Accumulo servers have
seen some configuration update?
> Serialize table configs into a single ZK node
> ---------------------------------------------
>
> Key: ACCUMULO-4050
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4050
> Project: Accumulo
> Issue Type: Sub-task
> Reporter: Christopher Tubbs
> Fix For: 2.0.0
>
>
> Use a single ZK node to store table configs, rather than split across
> multiple configs. This should make it easier to implement atomic changes to
> the configuration, and should simplify reading loading/saving configuration
> from/to ZooKeeper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
