June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3041) Add support for xml document models in ddl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3041?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3041. --------------------------------- We will not pursue a direct representation of xml/xsd models in ddl. > Add support for xml document models in ddl > ------------------------------------------ > > Key: TEIID-3041 > URL: https://issues.jboss.org/browse/TEIID-3041 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > xml document model support was left out of the initial ddl design, but since the feature has not yet been retargeted from designer we should add support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2806) Accumulo Connector: Handling Authorizations with NULL value

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2806?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2806. --------------------------------- > Accumulo Connector: Handling Authorizations with NULL value > ----------------------------------------------------------- > > Key: TEIID-2806 > URL: https://issues.jboss.org/browse/TEIID-2806 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.7 > > > Currently the connector cannot handle null authorizations or roles left blank. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-189) Temp tables should maintain their costing metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-189?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-189. -------------------------------- Assignee: Steven Hawkins > Temp tables should maintain their costing metadata > -------------------------------------------------- > > Key: TEIID-189 > URL: https://issues.jboss.org/browse/TEIID-189 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.2 > > > Defect Tracker #24522: Temp table cardinality is currently only used for staging tables. It would also be generally useful for ad hoc queries to have the TempTableStoreImpl maintain the cardinality of the tables. Other costing information could actually be incorrect now (such as column min/max) depending upon what has been selected into a temp table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-744) Inversion of convert(string, ...) and parseXXX(string, ...) is not always possible.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-744?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-744. -------------------------------- > Inversion of convert(string, ...) and parseXXX(string, ...) is not always possible. > ----------------------------------------------------------------------------------- > > Key: TEIID-744 > URL: https://issues.jboss.org/browse/TEIID-744 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > The parsing routines for date and numeric types from string allow for non-canonical string forms. Inverting the convert or parse assumes that the format matches exactly (no additional trailing 0's for example) and there is no leading/trailing ws. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4104) FORMATTIMESTAMP function is not correctly pushed down when a column is passed as FORMAT argument

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4104?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4104: ---------------------------------- Summary: FORMATTIMESTAMP function is not correctly pushed down when a column is passed as FORMAT argument (was: FORMATTIMESTAMP function is not correctly pushed down when a colum is passed as FORMAT argument) > FORMATTIMESTAMP function is not correctly pushed down when a column is passed as FORMAT argument > ------------------------------------------------------------------------------------------------ > > Key: TEIID-4104 > URL: https://issues.jboss.org/browse/TEIID-4104 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Salvatore R > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.5 > > > I defined in PostgreSQL the following table: > {code:sql} > CREATE TABLE public.test > ( > ts timestamp without time zone, > fmt character varying(100) > ); > {code} > Running this query: > {code:sql} > select FORMATTIMESTAMP(ts, fmt) from pg.test; > {code} > throws the following exception: > {code} > 13:44:21,778 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue19) J0VWrGay8mz0 Connector worker process failed for atomic-request=J0VWrGay8mz0.8.0.2: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT formattimestamp(g_0."ts", g_0."fmt") FROM "public"."test" AS g_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.0.CR1.jar:8.12.0.CR1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:349) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_67] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_67] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_67] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_67] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy47.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] > Caused by: org.postgresql.util.PSQLException: ERROR: function formattimestamp(timestamp without time zone, character varying) does not exist > Hint: No function matches the given name and argument types. You might need to add explicit casts. > Character: 8 > at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) > at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) > at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) > at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.0.CR1.jar:8.12.0.CR1] > ... 18 more > {code} > A similar exception is thrown not only in PostgreSQL but also in other datasources like MySQL, Oracle or Microsoft SQL Server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4094: --------------------------------------- No. I've left it open against 8.12.5 as this change at least for the project branch makes a build that cannot be promoted in nexus. Based upon what I've seen with 8.11/8.12 it does look like we are producing a clean jdbc jar, so the resolution here even for 8.12.5 may not be to create another module, but to refine the productization changes for the build. > Move the packaging of teiid-jdbc.jar into is own project > -------------------------------------------------------- > > Key: TEIID-4094 > URL: https://issues.jboss.org/browse/TEIID-4094 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency. > {code} > [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile > [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile > {code} > And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4094: ------------------------------------- Is there anything needs to be done for 9.0? > Move the packaging of teiid-jdbc.jar into is own project > -------------------------------------------------------- > > Key: TEIID-4094 > URL: https://issues.jboss.org/browse/TEIID-4094 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency. > {code} > [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile > [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile > {code} > And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4164) Correct the transitive dependencies in OData4 translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4164?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4164. --------------------------------- Resolution: Done Added the needed runtime dependencies as dependencies in pom.xml for the "embedded" dependencies to be explicit, as well to build the Wildfly modules. Also updated Wildfly module building script to build all the dependent modules excluding that are natively provided by Wildfly itself. One concern I see is "com.fasterxml.*" is being used in multiple places Olingo, Swagger, Wildfly with Wildfly using a different version. We need to pull together these into some common dependency module, to reduce the complexity in individual modules. > Correct the transitive dependencies in OData4 translator > -------------------------------------------------------- > > Key: TEIID-4164 > URL: https://issues.jboss.org/browse/TEIID-4164 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 9.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 9.0 > > > Currently "com.fasterxml" transitive dependencies are not in "kits" or pom.xml > They need to be explicitly defined as dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4228: ------------------------------------- Component/s: ODBC Fix Version/s: 9.x Priority: Minor (was: Major) Affects Version/s: 8.7 Assignee: (was: Steven Hawkins) Lowering the priority of this as we are recommending with TEIID-4229 that parse statements not be used and 0 is an invalid precision. We should still investigate if we want to validate against that (possibly only for odbc) and where the 0 value is coming from. Marc - any updates from the customer side will help with that. > ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns > ----------------------------------------------------------------------------------- > > Key: TEIID-4228 > URL: https://issues.jboss.org/browse/TEIID-4228 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Environment: Connections through ODBC driver > Reporter: Marc Shirley > Priority: Minor > Fix For: 9.x > > > Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client. In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution. > This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4164) Correct the transitive dependencies in OData4 translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4164?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4164: -------------------------------- Fix Version/s: 9.0 > Correct the transitive dependencies in OData4 translator > -------------------------------------------------------- > > Key: TEIID-4164 > URL: https://issues.jboss.org/browse/TEIID-4164 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 9.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 9.0 > > > Currently "com.fasterxml" transitive dependencies are not in "kits" or pom.xml > They need to be explicitly defined as dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016