November 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1979) Changes to a table's columns can result in role being reset for the entire model - 7.7.x

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1979?page=com.atlassian.jira.plu... ] Johnathon Lee resolved TEIIDDES-1979. ------------------------------------- Resolution: Done > Changes to a table's columns can result in role being reset for the entire model - 7.7.x > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-1979 > URL: https://issues.jboss.org/browse/TEIIDDES-1979 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Johnathon Lee > Fix For: 7.7.5 > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2165) User can not use '.' for VDB name in order to version the VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2165?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2165: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1098413|https://bugzilla.redhat.com/show_bug.cgi?id=1098413] from ASSIGNED to MODIFIED > User can not use '.' for VDB name in order to version the VDB > ------------------------------------------------------------- > > Key: TEIIDDES-2165 > URL: https://issues.jboss.org/browse/TEIIDDES-2165 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.6.1, 9.0 > > > User can not use '.' for VDB name. > According to the Official document[1], user should be able to use '.' to specify the version for VDB. > [1]Administration_and_Configuration_Guide:11.2. Set the VDB Version > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Vir... > Version-Release number of selected component (if applicable): > Steps to Reproduce: > 1. Create a new VDB named "test1.1" > Actual results: > error occurs. Please check attached screenshot named vdb_versioning_error.png > Expected results: > User can use '.' for VDB name. > Additional info: > Teiid Designer 8.3.2.Final-v20140328-2123-B54 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1632) validation problems with trim and concat used together - 7.7.x

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1632?page=com.atlassian.jira.plu... ] Johnathon Lee resolved TEIIDDES-1632. ------------------------------------- Release Notes Text: Resolution: Done > validation problems with trim and concat used together - 7.7.x > -------------------------------------------------------------- > > Key: TEIIDDES-1632 > URL: https://issues.jboss.org/browse/TEIIDDES-1632 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 7.7 > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Fix For: 7.7.3 > > Attachments: Trimtest.zip > > > Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip). > On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error. > [1] > SELECT > ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME > FROM > CCH.MEMMAS AS Memb > [2] > SELECT > ((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME > FROM > CCH.MEMMAS AS Memb -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2382) No error message for query with aggregate function and no group by clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2382?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2382: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1161045|https://bugzilla.redhat.com/show_bug.cgi?id=1161045] from NEW to MODIFIED > No error message for query with aggregate function and no group by clause > ------------------------------------------------------------------------- > > Key: TEIIDDES-2382 > URL: https://issues.jboss.org/browse/TEIIDDES-2382 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 8.6 > Reporter: Jan Stastny > Assignee: Barry LaFond > > In designer when defining a table in view model with following transformation query, bad error message is returned to user. > SELECT cust.id AS customer_id, SUM(ord.amount) AS total_amount > FROM > customers AS cust INNER JOIN orders AS ord > ON cust.id = ord.customer_id > GROUP BY cust.id; > When user forgets to write the GROUP BY clause then error with following message occurs: "ERROR:ERROR". > When I execute similar query via teeid driver then I get very useful message: "Error: Remote org.teiid.api.exception.query.QueryValidatorException: Non-constant, non-aggregate expression cust.id cannot be mixed with aggregate functions and implicit grouping." > It would be very helpful if Teiid designer gave similar message instead of the "ERROR:ERROR" one. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2364) Remove .settings folder from Model Explorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2364?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2364. ------------------------------------ Resolution: Rejected The basic Eclipse already provides a simple/available filter option for .* file types. > Remove .settings folder from Model Explorer > ------------------------------------------- > > Key: TEIIDDES-2364 > URL: https://issues.jboss.org/browse/TEIIDDES-2364 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Joao Viragine > > Model Explorer should filter (don't show) the .settings folder in the Teiid Project Tree -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2341) Starting server does not result in full Teiid connection requiring Refresh action

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2341?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2341. ------------------------------------ Resolution: Done verified fix worked with master (9.0) as well. fix committed to 9.0.x and master. > Starting server does not result in full Teiid connection requiring Refresh action > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2341 > URL: https://issues.jboss.org/browse/TEIIDDES-2341 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.6.1 > Environment: Eclipse LUNA and JBoss Tools Luna TP > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Critical > Fix For: 9.0.1, 9.0 > > > 1) Testing against an EAP 6.1 Alpha + Teiid 8.7 runtime, I started the server and tried to preview a table. Warning dialog displayed indicating there was no Teiid connection. (not the Teiid contents in the server view indicated no Teiid connection) > 2) Clicked the Refresh button/action in the server view and could view the data sources & VDBs > 3) Tried preview again and it worked. > MORE INFO > * Creating a server configuration for DV6.1 ER3 (EAP 6.3) and starting does *not* show same behavior. The Teiid contents are displayed correctly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2341) Starting server does not result in full Teiid connection requiring Refresh action

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2341?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2341: ----------------------------------- Fix Version/s: 9.0.1 (was: 8.6.1) > Starting server does not result in full Teiid connection requiring Refresh action > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2341 > URL: https://issues.jboss.org/browse/TEIIDDES-2341 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.6.1 > Environment: Eclipse LUNA and JBoss Tools Luna TP > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Critical > Fix For: 9.0.1, 9.0 > > > 1) Testing against an EAP 6.1 Alpha + Teiid 8.7 runtime, I started the server and tried to preview a table. Warning dialog displayed indicating there was no Teiid connection. (not the Teiid contents in the server view indicated no Teiid connection) > 2) Clicked the Refresh button/action in the server view and could view the data sources & VDBs > 3) Tried preview again and it worked. > MORE INFO > * Creating a server configuration for DV6.1 ER3 (EAP 6.3) and starting does *not* show same behavior. The Teiid contents are displayed correctly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2387) Weird behaviour when creating parameters for procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2387?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2387. ------------------------------------ Resolution: Done the datatype editing support setElementValue() method was calling handleInfoChanged() which ended up refreshing the complete table. It was unnecessary, so removed it. commited to master, 8.6.x & 9.0.x > Weird behaviour when creating parameters for procedure > ------------------------------------------------------- > > Key: TEIIDDES-2387 > URL: https://issues.jboss.org/browse/TEIIDDES-2387 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Usability > Affects Versions: 9.0.1 > Environment: JBDS 8.0.0 > Windows 7 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.6.1, 9.0.1, 9.0 > > Attachments: params.webm > > > Adding of parameters to procedures behaves in a weird way (see attached screencast) on Windows, which prevents changing some parameters' data type. This happens in all dialogs that have parameter inputs (Relational View Procedure, Source Procedure, Source Function, Native Query Procedure), but not for e.g. columns input. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2387) Weird behaviour when creating parameters for procedure

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2387?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2387: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1161649|https://bugzilla.redhat.com/show_bug.cgi?id=1161649] from ASSIGNED to MODIFIED > Weird behaviour when creating parameters for procedure > ------------------------------------------------------- > > Key: TEIIDDES-2387 > URL: https://issues.jboss.org/browse/TEIIDDES-2387 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Usability > Affects Versions: 9.0.1 > Environment: JBDS 8.0.0 > Windows 7 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.6.1, 9.0.1, 9.0 > > Attachments: params.webm > > > Adding of parameters to procedures behaves in a weird way (see attached screencast) on Windows, which prevents changing some parameters' data type. This happens in all dialogs that have parameter inputs (Relational View Procedure, Source Procedure, Source Function, Native Query Procedure), but not for e.g. columns input. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2387) Weird behaviour when creating parameters for procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2387?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2387: ----------------------------------- Fix Version/s: 8.6.1 9.0.1 9.0 (was: 9.1) Steps to Reproduce: # Open the Create Relational View Procedure dialog # Switch to the paramters tab # Create enough new parameters for the last one to go off screen (so that it requires scrolling to see it) # Try to change that last parameter's data type, the view will jump and open the dropdown for a different parameter # This does not happen consistently, sometimes it works when a different column is selected first was: # Open the Create Relational View Procedure dialog # Switch to the paramters tab # Create enough new parameters for the last one to go off screen (so that it requires scrolling to see it) # Try to change that last parameter's data type, the view will jump and open the dropdown for a different parameter # This does not happen consistently, sometimes it works when a different column is selected first Assignee: Barry LaFond > Weird behaviour when creating parameters for procedure > ------------------------------------------------------- > > Key: TEIIDDES-2387 > URL: https://issues.jboss.org/browse/TEIIDDES-2387 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Usability > Affects Versions: 9.0.1 > Environment: JBDS 8.0.0 > Windows 7 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.6.1, 9.0.1, 9.0 > > Attachments: params.webm > > > Adding of parameters to procedures behaves in a weird way (see attached screencast) on Windows, which prevents changing some parameters' data type. This happens in all dialogs that have parameter inputs (Relational View Procedure, Source Procedure, Source Function, Native Query Procedure), but not for e.g. columns input. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2014