Yeah, you can try to move over to the new ZKI constructor which takes
the ClientConfiguration directly. This has been present since like
1.7.0? Hopefully you're on that codebase :)
I still like the idea of a uniform way for client configuration parsing
(ala `--config ~/cluster1.conf`) for cons
On Thu, Jun 30, 2016 at 11:13 AM Mike Drob wrote:
> On Wed, Jun 29, 2016 at 5:24 PM, Christopher wrote:
>
> > To get rid of the warning, don't use ClientConfiguration.loadDefault().
> > Unit tests should be self-contained, and not use the user's environment.
> > Instead, use "new ClientConfigura
On Wed, Jun 29, 2016 at 5:24 PM, Christopher wrote:
> To get rid of the warning, don't use ClientConfiguration.loadDefault().
> Unit tests should be self-contained, and not use the user's environment.
> Instead, use "new ClientConfiguration()". If you're still getting that
> warning, we need to f
Was thinking about this a bit more. One of the problems with classpath is
that makes it a bit hard to pull different configs within the same JVM
(multiple client connections). It can also come from unexpected jars,
resulting in surprising behavior. And, it depends on the classloader used
at runtime
Being able to pull off of the classpath would certainly be nice when you
want to interact with multiple instances from the same host (thus requiring
different client confs).
Christopher's #1 point would also be a similar solution to the same
problem. I'm not sure if one or the other would be bette
To get rid of the warning, don't use ClientConfiguration.loadDefault().
Unit tests should be self-contained, and not use the user's environment.
Instead, use "new ClientConfiguration()". If you're still getting that
warning, we need to fix it. That constructor shouldn't be reading any
external conf
Devs,
Is there a reason that ClientConfiguration looks in the user's home
directory, and for environment variables ACCUMULO_CONF_DIR and
ACCUMULO_HOME to find a configuration but can't be controlled via system
properties or the classpath?
I'm working on some unit tests and keep seeing 'WARN
org.a
