[
https://issues.apache.org/jira/browse/ACCUMULO-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612920#comment-13612920
]
Keith Turner commented on ACCUMULO-650:
---------------------------------------
I think the per table config route would be best. Ultimately its still sored
in zookeeper, just in a more systematic way. This would involve adding an
enum to o.a.a.core.conf.Property
could still have API methods in table operation to set and get desc. These
would be similar to methods for manipulating locality groups and iterator
settings, which are also per table configs. Also, if you are still thinking of
adding something to create table, I still think we should add a NewTableConfig
method.
Would still have an option on tables command to list descriptions. Would we
still need the desc command? I do not really like the name, but I am uncertain
about the functionality. As far as functionality, it may make things slightly
simpler for the user rather than using the config command. Also having a
specific shell command for setting it puts a layer of indirection between the
implementation and the user.
> Add table descriptions
> ----------------------
>
> Key: ACCUMULO-650
> URL: https://issues.apache.org/jira/browse/ACCUMULO-650
> Project: Accumulo
> Issue Type: Improvement
> Components: master
> Reporter: John Vines
> Assignee: Kevin Faro
> Attachments: ACCUMULO-650-2.patch, ACCUMULO-650.patch
>
>
> We should add a table description field, probably in zookeeper, to store an
> optional field end users can use to provide their relevant information on the
> table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
