[
https://issues.apache.org/jira/browse/ACCUMULO-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185404#comment-13185404
]
Josh Elser commented on ACCUMULO-303:
-------------------------------------
Yes, you would get a ClassNotFoundException if you tried to set a formatter
that doesn't exist on the Accumulo classpath. Additionally, if there was one
previously set on the table, you would, I think, see the same
ClassNotFoundException when you try to switch to that table in the shell. This
could very easily happen if someone upgrades Accumulo and forgets to copy the
jars from the old Accumulo installation's lib/.
Is there a desired benefit to falling back onto the DefaultFormatter if the
specified formatter cannot be loaded (ClassNotFoundException,
ClassCastException, etc)? Having a missing formatter class set *will* mess up
all the scans until removed or the classpath being fixed; however,
(Batch)Scanners won't be affected.
> 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
