September 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2314) VDB editor in TD 8.6 allows user to add source model from reused VDB

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2314?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2314: ---------------------------------------- *NOTE:* this is *verified only on 8.3.4.CR1* > VDB editor in TD 8.6 allows user to add source model from reused VDB > -------------------------------------------------------------------- > > Key: TEIIDDES-2314 > URL: https://issues.jboss.org/browse/TEIIDDES-2314 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Editors > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 8.3.4, 8.6 > > Attachments: screenshot1.png, screenshot2.png, screenshot3.png > > > VDB editor in Teiid Designer 8.6.0.Alpha1-v20140825-1403-B2763 allows me to add source model from reused VDB to new VDB. > The "New VDB" dialogoue accessed using New -> Teiid VDB doesn't allow me to do so (screenshot1) > But when I complete the creation of this VDB, edit this VDB and try to add new model using Edit VDB view, it allows me to add this source model without any warning. (screenshot2 and screenshot3) > NOTE: I can also get around this by selecting a vdb source model and right-click *New > VDB* ... it'll add the model to the VDB -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2196) Data Roles dialog issues

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2196?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2196: ---------------------------------------- I am not able to add screenshot right now, sorry... > Data Roles dialog issues > ------------------------ > > Key: TEIIDDES-2196 > URL: https://issues.jboss.org/browse/TEIIDDES-2196 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Dialogs > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.5, 8.3.4 > > Attachments: column-masking-dialog.png, permissions-row-filter-tab.png, row-based-security-dialog.png > > > There is one bug, few couple suggestions > 1) Rename "Conditions" tab to "Row Filter" > 2) Rename "Mask" tab "Column Masking" > 3) When somebody clicks "add" in conditions, the resource only applies to tables and views not columns. So, the the pick list should be on tables > 4) change the text on the this pop-up box, it says "Add Column Row-based security", that makes no sense to me. Say "Row based security through filtering", in description say "Provide any boolean based criteria (ex:...)" > 5) On masking "add" dialog, change > * target column ==> Column to Mask > * Masking ==> Column Expression > You can have hint in the bottom saying that, "Column Expression will be used in place of masked column in executed query" -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2196) Data Roles dialog issues

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2196?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2196: ---------------------------------------- Just one suggestion after conversation in TEIIDDES-2274 about the security beiing liitle confusing in TD... If I could suggest one more change, I would remove the security column in model panel or at least the functionality to define row-based security(on tables) and masking (on columns) this way. (screenshot) This was confusing for me when I tried to understand Data Roles in TD for the first time. I would leave there only Row Filter and Column masking panels/tabs to define row-based security and column masking. And maybe some enhancement to the dialogue that appears after you click _Add_ on the _Colum Masking_ panel would be great. It would make data roles security little less confusing in my opinion. Now there are 2 ways to define column masking and also 2 ways to define row filtering. But it's just a suggestion.... > Data Roles dialog issues > ------------------------ > > Key: TEIIDDES-2196 > URL: https://issues.jboss.org/browse/TEIIDDES-2196 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Dialogs > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.5, 8.3.4 > > Attachments: column-masking-dialog.png, permissions-row-filter-tab.png, row-based-security-dialog.png > > > There is one bug, few couple suggestions > 1) Rename "Conditions" tab to "Row Filter" > 2) Rename "Mask" tab "Column Masking" > 3) When somebody clicks "add" in conditions, the resource only applies to tables and views not columns. So, the the pick list should be on tables > 4) change the text on the this pop-up box, it says "Add Column Row-based security", that makes no sense to me. Say "Row based security through filtering", in description say "Provide any boolean based criteria (ex:...)" > 5) On masking "add" dialog, change > * target column ==> Column to Mask > * Masking ==> Column Expression > You can have hint in the bottom saying that, "Column Expression will be used in place of masked column in executed query" -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2274) Row-based Security creates incorrect permission

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2274?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2274: ---------------------------------------- Yes, I have seen it. I think that we have this branch available for testing. This updated Data roles editor is much better then the one in 8.3.3. > Row-based Security creates incorrect permission > ----------------------------------------------- > > Key: TEIIDDES-2274 > URL: https://issues.jboss.org/browse/TEIIDDES-2274 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Modeling, VDB & Execution > Affects Versions: 8.3.3 > Environment: OSX 10.9.4, Java 1.7.0_25. However, this bug has also been verified on a RHEL 7 instance as well. > Reporter: Blaine Mincey > Assignee: Barry LaFond > Labels: designer, teiid > Fix For: 8.3.4, 8.6, 8.5.1 > > > In modeling a VDB, when adding a condition for row-based security, an incorrect permission is created. For example, if using the Designer to select a column, the following condition is added: > <permission> > <resource-name>AccountsView.CUSTOMER.STATE</resource-name> > <condition constraint="true"><> 'New York'</condition> > </permission>. > In order for row-based security to work, the VDB.xml needs to be edited to be the following: > <permission> > <resource-name>AccountsView.CUSTOMER</resource-name> > <condition constraint="true">STATE <> 'New York'</condition> > </permission> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2332) Import VDB not redeployed after backing and changing import properties

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2332?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2332: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1136886 > Import VDB not redeployed after backing and changing import properties > ---------------------------------------------------------------------- > > Key: TEIIDDES-2332 > URL: https://issues.jboss.org/browse/TEIIDDES-2332 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Andrej Šmigala > > In Teiid Connection import, once the import VDB is deployed, going back in the dialog and changing import properties does not cause the VDB to redeploy -- clicking Next in the "Select the target model for the import" step moves directly to the next step, which shows the old DDL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2332) Import VDB not redeployed after backing and changing import properties

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2332: ---------------------------------------- Summary: Import VDB not redeployed after backing and changing import properties Key: TEIIDDES-2332 URL: https://issues.jboss.org/browse/TEIIDDES-2332 Project: Teiid Designer Issue Type: Bug Security Level: Public (Everyone can see) Components: Import/Export Affects Versions: 8.6 Reporter: Andrej Šmigala In Teiid Connection import, once the import VDB is deployed, going back in the dialog and changing import properties does not cause the VDB to redeploy -- clicking Next in the "Select the target model for the import" step moves directly to the next step, which shows the old DDL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2274) Row-based Security creates incorrect permission

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2274?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2274: ---------------------------------------- [~mmakovy] Please read TEIIDDES-2196 that is exactly what has been proposed and done, the question is that updates may not have committed to branch of code you are testing, which seems to be needed, then this can be marked as duplicate. > Row-based Security creates incorrect permission > ----------------------------------------------- > > Key: TEIIDDES-2274 > URL: https://issues.jboss.org/browse/TEIIDDES-2274 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Modeling, VDB & Execution > Affects Versions: 8.3.3 > Environment: OSX 10.9.4, Java 1.7.0_25. However, this bug has also been verified on a RHEL 7 instance as well. > Reporter: Blaine Mincey > Assignee: Barry LaFond > Labels: designer, teiid > Fix For: 8.3.4, 8.6, 8.5.1 > > > In modeling a VDB, when adding a condition for row-based security, an incorrect permission is created. For example, if using the Designer to select a column, the following condition is added: > <permission> > <resource-name>AccountsView.CUSTOMER.STATE</resource-name> > <condition constraint="true"><> 'New York'</condition> > </permission>. > In order for row-based security to work, the VDB.xml needs to be edited to be the following: > <permission> > <resource-name>AccountsView.CUSTOMER</resource-name> > <condition constraint="true">STATE <> 'New York'</condition> > </permission> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2307) Wrong columns are presented when defining primary key

