You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@impala.apache.org by Tim Armstrong <ta...@cloudera.com> on 2016/04/15 02:47:41 UTC

Re: What are the intentions of Cloudera for Jdbc and Impala?

Moving to Apache Incubator list, impala-user@cloudera.org is going away.

The Simba drivers are not part of the Apache Incubator project and are
developed by Simba, not by Impala contributors. We implement the open HS2
protocol, so as you noted it's possible to connect to Impala with a variety
of drivers.

The core of Impala is open source but we do have proprietary components in
the ecosystem, similar to many other open source projects.

On Mon, Apr 11, 2016 at 10:40 AM, Randy Hammon <yo...@gmail.com> wrote:

> Hi!
> I am implementing the TCLIServer protocol and use the hiveserver2 jdbc
> driver. The Hive code as well as Impala server implementation has helped as
> a reference.
> I started playing with the newish simba-impala jdbc drivers. I was a
> little surprised that they seem to be proprietary drivers. How does that
> line up with being an incubating apache project?
> They certainly are impala specific as a fair amount of impala-only query
> processing has been moved into the driver and I would guess it's not usable
> as a hiveserver2
> jdbc driver. Seems great to have clear, focused, source code for jdbc
> without all the other hive stuff, but you could have done this with the
> existing hiveserver2 code.
> I saw a post somewhere that someone had already done it minus the kerberos
> part. They said they could add it in a weekend.
>
> Where is Cloudera going with this? Will the source code for the driver be
> published?
>
> Thanks
> Randy
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Impala User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to impala-user+unsubscribe@cloudera.org.
>