Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
From: Wyatt Frelot <Wyatt.Frelot@altamiracorp.com>
To: "user@accumulo.apache.org" <user@accumulo.apache.org>
Subject: Re: VFS class reloading
Thread-Topic: VFS class reloading
Thread-Index: AQHSQULvrCDRVmDyh02rlQ/3epQ3jg==
Date: Fri, 18 Nov 2016 02:25:32 +0000
Message-ID: <SN2PR01MB2045B40E64AABB812A72ABD5F3B00@SN2PR01MB2045.prod.exchangelabs.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: altamiracorp.com does not
 designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_SN2PR01MB2045B40E64AABB812A72ABD5F3B00SN2PR01MB2045prod_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2016 02:25:32.6257
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 45c06d49-d423-4624-9b9c-67ba304c554a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN2PR01MB2048
archived-at: Fri, 18 Nov 2016 02:26:27 -0000

--_000_SN2PR01MB2045B40E64AABB812A72ABD5F3B00SN2PR01MB2045prod_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Andrew,

I ran into this before and had to delete the VFS temp dir in the /tmp direc=
tory or where ever you place it.

Wyatt

On Nov 17, 2016 9:07 PM, Andrew Hulbert <ahulbert@ccri.com> wrote:
Hi all,

I've been noticing some weird behavior that occurs when trying to update
jars for custom classpaths using VFS. After updating jars in HDFS they
seem to still be cached even though I have deleted the namespace,
classpath context and jar in HDFS. After putting the jar at a different
path and creating a newly named context it worked.

Does this sound like the kind of issues that were fixed in the 1.6.6
release perhaps? I couldn't tell from the release notes. This cluster is
1.6.4 so perhaps its already fixed but figured I'd ask.

Thanks!

Andrew


--_000_SN2PR01MB2045B40E64AABB812A72ABD5F3B00SN2PR01MB2045prod_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<p dir=3D"ltr">Andrew,</p>
<p dir=3D"ltr">I ran into this before and had to delete the VFS temp dir in=
 the /tmp directory or where ever you place it.</p>
<p dir=3D"ltr">Wyatt</p>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Nov 17, 2016 9:07 PM, Andrew Hulbert &lt;ahul=
bert@ccri.com&gt; wrote:<br type=3D"attribution">
<blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<div><font size=3D"2"><span style=3D"font-size:10pt"></span></font>
<div>Hi all,<br>
<br>
I've been noticing some weird behavior that occurs when trying to update <b=
r>
jars for custom classpaths using VFS. After updating jars in HDFS they <br>
seem to still be cached even though I have deleted the namespace, <br>
classpath context and jar in HDFS. After putting the jar at a different <br=
>
path and creating a newly named context it worked.<br>
<br>
Does this sound like the kind of issues that were fixed in the 1.6.6 <br>
release perhaps? I couldn't tell from the release notes. This cluster is <b=
r>
1.6.4 so perhaps its already fixed but figured I'd ask.<br>
<br>
Thanks!<br>
<br>
Andrew<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_SN2PR01MB2045B40E64AABB812A72ABD5F3B00SN2PR01MB2045prod_--