November 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2574) HiveMetadata procesor typo in importer property name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2574?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2574: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 984853|https://bugzilla.redhat.com/show_bug.cgi?id=984853] Fixed before GA - setting to requires_doc_text- accordingly > HiveMetadata procesor typo in importer property name > ---------------------------------------------------- > > Key: TEIID-2574 > URL: https://issues.jboss.org/browse/TEIID-2574 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 8.4.1, 8.5 > > > HiveMetadatProcessor's method setTrimColumNames should be named setTrimColumnNames > Unfortunately, when the documentation is without typo so when user sets the importer property according to docs, the property is silently not set. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2475) The RelationalNode.collectNodeStats is only subtracting out the last node

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2475?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2475: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 967982|https://bugzilla.redhat.com/show_bug.cgi?id=967982] Fixed before GA - setting to requires_doc_text- accordingly > The RelationalNode.collectNodeStats is only subtracting out the last node > ------------------------------------------------------------------------- > > Key: TEIID-2475 > URL: https://issues.jboss.org/browse/TEIID-2475 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > Attachments: Query_Plan.txt > > > The "Node Cumulative Next Batch Process Time" Statistic > If you have a look at the explain plan (attached). Following the definition, > the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) + JoinNode (Node Process Time: 2203120). The summation does not agree. > The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting out the last node) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2361) The current MAX String size is 4000, add the ability to configure when larger sizes are used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2361?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2361: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 896305|https://bugzilla.redhat.com/show_bug.cgi?id=896305] Fixed before GA - setting to requires_doc_text- accordingly > The current MAX String size is 4000, add the ability to configure when larger sizes are used > -------------------------------------------------------------------------------------------- > > Key: TEIID-2361 > URL: https://issues.jboss.org/browse/TEIID-2361 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.3, 7.7.7 > > > The MAX String size is currently 4000. After a discussion with Steve, he indicated a more common default might be 16k, and also add the ability to configure the size when a data source is being used that contains large sizes. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2188) When using CONCAT2(x, y), can the source query be changed to not include the CASE statements and let Oracle do the NULL compare

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2188?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2188: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 855016|https://bugzilla.redhat.com/show_bug.cgi?id=855016] Fixed before GA - setting to requires_doc_text- accordingly > When using CONCAT2(x, y), can the source query be changed to not include the CASE statements and let Oracle do the NULL compare > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2188 > URL: https://issues.jboss.org/browse/TEIID-2188 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 7.4.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.2 > > > When CONCAT2(x, y) is used, the rewritten query is very verbose in adding a CASE statement to check for nulls. Can the rewritten query not include the CASE statements and just let Oracle do the compare, because it can do it more efficiently within the CONCAT call? > Example: > select concat2(f1,f2) from table1 > results in > SELECT c_0 FROM (SELECT CASE WHEN to_char(g_0.f1) IS NULL AND g_0.f2 IS NULL THEN NULL ELSE concat(nvl(to_char(g_0.f1), ''), nvl(g_0.f2, '')) END AS c_0 FROM table1 g_0) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2035: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 985578|https://bugzilla.redhat.com/show_bug.cgi?id=985578] Fixed before GA - setting to requires_doc_text- accordingly > DeleteDataSource method on Admin API does not completely delete the Connection Factory > -------------------------------------------------------------------------------------- > > Key: TEIID-2035 > URL: https://issues.jboss.org/browse/TEIID-2035 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.4.1, 8.5 > > > ConnectionFactory requires a two step creation process > 1) create the resource-adaptor section > 2) connection factory section > The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2655) Minimize the reporting of erroneous illegalstateexceptions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2655?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2655: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 1006019|https://bugzilla.redhat.com/show_bug.cgi?id=1006019] Fixed before GA - setting to requires_doc_text- accordingly > Minimize the reporting of erroneous illegalstateexceptions > ---------------------------------------------------------- > > Key: TEIID-2655 > URL: https://issues.jboss.org/browse/TEIID-2655 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Service injector illegalstateexceptions can be seen as errors in the logs with asynch metadata load when the vdb has already failed for another reason. We should ensure that these are not reported as additional errors. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2329) Add support for Mongo DB as a data source

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2329?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2329: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 888935|https://bugzilla.redhat.com/show_bug.cgi?id=888935] Fixed before GA - setting to requires_doc_text- accordingly > Add support for Mongo DB as a data source > ----------------------------------------- > > Key: TEIID-2329 > URL: https://issues.jboss.org/browse/TEIID-2329 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.4, Open To Community > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2709) Quickstart - drools-integration uses drools 5 instead of drools 6

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2709?page=com.atlassian.jira.plugin... ] Work on TEIID-2709 started by Van Halbert. > Quickstart - drools-integration uses drools 5 instead of drools 6 > ------------------------------------------------------------------- > > Key: TEIID-2709 > URL: https://issues.jboss.org/browse/TEIID-2709 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The drools-integration quick start uses drools 5, instead of drools 6. > And its not a matter of swapping out the versions due to api changes drools 6. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2745) Evaluatable subquery in ON clause produces invalid query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2745?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2745. ----------------------------------- Resolution: Done Corrected the rewriter. > Evaluatable subquery in ON clause produces invalid query > -------------------------------------------------------- > > Key: TEIID-2745 > URL: https://issues.jboss.org/browse/TEIID-2745 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > Using an evaluatable subquery, such as a scalar subquery in an outer join on clause will result in all criteria being removed and an invalid source query being issued. > For example: > with a (x, y, z) as (select e1, e2, e3 from pm1.g1 limit 1) SELECT pm2.g1.e1 from pm2.g1 left outer join pm2.g2 on (pm2.g1.e2 = pm2.g2.e2 and pm2.g1.e1 = (select a.x from a)) > And a source that doesn't support with (or the with clause cannot be pushed as part of the main query), then the evaluation of the scalar subquery will block and cause the issue. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2745) Evaluatable subquery in ON clause produces invalid query

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2745: ------------------------------------- Summary: Evaluatable subquery in ON clause produces invalid query Key: TEIID-2745 URL: https://issues.jboss.org/browse/TEIID-2745 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.6 Using an evaluatable subquery, such as a scalar subquery in an outer join on clause will result in all criteria being removed and an invalid source query being issued. For example: with a (x, y, z) as (select e1, e2, e3 from pm1.g1 limit 1) SELECT pm2.g1.e1 from pm2.g1 left outer join pm2.g2 on (pm2.g1.e2 = pm2.g2.e2 and pm2.g1.e1 = (select a.x from a)) And a source that doesn't support with (or the with clause cannot be pushed as part of the main query), then the evaluation of the scalar subquery will block and cause the issue. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2013