accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3093) Shell scan command does not find formatter
Date Wed, 03 Sep 2014 00:17:51 GMT


Christopher Tubbs commented on ACCUMULO-3093:

The ClassLoader we provide is for tservers, and depends on reading classpath configuration
from the accumulo-site.xml file to be fully useful. That's configuration that clients, such
as the shell, are not expected to be able to read. Wouldn't it be simpler to just add these
extra formatters to the CLASSPATH environment when running the shell?

If the requirement is to load them out of HDFS, and the use of the -Djava.system.class.loader=some.basic.HDFSClassLoader
might be needed.

I think either of these two options are much simpler than more tightly coupling our built-in
class loading mechanisms to client code. It's not enough to -1 the patch, but I do think there's
simpler alternatives.

Another option is to work around the fact that clients don't/shouldn't have access to the
server config files, and instead add client classpath configuration options to the client
configuration file in the user's ~/.accumulo directory, but I'm not sure that's a good idea.
It's certainly more to maintain to duplicate the functionality of the CLASSPATH/-classpath
environment/parameter and "-Djava.system.class.loader".

> Shell scan command does not find formatter
> ------------------------------------------
>                 Key: ACCUMULO-3093
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 1.6.1
>         Environment: Accumulo 1.6.1-SNAPSHOT
>            Reporter: Dave Marion
>            Assignee: Dave Marion
>         Attachments: ACCUMULO-3093-1.patch
> The Scan command is not using the ContextManager to find the specified formatter class.
With a table using context classpath the following fails:
> {code}
> scan -t <table> -fm <formatterClass>
> {code}
> It also fails if the formatter is configured on table and a scan is issued.

This message was sent by Atlassian JIRA

View raw message