December 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2787) Correlated grouping expression not properly replaced in pushdown subquery

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2787?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2787. ----------------------------------- Resolution: Done Made sure that pushdown symbol replacement uses deep navigation. > Correlated grouping expression not properly replaced in pushdown subquery > ------------------------------------------------------------------------- > > Key: TEIID-2787 > URL: https://issues.jboss.org/browse/TEIID-2787 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > A correlated grouping expression appears in the pushdown query with the internal group name anon_grpX rather than the proper reference from the outer query. > For example the user query: > select x, (select avg\(y) from tbl1 where x = tbl2.x) from tbl2 group by x > would have > where x = anon_grp0.x -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2787) Correlated grouping expression not properly replaced in pushdown subquery

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2787?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2787: ---------------------------------- Description: A correlated grouping expression appears in the pushdown query with the internal group name anon_grpX rather than the proper reference from the outer query. For example the user query: select x, (select avg\(y) from tbl1 where x = tbl2.x) from tbl2 group by x would have where x = anon_grp0.x was: A correlated grouping expression appears in the pushdown query with the internal group name anon_grpX rather than the proper reference from the outer query. For example the user query: select x, (select avg(y) from tbl1 where x = tbl2.x) from tbl2 group by x would have where x = anon_grp0.x Workaround Description: Use an inline view to correlated on a projected column. For example rather than: select x, (select avg\(y) from tbl1 where x = tbl2.x) from tbl2 group by x use: select x, (select avg\(y) from tbl1 where x = v.x) from (select x from tbl2 group by x) as v was: Use an inline view to correlated on a projected column. For example rather than: select x, (select avg(y) from tbl1 where x = tbl2.x) from tbl2 group by x use: select x, (select avg(y) from tbl1 where x = v.x) from (select x from tbl2 group by x) as v > Correlated grouping expression not properly replaced in pushdown subquery > ------------------------------------------------------------------------- > > Key: TEIID-2787 > URL: https://issues.jboss.org/browse/TEIID-2787 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > A correlated grouping expression appears in the pushdown query with the internal group name anon_grpX rather than the proper reference from the outer query. > For example the user query: > select x, (select avg\(y) from tbl1 where x = tbl2.x) from tbl2 group by x > would have > where x = anon_grp0.x -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2787) Correlated grouping expression not properly replaced in pushdown subquery

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2787: ------------------------------------- Summary: Correlated grouping expression not properly replaced in pushdown subquery Key: TEIID-2787 URL: https://issues.jboss.org/browse/TEIID-2787 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7 A correlated grouping expression appears in the pushdown query with the internal group name anon_grpX rather than the proper reference from the outer query. For example the user query: select x, (select avg(y) from tbl1 where x = tbl2.x) from tbl2 group by x would have where x = anon_grp0.x -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2778) The artifact name contains .6 (infinispan-remote-cache.6), remove it

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2778?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-2778. -------------------------------- Resolution: Done PR https://github.com/teiid/teiid-quickstarts/pull/50 Updated root pom to use Teiid 8.6.0.Final > The artifact name contains .6 (infinispan-remote-cache.6), remove it > -------------------------------------------------------------------- > > Key: TEIID-2778 > URL: https://issues.jboss.org/browse/TEIID-2778 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The quick start infinispan-remote-cache has its artifact name set to: infinispan-remote-cache.6 > The '.6' should be removed. This will resolve the issue where the pogo jar name will then match the module name. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2786: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1046501 > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: > 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) > 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) > 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2786: --------------------------------------- Just set widenUnsingedTypes to false. If we catch this exception with widenUnsignedTypes set to true (the default) we effectively won't know what types are unsigned so at the least a warning log would be needed. Or we can just leave things as they are with a more detailed exception message. > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: > 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) > 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) > 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by Van Halbert (JIRA)

Van Halbert created TEIID-2786: ---------------------------------- Summary: ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException Key: TEIID-2786 URL: https://issues.jboss.org/browse/TEIID-2786 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.7 Reporter: Van Halbert Assignee: Steven Hawkins When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2773) MATVIEW corrupted after SYSADMIN.refreshMatView()

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2773?page=com.atlassian.jira.plugin... ] Johnathon Lee resolved TEIID-2773. ---------------------------------- Resolution: Done Committed r4619 to https://svn.jboss.org/repos/teiid/branches/7.7.x > MATVIEW corrupted after SYSADMIN.refreshMatView() > ------------------------------------------------- > > Key: TEIID-2773 > URL: https://issues.jboss.org/browse/TEIID-2773 > Project: Teiid > Issue Type: Bug > Components: Query Engine, Server > Affects Versions: 7.7.5 > Environment: EDS 5.3.1 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Fix For: 7.7.9 > > > After CALL SYSADMIN.refreshMatView(viewname=>TABLE_NAME, invalidate=>false) against Materialized View, querying "select * from TABLE_NAME", one of columns shows a value of another column. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2773) MATVIEW corrupted after SYSADMIN.refreshMatView()

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2773?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2773: --------------------------------- Fix Version/s: 7.7.9 > MATVIEW corrupted after SYSADMIN.refreshMatView() > ------------------------------------------------- > > Key: TEIID-2773 > URL: https://issues.jboss.org/browse/TEIID-2773 > Project: Teiid > Issue Type: Bug > Components: Query Engine, Server > Affects Versions: 7.7.5 > Environment: EDS 5.3.1 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Fix For: 7.7.9 > > > After CALL SYSADMIN.refreshMatView(viewname=>TABLE_NAME, invalidate=>false) against Materialized View, querying "select * from TABLE_NAME", one of columns shows a value of another column. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call

by Van Halbert (JIRA)

Van Halbert created TEIID-2785: ---------------------------------- Summary: Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call Key: TEIID-2785 URL: https://issues.jboss.org/browse/TEIID-2785 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Affects Versions: 8.7 Reporter: Van Halbert Assignee: Van Halbert The ModeShapeExecutionFactory should expose the JCR procedures in the metadata when the getMetadata(..) is called. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2013