[
https://issues.jboss.org/browse/TEIID-4858?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4858:
---------------------------------------
Sorry for the delay in following up. Yes the source sql is in there - the difference it
that the slow log has an "order by" clause. There does appear to be references
to the order by operation not being well optimized on hive, so the simple solution would
be to disable order by support on the hive translator with an override:
{code}
<translator name="hive-restricted" type="hive" />
<property name="supportsOrderBy" value="false"/>
</translator>
{code}
And then reference the hive-restricted as the translator for your source.
It would be good to know if there are some other considerations in play here as I
wouldn't expect such a difference in performance. Do you see all sorts performing
poorly, or perhaps is it related to the data type, or some other factor?
hive translator is extremely slow
---------------------------------
Key: TEIID-4858
URL:
https://issues.jboss.org/browse/TEIID-4858
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.12.9.6_3
Environment: Tested against JDV 6.3.4 and the Cloudera quickstart 5.8 VM with the
Cloudera sample data loaded into hive
Reporter: Michael Echevarria
Assignee: Steven Hawkins
Attachments: fast.log, slow.log
When querying a table through the hive translator the results take close to 30 seconds to
return.
When querying a table through jdbc default results take under 1 second to return.
Both use the same underlying jboss server datasource.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)