drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jack Ingoldsby <jack.ingold...@gmail.com>
Subject Re: 1.11 Release date
Date Mon, 19 Jun 2017 20:07:55 GMT
Thanks, I created an issue in JIRA.
https://issues.apache.org/jira/browse/DRILL-5596

On Mon, Jun 19, 2017 at 1:40 PM, Abhishek Girish <agirish@apache.org> wrote:

> Thanks for sharing details! It's always helpful to know the context in any
> request. It's also exciting to learn about new Drill use-cases.
>
> Regarding the release timeline, I hope someone will start a thread in the
> Dev mailing list soon. Or for someone in the PMC to comment on it, here.
>
> I think you should file a JIRA for the S3 regions issue. It's a useful
> reference for others encountering similar issues. We should also document
> it, until it's resolved.
>
> -Abhishek
>
> On Mon, Jun 19, 2017 at 7:55 AM, Jack Ingoldsby <jack.ingoldsby@gmail.com>
> wrote:
>
> > Hi,
> > Here is the JIRA for the JDBC issue, BTW.
> > https://issues.apache.org/jira/browse/DRILL-5373
> >
> > Regards,
> > Jack
> >
> > On Mon, Jun 19, 2017 at 10:46 AM, Jack Ingoldsby <
> jack.ingoldsby@gmail.com
> > >
> > wrote:
> >
> > > Hi,
> > > Thanks, I appreciate the offer to help to help very much.
> > > So, the situation is that I'm working as a presales engineer at a
> > business
> > > intelligence tech startup (not really a startup any more, they have
> c300
> > > employees).
> > > We provide an easily installed tool to enable business users to mash up
> > > data from various sources and perform analysis.
> > > I wanted to see if we could use Drill to get data from S3 as an
> > additional
> > > data source.
> > >
> > > Thanks to help from the user group was able to do so, used Drill ODBC
> to
> > > load 37 million records successfully, so have proof of concept.
> > >
> > > Currently the standard architecture  is Analytic Server, Web Server all
> > > installed on a single Windows server. We are looking to provide a Linux
> > > offering in the coming months,
> > >
> > > I'd like to get the product team to buy into using Apache Drill as a
> > > standard data source.  So a couple of issues
> > >
> > >    1. Need to get JDBC up and running, (ideally on a Windows embedded
> > >    instance for testing purposes prior to the Linux release)
> > >    2. I think there is an issue connecting to different regions of AWS
> > >    S3. I can connect successfully to N Virgina, but not to Ohio, I
> think
> > >    because of signature versions (http://drill-user.incubator.
> > >    apache.narkive.com/Ue0zF3kp/s3-storage-plugin-not-working-
> > >    for-signature-v4-regions
> > >    <http://drill-user.incubator.apache.narkive.com/Ue0zF3kp/
> > s3-storage-plugin-not-working-for-signature-v4-regions>
> > >    )
> > >
> > > So, I think rather than using a forked Drill version for short term
> > > purposes, I'd like to present the product team with with a demo using
> an
> > > official Drill release where these issues are addressed, even if that
> is
> > > weeks or months away, hence my interest in likely release schedule
> > >
> > > Thanks,
> > > Jack
> > >
> > >
> > > On Sun, Jun 18, 2017 at 12:49 PM, Abhishek Girish <agirish@apache.org>
> > > wrote:
> > >
> > >> That's a good question - however, I don't think it hasn't been
> discussed
> > >> yet.
> > >>
> > >> If not a 1.11.0 release right away, we should consider having a 1.10.1
> > >> minor release.
> > >>
> > >> Coming to your question on issue with Windows embedded JDBC, if you
> see
> > >> that's now been resolved (is there a JIRA?), you could build from
> source
> > >> (Apache master) and try it out. Let us know if you need help with
> that.
> > >>
> > >> On Sun, Jun 18, 2017 at 9:33 AM, Jack Ingoldsby <
> > jack.ingoldsby@gmail.com
> > >> >
> > >> wrote:
> > >>
> > >> > Hi,
> > >> > Is there a likely release date for 1.11?
> > >> > I hit a known issue with Windows embedded JDBC, looks like it will
> > have
> > >> > been addressed in 1.11.
> > >> > Thanks,
> > >> > Jack
> > >> >
> > >>
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message