by Greg MacKinnon (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2307?page=com.atlassian.jira.plu... ] Greg MacKinnon commented on TEIIDDES-2307: ------------------------------------------ Thanks, Barry. I'll attach a model project with the view model in question. > Wrong columns are presented when defining primary key > ----------------------------------------------------- > > Key: TEIIDDES-2307 > URL: https://issues.jboss.org/browse/TEIIDDES-2307 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Environment: teiid designer 8.6, teiid 8.7, windows 7 > Reporter: Greg MacKinnon > > I can define a primary key for a view model entity. If I then try to define a primary key on another entity in the same view model, the columns I can choose from are those related to the entity I first defined a primary key for. I can define a unique constraint on this second entity but not a primary key. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2331) Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2331?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2331: ----------------------------------- Affects Version/s: 8.6 > Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7) > ------------------------------------------------------------------- > > Key: TEIIDDES-2331 > URL: https://issues.jboss.org/browse/TEIIDDES-2331 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.3.4, 8.6 > Environment: Windows 7 > Reporter: Matus Makovy > Attachments: Dataroles_project.zip, log.log, screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png, screenshot5.png > > > There is couple of issues with renaming source model that is referenced in some view model. > I am using project Dataroles_project.zip (attached) > 1. I tried to rename Products_source.xmi to Products_source1.xmi > * this generates some error in log but it works... > *[screenshot1.png] > 2. Rename Products_source1.xmi to Products_source2.xmi > * this fails to rewrite the reference in view model > * I changed the references manually > *[screenshot2.png and screenshot3.png] > 3. Remane Products_source2.xmi to Products_source3.xmi > * this deletes tables from view model > *[screenshot4.png and screenshot5.png] > This problem occurs only on Windows, Linux is fine... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2331) Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2331?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2331: ----------------------------------- Summary: Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7) (was: Issues with renaming Source Model (8.3.4.CR1 + Windows 7)) > Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7) > ------------------------------------------------------------------- > > Key: TEIIDDES-2331 > URL: https://issues.jboss.org/browse/TEIIDDES-2331 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.3.4, 8.6 > Environment: Windows 7 > Reporter: Matus Makovy > Attachments: Dataroles_project.zip, log.log, screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png, screenshot5.png > > > There is couple of issues with renaming source model that is referenced in some view model. > I am using project Dataroles_project.zip (attached) > 1. I tried to rename Products_source.xmi to Products_source1.xmi > * this generates some error in log but it works... > *[screenshot1.png] > 2. Rename Products_source1.xmi to Products_source2.xmi > * this fails to rewrite the reference in view model > * I changed the references manually > *[screenshot2.png and screenshot3.png] > 3. Remane Products_source2.xmi to Products_source3.xmi > * this deletes tables from view model > *[screenshot4.png and screenshot5.png] > This problem occurs only on Windows, Linux is fine... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014