[JBoss JIRA] (TEIID-2575) Hive's Binary Type Handling by Teiid
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2575?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2575:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=984852
> Hive's Binary Type Handling by Teiid
> ------------------------------------
>
> Key: TEIID-2575
> URL: https://issues.jboss.org/browse/TEIID-2575
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.4.1
> Reporter: Filip Nguyen
> Assignee: Ramesh Reddy
>
> I have simple Hive table (column definition: "OBJECTVALUE BINARY" see [1]). When running a simple query "statement.executeQuery("select OBJECTVALUE from smalla;");" I am getting [2]. When I run it simply from Hive console it works ok.
> [1]
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Types
> [2]
> {noformat}
> org.teiid.jdbc.TeiidSQLException: TEIID10076 Invalid conversion from type class org.teiid.core.types.BinaryType with value 'EFBFBDEFBFBDEFBFBD' to type class java.lang.String
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:516)
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:130)
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:37)
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75)
> at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:235)
> at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:271)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:102)
> at $Proxy6.read(Unknown Source)
> at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:370)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:525)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> at org.jboss.qe.HiveTranslatorTest.simpleQueryTest(HiveTranslatorTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46)
> at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.teiid.core.types.TransformationException: TEIID10076 Invalid conversion from type class org.teiid.core.types.BinaryType with value 'EFBFBDEFBFBDEFBFBD' to type class java.lang.String
> at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:891)
> at org.teiid.dqp.internal.process.DataTierTupleSource.correctTypes(DataTierTupleSource.java:186)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:326)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:306)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:149)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:149)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:112)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214)
> {noformat}
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2578) Provide API to add schema elements at translator layer
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2578:
---------------------------------------
> The motivation for the feature is to provide a more comprehensive materialization feature.
I'm not sure if this effort is necessarily tied to materialization as the current mechanism for bringing in source tables as temp tables is sufficient since the they can be pulled in at a global scope. Alternatively if you want to add materialized tables to Teiid schemas it seems like this would be done at load time.
> Provide API to add schema elements at translator layer
> ------------------------------------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.5
>
>
> Currently the translator API is can expose the source schema they represent, however there are no facilities to create the schema elements like
> * table
> * procedure
> the function support is available, but this needs be re-factored under this interface (may be this can be a follow on task)
> Using this feature, query engine should be able to ad-hoc create tables or procedures. The motivation for the feature is to provide a more comprehensive materialization feature.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2581) vararg stored procedure error with empty call
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2581?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2581.
-----------------------------------
Resolution: Done
Updated the named parameter resolving to check if the missing parameter is varargs.
> vararg stored procedure error with empty call
> ---------------------------------------------
>
> Key: TEIID-2581
> URL: https://issues.jboss.org/browse/TEIID-2581
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> A stored procedure with a single in parameter that is marked as varargs will throw an error in the LanguageBridgeFactory because the resolver will have resolved the procedure as if using named parameters and will pass a null array.
> For example:
> create foreign procedure proc (VARIADIC z integer) returns (x string);
> call proc() //will fail
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2579) Have SSL connector support for plaintext passwords
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2579?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2579:
----------------------------------
Issue Type: Quality Risk (was: Feature Request)
Fix Version/s: 8.4.1
8.5
Affects: Documentation (Ref Guide, User Guide, etc.)
> Have SSL connector support for plaintext passwords
> --------------------------------------------------
>
> Key: TEIID-2579
> URL: https://issues.jboss.org/browse/TEIID-2579
> Project: Teiid
> Issue Type: Quality Risk
> Affects Versions: 8.4
> Reporter: Graeme Gillies
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> Hi,
> At the moment the ssl configuration on the teiid jdbc and odbc connectors only supports keeping the keystore password in jboss vault. Can it please also support plain text passwords, and the documentation be updated to reflect this (at the moment the docs are incorrect as they have no mention of vault).
> Regards,
> Graeme
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2581) vararg stored procedure error with empty call
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2581:
-------------------------------------
Summary: vararg stored procedure error with empty call
Key: TEIID-2581
URL: https://issues.jboss.org/browse/TEIID-2581
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
A stored procedure with a single in parameter that is marked as varargs will throw an error in the LanguageBridgeFactory because the resolver will have resolved the procedure as if using named parameters and will pass a null array.
For example:
create foreign procedure proc (VARIADIC z integer) returns (x string);
call proc() //will fail
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2580) xsi:nil is not honored by xmltable
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2580?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2580.
-----------------------------------
Resolution: Done
Saxon does not mark elements as nillable on unvalidated documents, so the logic has to directly check the attribute - however the projection filtering was removing the attribute information, so the path map logic was updated as well.
> xsi:nil is not honored by xmltable
> ----------------------------------
>
> Key: TEIID-2580
> URL: https://issues.jboss.org/browse/TEIID-2580
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> If an element is returnable by xmltable, but marked as nil more than likely an exception will be produced when attempting to convert the empty string value to a result.
> For example:
> {code}
> select * from xmltable('/a/b' passing convert('<a xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><b xsi:nil="true"/><b>1</b></a>', xml) columns val integer path '.') as x
> {code}
> will error converting the first b element to an integer.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2580) xsi:nil is not honored by xmltable
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2580?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2580:
----------------------------------
Description:
If an element is returnable by xmltable, but marked as nil more than likely an exception will be produced when attempting to convert the empty string value to a result.
For example:
{code}
select * from xmltable('/a/b' passing convert('<a xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><b xsi:nil="true"/><b>1</b></a>', xml) columns val integer path '.') as x
{code}
will error converting the first b element to an integer.
was:
If an element is returnable by xmltable, but marked as nil more than likely an exception will be produced when attempting to convert the empty string value to a result.
For example:
{code}
select * from xmltable('/a/b' passing convert('<a xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><b xsi:nil=\"true\" xsi:type=\"xs:int\"/><b>1</b></a>', xml) columns val integer path '.') as x
{code}
will error converting the first b element to an integer.
> xsi:nil is not honored by xmltable
> ----------------------------------
>
> Key: TEIID-2580
> URL: https://issues.jboss.org/browse/TEIID-2580
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> If an element is returnable by xmltable, but marked as nil more than likely an exception will be produced when attempting to convert the empty string value to a result.
> For example:
> {code}
> select * from xmltable('/a/b' passing convert('<a xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><b xsi:nil="true"/><b>1</b></a>', xml) columns val integer path '.') as x
> {code}
> will error converting the first b element to an integer.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2580) xsi:nil is not honored by xmltable
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2580:
-------------------------------------
Summary: xsi:nil is not honored by xmltable
Key: TEIID-2580
URL: https://issues.jboss.org/browse/TEIID-2580
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
If an element is returnable by xmltable, but marked as nil more than likely an exception will be produced when attempting to convert the empty string value to a result.
For example:
{code}
select * from xmltable('/a/b' passing convert('<a xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><b xsi:nil=\"true\" xsi:type=\"xs:int\"/><b>1</b></a>', xml) columns val integer path '.') as x
{code}
will error converting the first b element to an integer.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2579) Have SSL connector support for plaintext passwords
by Graeme Gillies (JIRA)
Graeme Gillies created TEIID-2579:
-------------------------------------
Summary: Have SSL connector support for plaintext passwords
Key: TEIID-2579
URL: https://issues.jboss.org/browse/TEIID-2579
Project: Teiid
Issue Type: Feature Request
Affects Versions: 8.4
Reporter: Graeme Gillies
Assignee: Steven Hawkins
Hi,
At the moment the ssl configuration on the teiid jdbc and odbc connectors only supports keeping the keystore password in jboss vault. Can it please also support plain text passwords, and the documentation be updated to reflect this (at the moment the docs are incorrect as they have no mention of vault).
Regards,
Graeme
--
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
11 years, 5 months