[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2842:
-------------------------------------
I came to find out that .lzo file libraries are may not have included by default in these VMs due to license differences. It is possible that lack of availability causing this issue?
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (TEIID-2868) Provide Aggregation function support in Accumulo translator
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2868:
-----------------------------------
Summary: Provide Aggregation function support in Accumulo translator
Key: TEIID-2868
URL: https://issues.jboss.org/browse/TEIID-2868
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 8.7
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Currently there is no support for SUM, AVG, MIN, MAX aggregation functions, it was not clear to me right now how these can be calculated in the partitioned way Accumulo deals with row contents. This needs to be investigated and implemented.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (TEIID-2867) Add function support to Accumulo translator
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2867:
-----------------------------------
Summary: Add function support to Accumulo translator
Key: TEIID-2867
URL: https://issues.jboss.org/browse/TEIID-2867
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 8.7
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Currently there is no function support available on Accumulo queries. Since Teiid query libraries will be available in Accumulo's classpath, it should be possible to push the system function support to the Accumulo layer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (TEIID-2863) Allow both gssapi and username/password authentication on the same transport
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2863:
---------------------------------------
Correct me if I'm wrong, but aren't we fairly close with our current structure. For example if we remove the LogonImpl.logon check of the authentication type and allow the JDBC client to determine on its own whether to make a gssapi login - won't that allow for gss and password authentications on the same transport (with logically similar changes on the ODBC side)?
I think we are also now, after the change to allow the vdb to declare a security domain, effectively moving toward treating the security domains setting on a transport to be interpreted as the default security domain (singular). We could do something similar with the idea of what the kerberos security domain is, that is declaring it in the vdb.xml. Or couldn't we just assume that the kerberos loginmodule is stacked in the same security domain?
> Allow both gssapi and username/password authentication on the same transport
> ----------------------------------------------------------------------------
>
> Key: TEIID-2863
> URL: https://issues.jboss.org/browse/TEIID-2863
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> With GSSAPI support enabled, username/password support on the same transport is effectively disabled. JDBC/ODBC should ideally support both on the same transport.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (TEIID-2863) Allow both gssapi and username/password authentication on the same transport
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2863:
-------------------------------------
Agree. Can think of reason why a transport need to be effectively combined with security at that intimate level. We can pull the security modules out of transport and define allowed security-domains at teiid configuration level that can be used across all the transports. But this would mean clients need to specify which allowed security-domain they would like to participate. We kind of do that for kerberoes.
> Allow both gssapi and username/password authentication on the same transport
> ----------------------------------------------------------------------------
>
> Key: TEIID-2863
> URL: https://issues.jboss.org/browse/TEIID-2863
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> With GSSAPI support enabled, username/password support on the same transport is effectively disabled. JDBC/ODBC should ideally support both on the same transport.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months