June 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2561) Allow nested MERGE of entities in MongoDB translators

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2561: ----------------------------------- Summary: Allow nested MERGE of entities in MongoDB translators Key: TEIID-2561 URL: https://issues.jboss.org/browse/TEIID-2561 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.4 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.5 Currently the MERGE (EMBEDIN) functionality can not be nested with other embeddable properties. I.e. if table defined "EMBEDIN", then it's parent can not define any embeddable properties. 1) Rename EMBEDIN --> MERGE extension property 2) When MERGE is on child table, Allow parent table to be participate in another "MERGE" or "EMBEDDEBLE" scenario. This will allow greater number of tables to be collapsed into single document. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2441) Invalid character detected for charset {0}. The text may be encoded in a different charset.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2441?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2441. ----------------------------------- Fix Version/s: 8.4.1 Resolution: Done Updated the conversion classes InputStreamReader and ReaderInputStream to provide better messages and added better message handling to to_bytes and to_chars. Also added well-formed arguments to to_bytes/to_chars (doc'd in 8.5, but not in 8.4.1 as there's no placeholder for that) so that the user can better control when and if exceptions are thrown from the conversion functions. > Invalid character detected for charset {0}. The text may be encoded in a different charset. > -------------------------------------------------------------------------------------------- > > Key: TEIID-2441 > URL: https://issues.jboss.org/browse/TEIID-2441 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.4.1, 8.5 > > > The error could return a more clear statement -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2390) Improve xml/json production

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2390?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2390. ----------------------------------- Fix Version/s: 8.5 Resolution: Done Just improved direct nesting of jsonArray/jsonObject. Further improvements to json/xml would likely take the form of a compiled plan similar to an xmldocument plan, such that it can be built top down and account for blocked exceptions. As it stands it would be a major change to allow inline evaluation (to prevent recopying) of aggregate expressions and subqueries. Switching a pull processing notion would also help to simply delay evaluation until the expression is fully evaluated, but must all of the logic was written from the perspective of fully realizing the values as evaluation proceeds. The performance improvement is minor for small documents or if there is little direct nesting, thus I'm not proceeding with SQL/XML at this time. > Improve xml/json production > --------------------------- > > Key: TEIID-2390 > URL: https://issues.jboss.org/browse/TEIID-2390 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > The current xml/json logic can produce a lot of intermediate results that are recopied and can result in a slower performance for larger documents. > The logic could allow for nested evaluations to delay creating their full string forms or simply allow the return values to remain appendable rather than requiring full copies. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2390) Improve xml/json production

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2390?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2390: --------------------------------------- It's fairly easy to convert the json handling for jsonobject/jsonarray so that their nested evaluations are done in the scope of the parent - but jsonarray_agg and jscon scalar subqueries would still be separate evaluations. The same approach to xml is basically untenable as there are too many nesting combinations. With subqueries there is also the issue that evaluation will block and the whole intermediate result will be invalid and rebuilt with the next processing run. Generally speaking all intermediate filestores should have better cleanup (when not used due to an exception or even when used, but never returned from the evaluator). Will keep investigating. > Improve xml/json production > --------------------------- > > Key: TEIID-2390 > URL: https://issues.jboss.org/browse/TEIID-2390 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > The current xml/json logic can produce a lot of intermediate results that are recopied and can result in a slower performance for larger documents. > The logic could allow for nested evaluations to delay creating their full string forms or simply allow the return values to remain appendable rather than requiring full copies. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2557) Provide support for Composite Foreign Keys in MongoDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2557?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2557. --------------------------------- Labels: alpha1 (was: ) Fix Version/s: 8.5 Resolution: Done Added support to handle the composite foreign key. The need itself may be little un-common, but when used on table all the referencing columns in FK, get all the columns involved in FK. For ex: {code} CREATE FOREIGN TABLE G1 ( e1 integer NOT NULL, e2 integer NOT NULL, e3 integer, PRIMARY KEY (e1, e2) ) OPTIONS(UPDATABLE 'TRUE'); CREATE FOREIGN TABLE G2 ( e1 integer NOT NULL, e2 integer NOT NULL, e3 integer, FOREIGN KEY (e1, e2) REFERENCES G1 (e1, e2) ) OPTIONS(UPDATABLE 'TRUE'); {code} will generate a document like {code} > db.G1.findOne() { "_id" : { "e1" : 1, "e2" : 2 }, "e3" : 3 } > db.G2.findOne() { "_id" : DBRef("G1", { "e1" : 1, "e2" : 2 }), "e2" : DBRef("G1", { "e1" : 1, "e2" : 2 }), "e3" : 3 } {code} This way I could keep the DBRef structure intact, only side effect is during the updates one needs to supply all the keys to form a correct query, otherwise it will result in error. > Provide support for Composite Foreign Keys in MongoDB > ----------------------------------------------------- > > Key: TEIID-2557 > URL: https://issues.jboss.org/browse/TEIID-2557 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: alpha1 > Fix For: 8.4.1, 8.5 > > > TEIID-2529 provided support for PK, but missed the FKs that have multiple keys, this need to be fixed -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2560) wrong result with distinct independent values in a depedent join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2560?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2560. ----------------------------------- Resolution: Done corrected the distinct check to make sure it is across just the columns used for that join. > wrong result with distinct independent values in a depedent join > ---------------------------------------------------------------- > > Key: TEIID-2560 > URL: https://issues.jboss.org/browse/TEIID-2560 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > This should be a fairly uncommon scenario, but if given a query such as: > SELECT ... FROM pm1.g1, pm3.g2, /*+ makeind */ (select distinct e1, e2 from pm2.g1) x WHERE x.e1=pm1.g1.e1 AND pm3.g2.e2=x.e2 > such that the independent side of the join is seen as having distinct values and the dependent sets are targeted at different sources, we will not correctly detect that the values need pre-processed with dup removal. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2560) wrong result with distinct independent values in a depedent join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2560?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2560: --------------------------------------- One more condition is that the independent values must exceed the threshold of issuing a single query against a dependent side. > wrong result with distinct independent values in a depedent join > ---------------------------------------------------------------- > > Key: TEIID-2560 > URL: https://issues.jboss.org/browse/TEIID-2560 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > This should be a fairly uncommon scenario, but if given a query such as: > SELECT ... FROM pm1.g1, pm3.g2, /*+ makeind */ (select distinct e1, e2 from pm2.g1) x WHERE x.e1=pm1.g1.e1 AND pm3.g2.e2=x.e2 > such that the independent side of the join is seen as having distinct values and the dependent sets are targeted at different sources, we will not correctly detect that the values need pre-processed with dup removal. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2560) wrong result with distinct independent values in a depedent join

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2560: ------------------------------------- Summary: wrong result with distinct independent values in a depedent join Key: TEIID-2560 URL: https://issues.jboss.org/browse/TEIID-2560 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 This should be a fairly uncommon scenario, but if given a query such as: SELECT ... FROM pm1.g1, pm3.g2, /*+ makeind */ (select distinct e1, e2 from pm2.g1) x WHERE x.e1=pm1.g1.e1 AND pm3.g2.e2=x.e2 such that the independent side of the join is seen as having distinct values and the dependent sets are targeted at different sources, we will not correctly detect that the values need pre-processed with dup removal. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2559) Add additional make dep hint options

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2559: ------------------------------------- Summary: Add additional make dep hint options Key: TEIID-2559 URL: https://issues.jboss.org/browse/TEIID-2559 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 make dep hints should support additional options to facilitate TEIID-2249. This includes: min - the minimum number of rows to trigger a dependent join full pushdown max - the maximum number of rows allowed before rejecting the dependent join (this would apply in both full pushdown and partial non-pushdown scenarios - in the latter though it will likely refer to the number of distinct values) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2558) Add translator support for dependent join pushdown

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2558: ------------------------------------- Summary: Add translator support for dependent join pushdown Key: TEIID-2558 URL: https://issues.jboss.org/browse/TEIID-2558 Project: Teiid Issue Type: Sub-task Components: Connector API Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 JDBC translators should offer built-in support for dependent join pushdown - possibly with index creation and other options. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2013