<user@accumulo.apache.org<mailto:user@accumulo.apache.org>>
Subject: Re: Accumulo Iterator painful development because TS don't pick up
changes to Jars
Also, turn the logging on the tservers up to DEBUG for
org.apache.accumulo.start.classloader.*. You should see a line in th
gCopy.action?projectId=129=Apache+Commons+VFS=dist/target
-Original Message-
From: dlmar...@comcast.net [mailto:dlmar...@comcast.net]
Sent: Thursday, October 29, 2015 8:04 PM
To: user@accumulo.apache.org
Subject: RE: Accumulo Iterator painful development because TS don't pick up
change
apache.org
Sent: Friday, October 30, 2015 11:57:27 AM
Subject: Re: Accumulo Iterator painful development because TS don't pick up
changes to Jars
Thanks for the help with this,
To be clear I believe we are using the context class loader for each of the
sets of tables, and we don’t see the jar r
2:22:53 PM
Subject: Re: Accumulo Iterator painful development because TS don't pick up
changes to Jars
Try replacing the vfs jar in lib with a 2.1-SNAPSHOT. Several issues have been
fixed, but one of them is that if more than one monitored resource changed then
it would miss some of them.
=129=Apache+Commons+VFS=dist/target
>
>
>> -Original Message-
>> From: dlmar...@comcast.net [mailto:dlmar...@comcast.net]
>> Sent: Thursday, October 29, 2015 8:04 PM
>> To: user@accumulo.apache.org
>> Subject: RE: Accumulo Iterator painful development be
er@accumulo.apache.org
> Subject: RE: Accumulo Iterator painful development because TS don't pick up
> changes to Jars
>
> Can you provide the relevant classpath sections of your accumulo-site.xml
> file?
>
> > -Original Message-
> > From: Rob Povey [mailto:r...@ma
Caveat I’m still running 1.6.2 internally here, and things may have changed and
I could simply “be doing it wrong”, or have missed the solution in the docs.
It’s also probably not a typical use case.
This is not really an issue for most day to day development, but our internal
testing process
