QlikView not using TEZ ?

[#1]

Hi,

we have seen that only more complex (case, count,...) SELECT statements from Qlikview are being executed via TEZ.

All settings in Ambari are set to use TEZ by default.

Is this a Hortonworks issue?

Thank you!

[#2]

@Daniel Scheiner

In HDP, we have hive.execution.engine set to TEZ by default, hence all the complex queries gets executed via TEZ.

If you want, you can modify this property to 'mr'.

Hope this information helps.

[#3]

hive.execution.engine already is TEZ - we do not want MR due to its very very poor performance...

the problem appears to be with Qlik...

[#4]

@Daniel Scheiner

QlikView override the execution engine at the runtime. It uses a cost-based optimizer and based on its stats running the query with MR makes more sense. Reach to you QlikView support to learn the reasoning.

If this response helped, please vote and accept it as a best answer.

[#5 · Accepted solution]

i wanted to let you know the result of our analysis:

Qlik will use TEZ which considerably speeds up the request times - IF the SQL-statement is sufficiently complex! (i.e. use a count or sum command - as a dummy)

[#6]

@Daniel Scheiner

See my response from Nov 11 at 05:21 PM. It states the same, Cost Based Optimizer decides to use Tez for those queries where Tez can deliver faster that MR.