accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ACCUMULO-3632) Client configuration needs to be able to support server classpath
Date Tue, 03 Mar 2015 00:16:05 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344113#comment-14344113
] 

Josh Elser edited comment on ACCUMULO-3632 at 3/3/15 12:15 AM:
---------------------------------------------------------------

Good points from [~ctubbsii] on ACCUMULO-3631
{quote}
You're right, we don't have such a thing as "client classpath". Regarding this, one thing
that Keith Turner and I have recently been discussing (because it'd be convenient for Fluo)
is this problem of how a service can provide information to the client about a runtime "client
classpath". Typically, it's some subset of that service's own classpath, but it's not necessarily
a subset, and even if it were, figuring out which subset is difficult to do. Currently, a
"client-classpath" command in Accumulo would probably just return the location of "accumulo-core.jar"
and its dependencies (and transitive dependencies). In the future, it might just return that
of "accumulo-client.jar". But even then, these may not even be on a filesystem which the client
knows how to load from (e.g.: vfs), because the client may not have a classloader to handle
them.
{quote}


was (Author: elserj):
Good points from [~ctubbsii] on ACUMULO-3631
{quote}
You're right, we don't have such a thing as "client classpath". Regarding this, one thing
that Keith Turner and I have recently been discussing (because it'd be convenient for Fluo)
is this problem of how a service can provide information to the client about a runtime "client
classpath". Typically, it's some subset of that service's own classpath, but it's not necessarily
a subset, and even if it were, figuring out which subset is difficult to do. Currently, a
"client-classpath" command in Accumulo would probably just return the location of "accumulo-core.jar"
and its dependencies (and transitive dependencies). In the future, it might just return that
of "accumulo-client.jar". But even then, these may not even be on a filesystem which the client
knows how to load from (e.g.: vfs), because the client may not have a classloader to handle
them.
{quote}

> Client configuration needs to be able to support server classpath
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-3632
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3632
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: Josh Elser
>            Priority: Blocker
>             Fix For: 1.7.0
>
>
> Long-term fix for ACCUMULO-3631. When the accumulo-site.xml file is not available for
a client application to read (e.g. {{accumulo shell}}), the fallback is only on a hard-coded
string in {{AccumuloClassLoader.java}}.
> We should expose the same comma-separate regex to inform clients on where the necessary
jars to add to the classpath are located instead of relying on a hard-coded string in java
code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message