October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2754) DatabaseMetaData reports views as tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2754?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2754: --------------------------------------- 9.0 will change the default for reportAsViews to true. > DatabaseMetaData reports views as tables > ---------------------------------------- > > Key: TEIID-2754 > URL: https://issues.jboss.org/browse/TEIID-2754 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 9.0 > > > The client already has a check for isVirtual & system table type to report a "system view". > We have a "View" type in our metadata, but we generally do not use it in our metadata code. > So we either could set the view type on the server (although this seems like a broad change) or add another DatabaseMetaData check for isVirtual & table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2754) DatabaseMetaData reports views as tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2754?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2754: ---------------------------------- Fix Version/s: 9.0 > DatabaseMetaData reports views as tables > ---------------------------------------- > > Key: TEIID-2754 > URL: https://issues.jboss.org/browse/TEIID-2754 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 9.0 > > > The client already has a check for isVirtual & system table type to report a "system view". > We have a "View" type in our metadata, but we generally do not use it in our metadata code. > So we either could set the view type on the server (although this seems like a broad change) or add another DatabaseMetaData check for isVirtual & table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3714) update webservice example to show how to invoke wsdl base procedures and swagger json based procedures

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3714?page=com.atlassian.jira.plugin... ] Kylin Soong resolved TEIID-3714. -------------------------------- Resolution: Done > update webservice example to show how to invoke wsdl base procedures and swagger json based procedures > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-3714 > URL: https://issues.jboss.org/browse/TEIID-3714 > Project: Teiid > Issue Type: Feature Request > Reporter: Kylin Soong > Assignee: Kylin Soong > > Teiid WS translator support invoke WSDL based procedure via WSDLMetadatProcessor and WSWSDLProcedureExecution; TEIID-3520 will add similar function for rest webservice. This issue will update webservice example to show: > * how to invoke wsdl base procedures > * how to invoke swagger json based procedures -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3743) Multiple Count Distinct Columns Fails for Impala

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3743?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3743. ----------------------------------- Fix Version/s: 8.12 Resolution: Done Addressed with the cross join workaround described. The fix will be in 8.12 Final. > Multiple Count Distinct Columns Fails for Impala > ------------------------------------------------ > > Key: TEIID-3743 > URL: https://issues.jboss.org/browse/TEIID-3743 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.11.4 > Reporter: Scott Wallace > Assignee: Steven Hawkins > Fix For: 8.12 > > > Teiid Impala translator incorrectly allows multiple count distinct columns, which fails to execute since it is not supported by Impala. > Per Cloudera documentation: > {quote}By default, Impala only allows a single COUNT(DISTINCT columns) expression in each query. > To produce the same result as multiple COUNT(DISTINCT) expressions, you can use the following technique for queries involving a single table: > select v1.c1 result1, v2.c1 result2 from (select count(distinct col1) as c1 from t1) v1 cross join (select count(distinct col2) as c1 from t1) v2;{quote} > The Teiid-Impala translator should ideally rewrite the query as necessary so that the query does not fail executing multiple count distincts against Impala. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3745) Procedure input parsing enhancements

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3745: ----------------------------------- Summary: Procedure input parsing enhancements Key: TEIID-3745 URL: https://issues.jboss.org/browse/TEIID-3745 Project: Teiid Issue Type: Enhancement Components: OData Affects Versions: 8.11 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.12 Based on Olingo 4.0.0 release, the procedure parameter parsing needs to be re-visited as some of it is written out side the framework in Teiid. Also handling of the Stream object (XML Document) input may be still outside the specification compliance for time being, as specification only allows procedure with Edm.Stream objects as Bound operations, and Teiid procedures are all UnBound operations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3742) out of range values not checked in sum aggregate

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3742?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3742. ----------------------------------- Resolution: Done Reused the plus method in the sum aggregate. > out of range values not checked in sum aggregate > ------------------------------------------------ > > Key: TEIID-3742 > URL: https://issues.jboss.org/browse/TEIID-3742 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > The sum aggregate may overflow, so there should be an explicit check. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3744) WS: PATCH Method is not supported

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3744?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3744. --------------------------------- Resolution: Done Labels: GA (was: ) Added CXF asynchronous http execution libraries, then modified the WS connection, such that it switches to async execution when PATCH based invocation is issued. > WS: PATCH Method is not supported > --------------------------------- > > Key: TEIID-3744 > URL: https://issues.jboss.org/browse/TEIID-3744 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: GA > Fix For: 8.12 > > > PATCH based HTTP method is currently not supported by the Web Services translator. The support in CXF is also NOT readily available. > In order to support PATCH method, CXF needs to use Apache HttpAsync client libraries. > http://cxf.apache.org/docs/asynchronous-client-http-transport.html > http://stackoverflow.com/questions/32067687/how-to-use-patch-method-in-cxf -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3744) WS: PATCH Method is not supported

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3744: ----------------------------------- Summary: WS: PATCH Method is not supported Key: TEIID-3744 URL: https://issues.jboss.org/browse/TEIID-3744 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.12 PATCH based HTTP method is currently not supported by the Web Services translator. The support in CXF is also NOT readily available. In order to support PATCH method, CXF needs to use Apache HttpAsync client libraries. http://cxf.apache.org/docs/asynchronous-client-http-transport.html http://stackoverflow.com/questions/32067687/how-to-use-patch-method-in-cxf -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3642) RhinoScriptEngineFactory be removed in Java 8

by jie tao (JIRA)

[ https://issues.jboss.org/browse/TEIID-3642?page=com.atlassian.jira.plugin... ] jie tao commented on TEIID-3642: -------------------------------- thx. I fixed the problem. Reason is: I did not create the user. > RhinoScriptEngineFactory be removed in Java 8 > ---------------------------------------------- > > Key: TEIID-3642 > URL: https://issues.jboss.org/browse/TEIID-3642 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2, 8.12 > Environment: * DV 6.2.0.ER4 > * Java 1.8.0_25 > Reporter: Kylin Soong > Assignee: Steven Hawkins > > RhinoScriptEngineFactory be removed in Java 8, this cause OData war deploy output Error: > {code} > 09:30:51,315 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-6) JBAS015868: Deployment "deployment.teiid-odata-8.7.1.6_2-redhat-2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice. > 09:30:51,424 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,429 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,505 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,513 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,583 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > {code} > *OData war* depend on *org.joda.time*, *org.joda.time* depend on *RhinoScriptEngineFactory*, due to RhinoScriptEngineFactory be removed in Java 8, so stderr output in console. > h3. how to reproduce > Start DV 6.2 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3642) RhinoScriptEngineFactory be removed in Java 8

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3642?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3642: ------------------------------------ can you post that to the community, would prefer not to continue this discussion on the jira. > RhinoScriptEngineFactory be removed in Java 8 > ---------------------------------------------- > > Key: TEIID-3642 > URL: https://issues.jboss.org/browse/TEIID-3642 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2, 8.12 > Environment: * DV 6.2.0.ER4 > * Java 1.8.0_25 > Reporter: Kylin Soong > Assignee: Steven Hawkins > > RhinoScriptEngineFactory be removed in Java 8, this cause OData war deploy output Error: > {code} > 09:30:51,315 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-6) JBAS015868: Deployment "deployment.teiid-odata-8.7.1.6_2-redhat-2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice. > 09:30:51,424 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,429 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,505 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,513 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,583 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > {code} > *OData war* depend on *org.joda.time*, *org.joda.time* depend on *RhinoScriptEngineFactory*, due to RhinoScriptEngineFactory be removed in Java 8, so stderr output in console. > h3. how to reproduce > Start DV 6.2 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015