[JBoss JIRA] (TEIID-2846) Add procedure parameter native type extension property handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2846?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2846:
----------------------------------
Summary: Add procedure parameter native type extension property handling (was: Add native type to procedure parameters)
Assignee: Steven Hawkins (was: Barry LaFond)
Description: TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). TEIIDDES-1863 adds support as an extension property, which needs handling on the teiid side. (was: TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). That is not currently in the index metadata. This value would need to be captured on import and either a new index version used, or an extension property (with additional Teiid handling), or the vdb.xml can use alter statements to add an option.)
> Add procedure parameter native type extension property handling
> ---------------------------------------------------------------
>
> Key: TEIID-2846
> URL: https://issues.jboss.org/browse/TEIID-2846
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). TEIIDDES-1863 adds support as an extension property, which needs handling on the teiid side.
--
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, 11 months
[JBoss JIRA] (TEIID-2846) Add native type to procedure parameters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2846?page=com.atlassian.jira.plugin... ]
Steven Hawkins moved TEIIDDES-2043 to TEIID-2846:
-------------------------------------------------
Project: Teiid (was: Teiid Designer)
Key: TEIID-2846 (was: TEIIDDES-2043)
Component/s: Query Engine
(was: Teiid Integration)
(was: Modeling)
Fix Version/s: 8.7
(was: 8.5)
> Add native type to procedure parameters
> ---------------------------------------
>
> Key: TEIID-2846
> URL: https://issues.jboss.org/browse/TEIID-2846
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 8.7
>
>
> TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). That is not currently in the index metadata. This value would need to be captured on import and either a new index version used, or an extension property (with additional Teiid handling), or the vdb.xml can use alter statements to add an option.
--
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, 11 months
[JBoss JIRA] (TEIID-2844) remove unauthorized columns from select *
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2844?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2844:
---------------------------------------
Added a system property:
org.teiid.ignoreUnauthorizedAsterisk (to control the system wide default behavior - defaults to false) and a session property ignore_unauthorized_asterisk to set whether select * or a qualified asterisk will ignore unauthorized columns when expanded.
So typically a client would issue:
{code}
select teiid_session_set('ignore_unauthorized_asterisk', true)
{code}
to enable this behavior - which could be made part of the initialization if using a pool.
A couple of follow ons for this issue include - providing a high level way of enabling this feature from the client side and refining the server side logic to ensure that plans and results are cachable for authorization modified commands.
> remove unauthorized columns from select *
> -----------------------------------------
>
> Key: TEIID-2844
> URL: https://issues.jboss.org/browse/TEIID-2844
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> For ease of use with entitlement checking enabled, user queries with select * and *.tbl, should simply not treat unauthorized columns as selectable.
--
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, 11 months
[JBoss JIRA] (TEIID-2845) MongoDB: Join processing produces wrong results in some cases
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2845:
-----------------------------------
Summary: MongoDB: Join processing produces wrong results in some cases
Key: TEIID-2845
URL: https://issues.jboss.org/browse/TEIID-2845
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.7
When two or more tables are used to build single document in the MongoDB, depending upon the JOIN query used it may produce wrong results.
- support for inner is not turned ON, this should be allowed
- For example cross-join between parent and embedded table
- right-join between parent and embedded table
- depending upon the parent the ordering of left and right join
--
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, 11 months
[JBoss JIRA] (TEIID-2844) remove unauthorized columns from select *
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2844?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2844:
---------------------------------------
The approach here will be to handle this on the server side close to the AuthorizationValidationVisitor. The logic does support the concept of modifying the query as part of the authorization, so it should be straight-forward to remove the extra columns. However with the current logic it will inhibit plan and result set caching for modified queries - but that can be addressed later.
Possibilities for enabling this feature include:
a vdb property
a connection property
a server side configuration
a system property
I'm leaning toward using a vdb property and possibly a system property to control the system wide default behavior.
> remove unauthorized columns from select *
> -----------------------------------------
>
> Key: TEIID-2844
> URL: https://issues.jboss.org/browse/TEIID-2844
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> For ease of use with entitlement checking enabled, user queries with select * and *.tbl, should simply not treat unauthorized columns as selectable.
--
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, 11 months
[JBoss JIRA] (TEIID-2844) remove unauthorized columns from select *
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2844:
-------------------------------------
Summary: remove unauthorized columns from select *
Key: TEIID-2844
URL: https://issues.jboss.org/browse/TEIID-2844
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7
For ease of use with entitlement checking enabled, user queries with select * and *.tbl, should simply not treat unauthorized columns as selectable.
--
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, 11 months
[JBoss JIRA] (TEIID-2843) MongoDB: ClassCastException while doing JOIN based query
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2843:
-----------------------------------
Summary: MongoDB: ClassCastException while doing JOIN based query
Key: TEIID-2843
URL: https://issues.jboss.org/browse/TEIID-2843
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.7
With Schema like
{code}
CREATE FOREIGN TABLE Company (
name varchar(50) PRIMARY KEY,
description varchar(256)
) OPTIONS(UPDATABLE 'TRUE',"teiid_mongo:EMBEDDABLE" 'true');
CREATE FOREIGN TABLE Job (
jobId integer PRIMARY KEY,
description varchar(256),
companyname varchar(50),
FOREIGN KEY (companyname) REFERENCES Company (name)
) OPTIONS(UPDATABLE 'TRUE', "teiid_mongo:EMBEDDABLE" 'true');
CREATE FOREIGN TABLE Employee (
ename varchar(50) PRIMARY KEY,
jobId integer,
FOREIGN KEY (jobId) REFERENCES Job (jobId)
) OPTIONS(UPDATABLE 'TRUE');
{code}
then doing a single JOIN Query
{code}
select e.ename, c.name, j.description from Employee as e JOIN Job j ON e.jobId = j.jobId JOIN Company c ON j.companyname = c.name
{code}
fails with
{code}
14:22:05,271 ERROR [org.teiid.PROCESSOR] (Worker23_QueryProcessorQueue432) 258Se2CWMytI TEIID30019 Unexpected exception for request 258Se2CWMytI.28: java.lang.ClassCastException: org.teiid.language.Join cannot be cast to org.teiid.language.NamedTable
at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:419)
at org.teiid.language.Join.acceptVisitor(Join.java:66) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT]
at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT]
at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:95)
at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:106)
at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:482)
at org.teiid.language.Select.acceptVisitor(Select.java:103) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT]
at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT]
{code}
--
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, 11 months
[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Ivan Chan (JIRA)
Ivan Chan created TEIID-2842:
--------------------------------
Summary: 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: Steven Hawkins
Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption:
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
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, 11 months
[JBoss JIRA] (TEIID-2833) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2833?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-2833:
-------------------------------------
Assignee: Steven Hawkins
> While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2833
> URL: https://issues.jboss.org/browse/TEIID-2833
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.4
> Reporter: Barry LaFond
> Assignee: Steven Hawkins
> Fix For: 8.4.2, 8.7
>
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
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, 11 months