Steve

The Apache distribution of Drill does not have a open source version of
ODBC driver.  There is however a JDBC driver that is available that you can
use to connect to Drill from BI tools. The ODBC driver you mentioned below
is provided by Simba and the license restrictions indicate that it
is licensed by MapR.

Regarding your other question, yes, Drill ships with MapR distribution of
Hadoop.
For more info refer to https://www.mapr.com/products/apache-drill


thanks
Neeraja


On Tue, Jul 19, 2016 at 3:27 PM, Steve Warren <swar...@myvest.com> wrote:

> I noticed the MapR ODBC driver contains the following restriction in their
> license agreement.
>
> *"Restrictions*. Customer shall only use the Software in conjunction with
> the MapR Product and not on a standalone basis.  For avoidance of doubt,
> Customer is not authorized to use the Software with other distributions for
> Apache Hadoop. For purposes of this Agreement, the “MapR Product” shall
> mean the MapR Distribution for Apache Hadoop."
>
> This seems problematic. Is there another ODBC driver that works with drill?
> Does MapR intend to loosen the restrictions on this product and/or open
> source it?
>
> Does Drill even ship with the MapR's distribution of Apache Hadoop?
>
> --
> Confidentiality Notice and Disclaimer:  The information contained in this
> e-mail and any attachments, is not transmitted by secure means and may also
> be legally privileged and confidential.  If you are not an intended
> recipient, you are hereby notified that any dissemination, distribution, or
> copying of this e-mail is strictly prohibited.  If you have received this
> e-mail in error, please notify the sender and permanently delete the e-mail
> and any attachments immediately. You should not retain, copy or use this
> e-mail or any attachment for any purpose, nor disclose all or any part of
> the contents to any other person. MyVest Corporation, MyVest Advisors and
> their affiliates accept no responsibility for any unauthorized access
> and/or alteration or dissemination of this communication nor for any
> consequence based on or arising out of the use of information that may have
> been illegitimately accessed or altered.
>

Reply via email to