Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Received-SPF: pass (nike.apache.org: domain of hgunes@maprtech.com designates
 209.85.223.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <552578F7.2040807@maprtech.com>
References: <552578F7.2040807@maprtech.com>
Date: Thu, 9 Apr 2015 16:42:16 -0700
Message-ID: 
 <CANZQJAx3JGV4VJCZFdAgDtapGmOkV4jEPy3NvWtRfaRyOe3uAw@mail.gmail.com>
Subject: Re: SqlAccessor for just JDBC or for other use too?
From: Hanifi Gunes <hgunes@maprtech.com>
To: dev@drill.apache.org
Content-Type: multipart/alternative; boundary=001a113fc0aca78a740513533291

--001a113fc0aca78a740513533291
Content-Type: text/plain; charset=UTF-8

Are interface org.apache.drill.exec.vector.accessor.SqlAccessor and the
various classes that implement it intended only for the JDBC driver ...?
- I think so. The only consumer that I know of is DrillAccessorList, which
is also under jdbc. I don't see why this interface should live under exec.


-Hanifi

On Wed, Apr 8, 2015 at 11:52 AM, Daniel Barclay <dbarclay@maprtech.com>
wrote:

> Are interface org.apache.drill.exec.vector.accessor.SqlAccessor and the
> various classes that implement it intended only for the JDBC driver,
> or are they also intended to be used elsewhere?
>
> (If those are only for JDBC, they should (eventually) be moved into the
> JDBC module/subproject, in particular because some SqlAccessor code
> defines exceptions (in the java-exec module) that need to be coordinated
> with exceptions defined in the JDBC module).
>
> Daniel
> --
> Daniel Barclay
> MapR Technologies
>

--001a113fc0aca78a740513533291--