When is the release date for 1.2? Sent from my iPhone
> On Oct 1, 2015, at 5:22 PM, Daniel Barclay <[email protected]> wrote: > > Dhruv Gohil wrote: >>> I think the JDBC driver didn't have any >>> "known" issues in 1.1 >> > DRILL-3632 seems to be a blocker on 1.1.0 . > > That is fixed now in master (for Drill 1.2) (via DRILL-3566). > > Daniel > > >> >>> On Thursday 01 October 2015 11:06 AM, Daniel Barclay wrote: >>> Hakim, >>> >>> Abdel Hakim Deneche wrote: >>>> Hi Nikunj, >>>> >>>> What kind of dependcy issues you are seeing ? DRILL-3589 purpose was to >>>> improve Drill JDBC dependencies but I think the JDBC driver didn't have any >>>> "known" issues in 1.1 >>> >>> Actually, it did have dependency problems, especially library-conflict >>> problems, reported against it. See some of DRILL-3589's linked JIRA >>> reports (i.e., DRILL-3502, DRILL-3581, and DRILL-3784.) >>> >>> Daniel >>> >>>> >>>> Thanks >>>> >>>> On Wed, Sep 30, 2015 at 12:02 PM, Daniel Barclay <[email protected]> >>>> wrote: >>>> >>>>> Nikunj Thakkar wrote: >>>>> >>>>>> ... >>>>>> I'm using drill v1.1.0 in my current setup and facing dependency issues. >>>>>> I >>>>>> came across https://issues.apache.org/jira/browse/DRILL-3589 which seems >>>>>> to >>>>>> be the root cause of my problem. Issue got resolved in v1.2. Can I use it >>>>>> with 1.1 release? Has anyone tried this? >>>>> >>>>> I think that it happens to work, but it's definitely not known to work, so >>>>> you'll have to check. >>>>> >>>>> (I think I tried that combination incidentally as part of doing something >>>>> else, so it wasn't a solid test, just connecting and a few basic queries). >>>>> >>>>> Daniel >>>>> >>>>> -- >>>>> Daniel Barclay >>>>> MapR Technologies > > > -- > Daniel Barclay > MapR Technologies ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
