[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2842.
---------------------------------
> Impala/ HIVE2: Unsupported compress file
> -----------------------------------------
>
> Key: TEIID-2842
> URL: https://issues.jboss.org/browse/TEIID-2842
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Impala/HIVE2 with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption:
> {code}
> java.sql.SQLException: AnalysisException: Failed to load metadata for table: default.omniturelogs
> CAUSED BY: TableLoadingException: Failed to load metadata for table:
> omniturelogs
> CAUSED BY: RuntimeException: Compressed text files are not supported: hdfs://localhost.localdomain:8020/user/cloudera/omniturelogs/Omniture.0.tsv.gz
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:161)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:149)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:182)
> at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:246)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.teiid.translator.hive.HiveMetadataProcessor.addTable(HiveMetadataProcessor.java:112)
> at org.teiid.translator.hive.HiveMetadataProcessor.getConnectorMetadata(HiveMetadataProcessor.java:48)
>
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:311)
> ... 155 more
> {code}
> Maybe Teiid should call "DESCRIBE FORMATTED table" for table that contains compress file.
> Reference:
> http://grokbase.com/t/cloudera/impala-user/13b7c9apmx/impala-failed-to-qu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3050) allow for more incremental insert with iterator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3050?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3050.
---------------------------------
> allow for more incremental insert with iterator
> -----------------------------------------------
>
> Key: TEIID-3050
> URL: https://issues.jboss.org/browse/TEIID-3050
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> The current bulk insert logic assumes that it is avoiding a global transactions by fully reading the results before sending the tuplebuffer iterator to the source for processing, which can then just use a local transaction. However if we are already operating under a transaction or the user doesn't want a transaction (such as with a staging materialized view load) then the insert should happen more incrementally.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-2926) Import properties definitions provided via getTranslatorDefinitions() call do not return default values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2926?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2926.
---------------------------------
> Import properties definitions provided via getTranslatorDefinitions() call do not return default values
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2926
> URL: https://issues.jboss.org/browse/TEIID-2926
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.7
> Reporter: Barry LaFond
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.7
>
>
> While enabling runtime-provided *IMPORT* properties for the Teiid Connection importer in Designer, I noticed that the property definitions that got returned did not include a *defaultValue*.
> The feature will work as is, however, users may be needlessly setting some properties to default (like most booleans) to false.
> This is also inconsistent with the Translator Override property definitions. The majority of those are defined with default values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months