March 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2800) Add back New Child >>View option to the View Model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2800?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2800: ---------------------------------------- Investigated the notion of providing virtual model *views* and interchanging tables and views. * Designer's *relational* EMF metamodel treats a *view" different than a *base table* in that the view does not support *FK/PK/UC* constructs. * Changing our EMF metamodel is not an exercise we've attempted for quite some time. * There is also a disconnect between Designer's use of virtual *table* and how it corresponds to Teiid runtime metadata of a *CREATE VIEW ..... * statement. * At most, we could add an extension property to virtual tables to switch between *table* and *view* types. * I wouldn't recommend adding this feature until all of the ramifications have been discovered and discussed. > Add back New Child >>View option to the View Model > -------------------------------------------------- > > Key: TEIIDDES-2800 > URL: https://issues.jboss.org/browse/TEIIDDES-2800 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Patch Release > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 9.0.6, 10.0.1 > > > RFE https://issues.jboss.org/browse/TEIID-4010 has been entered to differentiate table and view, so would like to have New View and Table option under View Model > New Child. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2199) Designer deletes materialization setting in transformation Editor

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2199?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-2199: ------------------------------------------- [~mmakovy] In answer to your comment: * The spaced version of the cache hint is just a normal comment so is retained * The cache hint is being dropped due problem analysed in TEIIDDES-2802 > Designer deletes materialization setting in transformation Editor > ----------------------------------------------------------------- > > Key: TEIIDDES-2199 > URL: https://issues.jboss.org/browse/TEIIDDES-2199 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Transformations > Affects Versions: 8.3.2 > Environment: fedora 19, Red Hat Data Virtualization 6, JBDS 7.1.1.GA > Reporter: Jason Marley > Assignee: Paul Richardson > Fix For: 10.0.1, 9.2.1 > > > In transformation editor and add caching comment /*+ cache(ttl:300000) */, if there is a space before + and the beginning of comment, upon save designer deletes the line. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2199) Designer deletes materialization setting in transformation Editor

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2199?page=com.atlassian.jira.plu... ] Paul Richardson closed TEIIDDES-2199. ------------------------------------- Resolution: Deferred This cannot be fixed until TEIIDDES-2802 is fixed. There is a solution/patch available but this would need to be incorportated into Teiid as well since there is no point in Designer retaining the cache hint and Teiid dropping it. > Designer deletes materialization setting in transformation Editor > ----------------------------------------------------------------- > > Key: TEIIDDES-2199 > URL: https://issues.jboss.org/browse/TEIIDDES-2199 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Transformations > Affects Versions: 8.3.2 > Environment: fedora 19, Red Hat Data Virtualization 6, JBDS 7.1.1.GA > Reporter: Jason Marley > Assignee: Paul Richardson > Fix For: 10.0.1, 9.2.1 > > > In transformation editor and add caching comment /*+ cache(ttl:300000) */, if there is a space before + and the beginning of comment, upon save designer deletes the line. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2802) Address co-existence of SQL comment and cache hint

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2802?page=com.atlassian.jira.plu... ] Paul Richardson updated TEIIDDES-2802: -------------------------------------- Description: An sql query, such as the following, parses but drops the cache hint {code} /* leading comment */ /*+ cache(ttl:180000) */ SELECT col1 FROM tbl {code} However, the same sql without the 'leading comment' retains the cache hint. The reason is that Designer uses the same parser handling syntax as the Teiid parser. Both use a regular expression for handling the cache hint, ie. {code} "/\\*\\+?\\s*cache(\\(\\s*(pref_mem)?\\s*(ttl:\\d{1,19})?\\s*(updatable)?\\s*(scope:(session|vdb|user))?\\s*(min:\\d{1,19})?[^\\)]*\\))?[^\\*]*\\*\\/.*"; {code} The dot-star (.*) at the end allows for the rest of the sql after the cache hint but there is no allowance for any comments prior to the cache hint. In order to handle this an extra pragma needs to prefix the regular expression above: {code} "(?:/\\*[^\\+].+?\\*/(?:\\s+)?)?" {code} * (...)? => an optional group so no comment is handled * ?: => the group is non-capturing so ignored by the matcher group count * [^\\+] => checks for a + following the comment opener. Cache hints are expected to use this so this distinguishes a normal comment from a cache hint * .+? => makes the comment contents non-greedy so the first comment closer is found rather than the last * (?:\\s+)? => non-capturing optional group that checks for any whitespace between the end of the comment and the cache hint Example patch for Designer parser added. This cannot be rectified in Designer until it is rectified in Teiid. Even then, older versions of Teiid will never support this. was: An sql query, such as the following, parses but drops the cache hint {code} /* leading comment */ /*+ cache(ttl:180000) */ SELECT col1 FROM tbl {code} However, the same sql without the 'leading comment' retains the cache hint. The reason is that Designer uses the same parser handling syntax as the Teiid parser. Both use a regular expression for handling the cache hint, ie. {code} "/\\*\\+?\\s*cache(\\(\\s*(pref_mem)?\\s*(ttl:\\d{1,19})?\\s*(updatable)?\\s*(scope:(session|vdb|user))?\\s*(min:\\d{1,19})?[^\\)]*\\))?[^\\*]*\\*\\/.*"; {code} The dot-star (.*) at the end allows for the rest of the sql after the cache hint but there is no allowance for any comments prior to the cache hint. In order to handle this an extra pragma needs to prefix the regular expression above: {code} "(?:/\\*[^\\+].+?\\*/(?:\\s+)?)?" {code} * (...)? => an optional group so no comment is handled * ?: => the group is non-capturing so ignored by the matcher group count * [^\\+] => checks for a + following the comment opener. Cache hints are expected to use this so this distinguishes a normal comment from a cache hint * .+? => makes the comment contents non-greedy so the first comment closer is found rather than the last * (?:\\s+)? => non-capturing optional group that checks for any whitespace between the end of the comment and the cache hint Example patch for Designer parser added. > Address co-existence of SQL comment and cache hint > -------------------------------------------------- > > Key: TEIIDDES-2802 > URL: https://issues.jboss.org/browse/TEIIDDES-2802 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.2, 10.0 > Reporter: Paul Richardson > Attachments: 0001-Patch-to-address-failures-in-comments-and-cache-hint.patch > > > An sql query, such as the following, parses but drops the cache hint > {code} > /* leading comment */ /*+ cache(ttl:180000) */ SELECT col1 FROM tbl > {code} > However, the same sql without the 'leading comment' retains the cache hint. > The reason is that Designer uses the same parser handling syntax as the Teiid parser. Both use a regular expression for handling the cache hint, ie. > {code} > "/\\*\\+?\\s*cache(\\(\\s*(pref_mem)?\\s*(ttl:\\d{1,19})?\\s*(updatable)?\\s*(scope:(session|vdb|user))?\\s*(min:\\d{1,19})?[^\\)]*\\))?[^\\*]*\\*\\/.*"; > {code} > The dot-star (.*) at the end allows for the rest of the sql after the cache hint but there is no allowance for any comments prior to the cache hint. In order to handle this an extra pragma needs to prefix the regular expression above: > {code} > "(?:/\\*[^\\+].+?\\*/(?:\\s+)?)?" > {code} > * (...)? => an optional group so no comment is handled > * ?: => the group is non-capturing so ignored by the matcher group count > * [^\\+] => checks for a + following the comment opener. Cache hints are expected to use this so this distinguishes a normal comment from a cache hint > * .+? => makes the comment contents non-greedy so the first comment closer is found rather than the last > * (?:\\s+)? => non-capturing optional group that checks for any whitespace between the end of the comment and the cache hint > Example patch for Designer parser added. > This cannot be rectified in Designer until it is rectified in Teiid. Even then, older versions of Teiid will never support this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2802) Address co-existence of SQL comment and cache hint

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-2802: ----------------------------------------- Summary: Address co-existence of SQL comment and cache hint Key: TEIIDDES-2802 URL: https://issues.jboss.org/browse/TEIIDDES-2802 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 9.2, 10.0 Reporter: Paul Richardson Attachments: 0001-Patch-to-address-failures-in-comments-and-cache-hint.patch An sql query, such as the following, parses but drops the cache hint {code} /* leading comment */ /*+ cache(ttl:180000) */ SELECT col1 FROM tbl {code} However, the same sql without the 'leading comment' retains the cache hint. The reason is that Designer uses the same parser handling syntax as the Teiid parser. Both use a regular expression for handling the cache hint, ie. {code} "/\\*\\+?\\s*cache(\\(\\s*(pref_mem)?\\s*(ttl:\\d{1,19})?\\s*(updatable)?\\s*(scope:(session|vdb|user))?\\s*(min:\\d{1,19})?[^\\)]*\\))?[^\\*]*\\*\\/.*"; {code} The dot-star (.*) at the end allows for the rest of the sql after the cache hint but there is no allowance for any comments prior to the cache hint. In order to handle this an extra pragma needs to prefix the regular expression above: {code} "(?:/\\*[^\\+].+?\\*/(?:\\s+)?)?" {code} * (...)? => an optional group so no comment is handled * ?: => the group is non-capturing so ignored by the matcher group count * [^\\+] => checks for a + following the comment opener. Cache hints are expected to use this so this distinguishes a normal comment from a cache hint * .+? => makes the comment contents non-greedy so the first comment closer is found rather than the last * (?:\\s+)? => non-capturing optional group that checks for any whitespace between the end of the comment and the cache hint Example patch for Designer parser added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2801) Cache hint is disappeared in the transformation editor

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2801?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-2801: ----------------------------------------- Assignee: Paul Richardson > Cache hint is disappeared in the transformation editor > ------------------------------------------------------ > > Key: TEIIDDES-2801 > URL: https://issues.jboss.org/browse/TEIIDDES-2801 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 10.0.1 > Environment: Fedora 23 > Reporter: Matej Kralik > Assignee: Paul Richardson > Attachments: Screenshot from 2016-03-03 13-29-56.png > > > When I put cache hint before SELECT query and I put comment before cache hint and save, transformation editor removes cache hint from SQL. Example from [TEIIDDES-2383 |https://issues.jboss.org/browse/TEIIDDES-2383] not work correctly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2800) Add back New Child >>View option to the View Model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2800?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2800: ----------------------------------- Fix Version/s: 9.0.6 10.0.1 > Add back New Child >>View option to the View Model > -------------------------------------------------- > > Key: TEIIDDES-2800 > URL: https://issues.jboss.org/browse/TEIIDDES-2800 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Fix For: 9.0.6, 10.0.1 > > > RFE https://issues.jboss.org/browse/TEIID-4010 has been entered to differentiate table and view, so would like to have New View and Table option under View Model > New Child. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2800) Add back New Child >>View option to the View Model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2800?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2800: -------------------------------------- Assignee: Barry LaFond > Add back New Child >>View option to the View Model > -------------------------------------------------- > > Key: TEIIDDES-2800 > URL: https://issues.jboss.org/browse/TEIIDDES-2800 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 9.0.6, 10.0.1 > > > RFE https://issues.jboss.org/browse/TEIID-4010 has been entered to differentiate table and view, so would like to have New View and Table option under View Model > New Child. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2800) Add back New Child >>View option to the View Model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2800?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2800: ----------------------------------- Component/s: Modeling Patch Release > Add back New Child >>View option to the View Model > -------------------------------------------------- > > Key: TEIIDDES-2800 > URL: https://issues.jboss.org/browse/TEIIDDES-2800 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Patch Release > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 9.0.6, 10.0.1 > > > RFE https://issues.jboss.org/browse/TEIID-4010 has been entered to differentiate table and view, so would like to have New View and Table option under View Model > New Child. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2664) Add Model Extension support for Procedure RESULTS OPTIONS

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2664?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2664: ---------------------------------------- This cannot be verified right now because of TEIIDDES-2798, I will look at this with next build. > Add Model Extension support for Procedure RESULTS OPTIONS > --------------------------------------------------------- > > Key: TEIIDDES-2664 > URL: https://issues.jboss.org/browse/TEIIDDES-2664 > Project: Teiid Designer > Issue Type: Enhancement > Components: ModeShape Integration, Patch Release, Teiid Integration > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Teiid DDL now supports options for procedure/functions returns clause parameters: > ... RETURNS (options ...) type > ... RETURNS (options ...) TABLE (...) > This was added to Teiid version 8.12 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2016