[
https://issues.apache.org/jira/browse/ACCUMULO-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185393#comment-13185393
]
Dave Marion commented on ACCUMULO-303:
--------------------------------------
Initially the formatter option only applied to the session. This allowed a
developer to create a formatter specific to his/her table and drop the jar into
the lib/ext directory. I like the idea of making it part of the table
configuration. But, what happens if you make it part of the table configuration
and the jar does not exist for some reason? I assume that it only affects the
shell and either the jar would have to placed back into the classpath or the
configuration option removed.
> Implement per-table persistent formatters
> -----------------------------------------
>
> Key: ACCUMULO-303
> URL: https://issues.apache.org/jira/browse/ACCUMULO-303
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: Josh Elser
> Assignee: Billie Rinaldi
> Priority: Minor
> Labels: formatter,, shell
> Fix For: 1.4.0
>
> Attachments: ACCUMULO-303.patch
>
>
> In the Accumulo shell, Formatters can only be set on a per-shell-session
> basis. Setting a custom Formatter in a shell session designed for a specific
> table must be removed when scanning a table of a different format.
> Implement a method to persist a formatter class on a table across shell
> sessions that encourages the creation and usage of Formatters
--
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
