February 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2330) Failed load shows a loading in the console

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2330?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2330: ------------------------------------- I was thinking to unwrap the exception, but what you said could work better as it is RuntimeException. > Failed load shows a loading in the console > ------------------------------------------ > > Key: TEIID-2330 > URL: https://issues.jboss.org/browse/TEIID-2330 > Project: Teiid > Issue Type: Bug > Components: Tools > Reporter: Steven Hawkins > > The metadataexception in the forum post should transition the vdb to failed. I'm logging this initially against the console as we have a similar unit test that correctly reports a failed load given invalid ddl, which is essentially the same exception. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2330) Failed load shows a loading in the console

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2330?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2330: --------------------------------------- > 1) During the metadata load, thrown as TranslatorException I do not believe that is correct. MetadataExceptions should not be rethrown as TranslatorExceptions, which is why this issue was logged. Do you see different handling? > Failed load shows a loading in the console > ------------------------------------------ > > Key: TEIID-2330 > URL: https://issues.jboss.org/browse/TEIID-2330 > Project: Teiid > Issue Type: Bug > Components: Tools > Reporter: Steven Hawkins > > The metadataexception in the forum post should transition the vdb to failed. I'm logging this initially against the console as we have a similar unit test that correctly reports a failed load given invalid ddl, which is essentially the same exception. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2330) Failed load shows a loading in the console

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2330?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2330: ------------------------------------- Yes, that is true, it is MetadataException. We have two different places these exceptions can originate. 1) During the metadata load, thrown as TranslatorException 2) During metadata validation, as MetadataException, which is RuntimeException. I see that during the vdbFinish, RuntimeExceptions are properly transitioned into FAILED state, where as TranslatorException is always treated as an issue with data source that can be corrected, so it is kept in the LOADING state. I will try to check the "cause" in the TranslatorException to see if that is in fact MetadataException, which should resolve this issue. BTW, console is very stupid (transparent) in this regard, it just show what information Teiid sends back. Yes, it shows those respective errors on the screen. > Failed load shows a loading in the console > ------------------------------------------ > > Key: TEIID-2330 > URL: https://issues.jboss.org/browse/TEIID-2330 > Project: Teiid > Issue Type: Bug > Components: Tools > Reporter: Steven Hawkins > > The metadataexception in the forum post should transition the vdb to failed. I'm logging this initially against the console as we have a similar unit test that correctly reports a failed load given invalid ddl, which is essentially the same exception. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2397) count of group by column return 1 over join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2397?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2397. ----------------------------------- Resolution: Done added a cardinality check before removing an agg over a grouping column. > count of group by column return 1 over join > ------------------------------------------- > > Key: TEIID-2397 > URL: https://issues.jboss.org/browse/TEIID-2397 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.3 > > > A query of the form: > select e1, count(e1) from pm1.g1, (select 1 from pm1.g2 limit 1) x group by e1 > Will fail to return the proper count for e1 as the decomposition is erroneously considering the decomposed count aggregate as unnecessary. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2330) Failed load shows a loading in the console

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2330?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2330: --------------------------------------- The forum posting is about getting a metadataexception, such as a duplicate table, and still showing up as loading. Seems like the mis-configured source should display loading or perhaps also indicate that it has already failed (there should be a warning attached to the model). > Failed load shows a loading in the console > ------------------------------------------ > > Key: TEIID-2330 > URL: https://issues.jboss.org/browse/TEIID-2330 > Project: Teiid > Issue Type: Bug > Components: Tools > Reporter: Steven Hawkins > > The metadataexception in the forum post should transition the vdb to failed. I'm logging this initially against the console as we have a similar unit test that correctly reports a failed load given invalid ddl, which is essentially the same exception. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2330) Failed load shows a loading in the console

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2330?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2330: ------------------------------------- Looks like in the case of data source mis-configuration, Teiid re-queues the metadata load job and keeps the vdb-status in "LOADING" state, thus the console never shows it as "failed". If the data source gets corrected then it will resume loading. > Failed load shows a loading in the console > ------------------------------------------ > > Key: TEIID-2330 > URL: https://issues.jboss.org/browse/TEIID-2330 > Project: Teiid > Issue Type: Bug > Components: Tools > Reporter: Steven Hawkins > > The metadataexception in the forum post should transition the vdb to failed. I'm logging this initially against the console as we have a similar unit test that correctly reports a failed load given invalid ddl, which is essentially the same exception. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2397) count of group by column return 1 over join

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2397: ------------------------------------- Summary: count of group by column return 1 over join Key: TEIID-2397 URL: https://issues.jboss.org/browse/TEIID-2397 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.3 A query of the form: select e1, count(e1) from pm1.g1, (select 1 from pm1.g2 limit 1) x group by e1 Will fail to return the proper count for e1 as the decomposition is erroneously considering the decomposed count aggregate as unnecessary. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2232) Update Hive translator for newer version of Hive Driver

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2232?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2232: ------------------------------------- Looking at the release notes for 0.8.1, 0.9.0, 0.10.0, I see only CROSS JOIN, BETWEEN support added that matters to this translator, which were already added. Just test with Hive 0.10.0. I think we can close this JIRA. > Update Hive translator for newer version of Hive Driver > ------------------------------------------------------- > > Key: TEIID-2232 > URL: https://issues.jboss.org/browse/TEIID-2232 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.1 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Labels: hive, teiid > Fix For: 8.3 > > > Originally Hive translator designed for 0.7 version of the Hive JDBC driver, the current version is "30 April, 2012: release 0.9.0 available". > Another important update we should do is take advantage of their direct map-reduce job submission through Hive as native command 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1854) OData server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1854?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1854. --------------------------------- Resolution: Done Implemented Aggregate ALL functionality. Any other bugs or features, will be worked as they are logged. > OData server > ------------ > > Key: TEIID-1854 > URL: https://issues.jboss.org/browse/TEIID-1854 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Mark Addleman > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Teiid should act as an OData server as well as a JDBC server. This is not TEIID-1757 as that is about Teiid being an OData client. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2396) count of column returns null instead of 0 over join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2396?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2396. ----------------------------------- Resolution: Done Added an ifnull to the aggregate decomposition. > count of column returns null instead of 0 over join > --------------------------------------------------- > > Key: TEIID-2396 > URL: https://issues.jboss.org/browse/TEIID-2396 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.3 > > > The aggregate pushing logic will decompose a count as a sum of count, which can be null if no rows are returned by the 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

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2013