Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAAL5oQJ=Be8qYw9TG0hJ7r7g3TrkMiMLVU9wBfb_bKXEhmfHhg@mail.gmail.com>
References: 
 <CAFno-uPXQmqHra=NmFHWx6X4LqoHi4ea9mBynVXTC99VxMP0xw@mail.gmail.com>
	<CAAL5oQJ=Be8qYw9TG0hJ7r7g3TrkMiMLVU9wBfb_bKXEhmfHhg@mail.gmail.com>
Date: Sun, 15 Nov 2015 12:50:49 -0800
Message-ID: 
 <CAFno-uP9Aqof+jKekh24NVUKit9PRQM8Xeq9RCfr7JeOBnPb1A@mail.gmail.com>
Subject: Re: No s3 access without jars from hadoop
From: Nathan Griffith <ngriffith@dremio.com>
To: dev@drill.apache.org
Content-Type: text/plain; charset=UTF-8

For old-style s3n support you didn't need jar files from a Hadoop
binary tarball --- just jets3t. So essentially someone wanting to use
s3 in Drill 1.3 would need to pull down and unpack a 200 MB file just
to grab a couple dependencies from it.

On Sat, Nov 14, 2015 at 10:39 PM, Tomer Shiran <tshiran@dremio.com> wrote:
> When you say "problem" - it seems like more work was required previously
> (with s3n). Or am I misunderstanding?
>
>
>
> On Fri, Nov 13, 2015 at 9:55 AM, Nathan Griffith <ngriffith@dremio.com>
> wrote:
>
>> Hi all,
>>
>> Currently if you want to use s3a in Drill 1.3.0 you need to copy a
>> couple files from the Hadoop binary distribution into jars/3rdparty.
>> For s3n you need those *and* the old jets3t dependency.
>>
>> Just wanted to highlight this problem since it seems like an important
>> but easy fix. The JIRA I filed about it is here:
>> https://issues.apache.org/jira/browse/DRILL-4063
>>
>> Best,
>> Nathan
>>
>
>
>
> --
> Tomer Shiran
> CEO and Co-Founder, Dremio