The problem with Tableau is that it tries to optimize the code itself which really does not work for something that uses generic ODBC 3. We used to have it with Tableau connecting to Oracle TimesTen IMDB (that did not have its dedicated ODBC driver in Tableau so had to use ODBC 2, even an older version). I am sure until Tableau knows how to optimize the query for Hive, it would not really work. Optimizing joins in Hive etc at the moment I am not sure.
I checked Tableau connectivity but they seem to suggest drivers from Hortonworks and Cloudera and also their propriety Hadoop tools. Cheers, Dr Mich Talebzadeh LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>* http://talebzadehmich.wordpress.com On 10 March 2016 at 23:49, Gopal Vijayaraghavan <gop...@apache.org> wrote: > > > If yes, maybe one should think about an open source one, which is > >reliable and supports a richer set of Odbc functionality. > > I had a similar thought last week, which ended up with me discovering that > the hive/odbc folder is full of dead code. > > I'm going to rm -rvf odbc/ with > https://issues.apache.org/jira/browse/HIVE-13234 > > > I can see already some improvements that could be made especially for > >visual analytic tools, such as Tableau or Spotfire. > > The ODBC capabilities bitsets need to be upgraded for something like > Tableau's "Add to Context" to create a temporary table instead of running > the full query everytime, for instance. > > Cheers, > Gopal > > >
