June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4175) Certain nested dependent join structure will cause fewer results than expected

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4175?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4175. --------------------------------- > Certain nested dependent join structure will cause fewer results than expected > ------------------------------------------------------------------------------ > > Key: TEIID-4175 > URL: https://issues.jboss.org/browse/TEIID-4175 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.7.6.6_2, 8.13.5 > > > With a query such as: > {code} > SELECT pm1.g1.e1, pm1.g2.e2 from /*+ makeind */ pm1.g1 inner join /*+ preserve */ (/*+ makeind */ pm1.g2 inner join pm1.g3 on pm1.g2.e2 = pm1.g3.e2) on pm1.g1.e1 = pm1.g2.e1 > {code} > There will be a join structure like: > {code} > JoinNode(1) [Dependent] > AccessNode(2) > JoinNode(3) [Dependent] [MERGE JOIN (ALREADY_SORTED/ALREADY_SORTED)] > DependentAccessNode(4) > DependentAccessNode(5) > {code} > Such that there is a dependent join as a left child of a merge join that is marked as having that child already sorted. When there is more than 1 query needed for DependentAccessNode(4), the DependentAccessNode will mistakenly mark the right child as needing to be sorted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4144) Mismanagement of output columns in ruleimplementjoinstrategy

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4144?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4144. --------------------------------- > Mismanagement of output columns in ruleimplementjoinstrategy > ------------------------------------------------------------ > > Key: TEIID-4144 > URL: https://issues.jboss.org/browse/TEIID-4144 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.0, 8.12.5, 8.13.1, 8.7.3.6_2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.7.6.6_2, 8.13.4 > > > Related to TEIID-3973 - the fix introduced a situation where if the sort node is not added and a join expression is used and there are intervening nodes, then the output columns are not correctly managed. The result is a similar value not found exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4186) Prevent partial aggregate pushdown based upon type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4186?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4186. --------------------------------- > Prevent partial aggregate pushdown based upon type > -------------------------------------------------- > > Key: TEIID-4186 > URL: https://issues.jboss.org/browse/TEIID-4186 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.7.6.6_2 > > > For limited value types, such as boolean or byte, there is little value in their use as grouping columns and should be avoided - even if distinct value counts are not available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3780) Hive: Convert "UseDatabaseMetaData: to be an translator import property

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3780?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3780. --------------------------------- > Hive: Convert "UseDatabaseMetaData: to be an translator import property > ----------------------------------------------------------------------- > > Key: TEIID-3780 > URL: https://issues.jboss.org/browse/TEIID-3780 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.11 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12.1, 8.13 > > > Currently "UseDatabaseMetadata" as been designed as Translator property, may be this should be designed as translator importer property? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3823) Issues with fetchsize and local connections

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3823?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3823. --------------------------------- > Issues with fetchsize and local connections > ------------------------------------------- > > Key: TEIID-3823 > URL: https://issues.jboss.org/browse/TEIID-3823 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.3, 8.13 > > > Settting the fetchSize property on localconnections (or if the internal batch size exceeds that of the maximum fetch size, which is unlikely by default) leads to several issues: > It can cause an exception or the client may seem to hang (since the logic won't properly save the current batch). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3515) make makedep and related hints consistent

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3515?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3515. --------------------------------- > make makedep and related hints consistent > ----------------------------------------- > > Key: TEIID-3515 > URL: https://issues.jboss.org/browse/TEIID-3515 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > There are three places where hints can be specified, in the options clause, after an item, and before in a comment block. > We should ensure that the comment block supports all options max/join for makedep, and that makeind should have the same options as makedep. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3361) Add source query details to the command log

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3361?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3361. --------------------------------- > Add source query details to the command log > ------------------------------------------- > > Key: TEIID-3361 > URL: https://issues.jboss.org/browse/TEIID-3361 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.1 > > > The command log for convenience only contains the Teiid sql form of the source query. It would be good to have the translators also add their actual form of the source query when possible to the command log just to have a single place to track things down. > Currently this info is logged to the CONNECTOR context inconsistently in each translator. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3655) Generated REST Service war do not allow any no-rest url

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3655?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3655. --------------------------------- > Generated REST Service war do not allow any no-rest url > ------------------------------------------------------- > > Key: TEIID-3655 > URL: https://issues.jboss.org/browse/TEIID-3655 > Project: Teiid > Issue Type: Quality Risk > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Kylin Soong > Priority: Blocker > Fix For: 8.12 > > Attachments: Screenshot.png > > > Generated REST Service war have the following configuration in web.xml > {code} > <servlet-mapping> > <servlet-name>RestDataservice</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > {code} > This means all request be thought as rest request. As attached screen, all shot, > {code} > http://localhost:8080/sample_1/swagger/css/typography.css > http://localhost:8080/sample_1/swagger/lib/jquery-1.8.0.min.js > http://localhost:8080/sample_1/swagger/lib/highlight.7.3.pack.js > {code} > be thought as rest request, but no relevant api define, 404 returned. > Current design is for guarantee the rest api path like > {code} > /{vdbName_vdbVersion}/{modelName}/{procedureName}/{path} > {code} > for example > {code} > http://localhost:8080/sample_1/view/g1/1 > {code} > But, I do wonder we really need to treat all are rest request? For example, if we request http://localhost:8080/sample_1, a rude 404 page with stacktrace return, we may consider and a customized 404 page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3546) Add distinct from syntax in for each row procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3546?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3546. --------------------------------- > Add distinct from syntax in for each row procedures > --------------------------------------------------- > > Key: TEIID-3546 > URL: https://issues.jboss.org/browse/TEIID-3546 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12 > > > Similar to postgresql, it would be good to allow for a quick comparison of new/old values to determine if row processing is needed. Something like: > IF new IS DISTINCT FROM old THEN > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3839) minimize implicit dependencies on sun classes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3839?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3839. --------------------------------- > minimize implicit dependencies on sun classes > --------------------------------------------- > > Key: TEIID-3839 > URL: https://issues.jboss.org/browse/TEIID-3839 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.3, 8.13 > > > Serialization of the server timezone can rely on sun.util.calendar.Zoneinfo, which is not allowed by default in EAP/Wildfly if using the driver as just a jar. Ideally we should avoid direct serialization of these classes as much as possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016