October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1303) Sybase 15 Queries - Incorrect syntax on queries with FULL OUTER JOIN

by Warren Gibson (JIRA)

Sybase 15 Queries - Incorrect syntax on queries with FULL OUTER JOIN -------------------------------------------------------------------- Key: TEIID-1303 URL: https://jira.jboss.org/browse/TEIID-1303 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steven Hawkins The following query and error is an example of Sybase 15 queries with a FULL OUTER JOIN. Sybase does not support FULL OUTER JOIN and a Translator change is needed. SELECT BQT2.SmallB.IntKey, y.DoubleNum FROM BQT2.SmallB FULL OUTER JOIN (SELECT IntKey, DoubleNum FROM BQT1.MediumA) AS y ON BQT2.SmallB.IntKey = y.IntKey ORDER BY IntKey, DoubleNum - RDBMS_Test_Queries_9500_TestQuery113 Error Code:102 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:102 Message:Error Code:102 Message:'Incorrect syntax near 'FULL'.' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.IntKey AS c_0, g_1.DoubleNum AS c_1 FROM SmallB g_0 FULL OUTER JOIN MediumA g_1 ON g_0.IntKey = g_1.IntKey ORDER BY c_0, c_1] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1296) Multi-Source may not be wrapping the transactional scope correctly

by Ramesh Reddy (JIRA)

Multi-Source may not be wrapping the transactional scope correctly ------------------------------------------------------------------ Key: TEIID-1296 URL: https://jira.jboss.org/browse/TEIID-1296 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 The distributed transaction is required when multiple sources are involved. Teiid determines this by counting the number of access nodes that represent sources. In the multi-source it counts as one, even in the cases it involves multiple sources underneath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1299) Remove un-implemented Admin API methods.

by Ramesh Reddy (JIRA)

Remove un-implemented Admin API methods. ---------------------------------------- Key: TEIID-1299 URL: https://jira.jboss.org/browse/TEIID-1299 Project: Teiid Issue Type: Task Components: AdminApi Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1, 7.2 Admin methods setRuntimeProperty - is not implemented, and signature may be not sufficient to implement in the future. Remove this and add when feature is required. getWorkManagerStats(String identifier) - since there is going to be single Teiid engine in a given VM, there is no need for the "identifier" parameter, this needs to be removed for simplicity. getProcesses(String processIdentifier) - this method is not also implemented, it was kept to make "AdminApiServerDiscovery" supported. However the way it is currently it is not functional, either this needs to be removed or fixed for correct usage. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1262) Update Netty to 3.2.1 in the 7.1.x branch

by Van Halbert (JIRA)

Update Netty to 3.2.1 in the 7.1.x branch ----------------------------------------- Key: TEIID-1262 URL: https://jira.jboss.org/browse/TEIID-1262 Project: Teiid Issue Type: Task Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.1.1 Netty needs to be updated to 3.2.1 version -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1293) subqueries should not allow select into

by Steven Hawkins (JIRA)

subqueries should not allow select into --------------------------------------- Key: TEIID-1293 URL: https://jira.jboss.org/browse/TEIID-1293 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 We already validate that union cannot contain a select into, we should ensure that exists/scalarsubquries/inlineviews/etc. cannot use select into. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1285) fixes from Data Services Platform version of the Teiid Developer Guide

by Darrin Mison (JIRA)

fixes from Data Services Platform version of the Teiid Developer Guide ---------------------------------------------------------------------- Key: TEIID-1285 URL: https://jira.jboss.org/browse/TEIID-1285 Project: Teiid Issue Type: Patch Components: Documentation Affects Versions: 7.1 Reporter: Darrin Mison Assignee: Steven Hawkins Attachments: EDS.patch Attached is the patch for the changes made downstream in the Data Services Platform version of this doc. Some of the changes are for compatibility with the docbook tool Publican, some are fixes, some are best practices changes. 1 - separated main.xml into Developer_Guide.xml & Book_Info.xml (main.xml removed) updated pom.xml. This is for better compatibility with Publican. Publican also expects a Developer_Guide.ent file with all the entities defined in it but this is impractical to do with yours since you have a shared entities file. 2 - moved a number of <programlisting> from inside <para>s. Having non-translatable block elements inside of translatable block elements (programlisting inside para) creates issues for translators. Best practice. 3 - reformatted a few <programlistings> for better presentation. Mainly made the alignment consistent & ensured they fit on one page without scrolling, very important for PDF output. 3- changed a number of usages of <link> to <xref> also changed them to show the target title instead of the specified text. ie. changed <link linkend="target">info here</link> to <link linkend="target"/> This is a best practice. It makes their intent clearer & presents much better in the PDF output. Also did similar to <ulink>. 4 - moved a number of lists (<itemizedlist> & <orderedlist>) outside of <para>s. See 2. 5 - added language & role attributes to <programlisting>s - provides syntax highlighting ;-) 6 - changed colwidths to integers - Compatibilty with Publican. 7 - changed a few itemizedlists to orderedlists where appropriate. 8 - changed a few itemizedlists to variablelists - was the best way to present these items. However there seems to be a formatting bug with jDocbook, doesn't always format the headings - logging a JIRA for it. 9 - changed "smart quotes" to regular quotes. These are invalid in code samples, if someone copy/pastes the code sample it will not compile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1272) Join planning should make better decisions when mixing costing and unknown values

by Steven Hawkins (JIRA)

Join planning should make better decisions when mixing costing and unknown values --------------------------------------------------------------------------------- Key: TEIID-1272 URL: https://jira.jboss.org/browse/TEIID-1272 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 When faced with an unknown value during join planning we use the default assumption of 100000 rows. However this may cause non-performant cross joins to be pushed in the worst case. It would be better to either not cost these scenarios or get a more accurate estimate of the post join cardinality based upon the the other side of the join. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1309) The engine should validate against using an insert with a query expression in a multisource scenario.

by Steven Hawkins (JIRA)

The engine should validate against using an insert with a query expression in a multisource scenario. ----------------------------------------------------------------------------------------------------- Key: TEIID-1309 URL: https://jira.jboss.org/browse/TEIID-1309 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.2 SELECT INTO or an INSERT with a query expression will not work correctly under a multisource scenario since we do not modify ProjectIntoNodes. We also do not properly handle a pushdown of a insert with a query expression, since the query may pull from multiple sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1290) Application name is null in JOPR

by Steven Hawkins (JIRA)

Application name is null in JOPR -------------------------------- Key: TEIID-1290 URL: https://jira.jboss.org/browse/TEIID-1290 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 Application name is null in JOPR -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1240) Exception with false join predicate

by Steven Hawkins (JIRA)

Exception with false join predicate ----------------------------------- Key: TEIID-1240 URL: https://jira.jboss.org/browse/TEIID-1240 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 Issuing a query such as select ... from a full outer join b on (false) where a.x = 1 will throw an exception because we'll attempt to update the join predicate, but the list is non-modifiable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010