Hi usersFor people facing the same problem, here the workaround in case Tableau
Quick filters does not populate. You need to enforce the column data type
manually and not let Tableau do it by itself. Here is 2 approaches to do it :
- create a raw view on top of a parquet file with typed fields
Hello Driller,
I'm facing issues using the Filter function of Tableau with Drill : Tableau
always populates values of the filter with null.The action is translated into
2 queries within Drill :
SELECT * FROM (SELECT field FROM Table GROUP BY field ORDER BY field ASC) T
LIMIT 0
SELECT field
I think Tableau also uses the first query to fetch the structure /
metadata of the expected result set.
We have often eliminated performance issues using Tableau by hiding
the structure of queries by putting them in database views. Could that
be a possible solution here?
On 17 Aug 2015, at
Hi Matt,
We also hide as far as possible queries by creating tables and views within
Drill. As a result we only have one massive table within Tableau. This approach
proved to be efficient with this kind of BI tools.
My specific issue is about dynamic filtering within Tableau on a dimension
The first query is meant to only capture the column info of the table/view,
thus limit 0.
What is the result of the second query of you execute it from sqlline?
What is the underlying datasource of Table in the queries?
Have not noticed the issue when working with Tableau 9.0 and Drill.
