September 2014 - teiid-designer-issues

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2331?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2331: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1136771 > Issues with renaming Source Model (8.3.4.CR1 + 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 > 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 + Windows 7)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2331?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2331: ----------------------------------- Attachment: log.log log from JBDS > Issues with renaming Source Model (8.3.4.CR1 + 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 > 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 + Windows 7)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2331?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2331: ----------------------------------- Attachment: screenshot1.png screenshot2.png screenshot3.png screenshot4.png screenshot5.png Dataroles_project.zip screenshots + project archive > Issues with renaming Source Model (8.3.4.CR1 + 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 > Environment: Windows 7 > Reporter: Matus Makovy > Attachments: Dataroles_project.zip, 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 + Windows 7)

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-2331: -------------------------------------- Summary: Issues with renaming Source Model (8.3.4.CR1 + 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 Environment: Windows 7 Reporter: Matus Makovy 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-2018) DDL importer creates wrong data type for "integer"

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ] Andrej Šmigala commented on TEIIDDES-2018: ------------------------------------------ [~blafond], what is supposed to be the resolution here? Because when I import the following DDL: {code:sql} CREATE FOREIGN TABLE "t1" ( c1 integer not null options (NAMEINSOURCE '"c1"', NATIVE_TYPE 'NUMBER') ) OPTIONS (NAMEINSOURCE 't1'); {code} I get the same result in 8.3.4 as in 8.3.3, that is the c1 column is created with datatype "integer : xs:decimal" (this is also true for 8.6) > DDL importer creates wrong data type for "integer" > -------------------------------------------------- > > Key: TEIIDDES-2018 > URL: https://issues.jboss.org/browse/TEIIDDES-2018 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.4, 8.3.4 > > Attachments: all_type_jdbc_import_from_vdb.png, types_comparison.png > > > When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model", > * if the DDL supplied is "Teiid" dialect > * if the data type supplied is "integer" > Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time. > This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long" -- 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: ---------------------------------------- It took me a while to understand this Masking and Row-based security. At least I think I understand it now. However, I think that the way that Teiid Designer mediates this functionality is still a bit confusing. In my opinion, it should somehow indicate that if user wants to create *Row-filtering* he has to choose *table (or view/procedure)* as target and if he wants to create *Masking* he has to choose *column* as target. (is it right? I hope so...) Long story short, you can not create *Row-filtering* when you have column as a target(resource-name).... I think this is the main problem that also Blaine is experiencing. If I understand, he tries to create Row-filtering and he has defined column(AccountsView.CUSTOMER.STATE) as target, entered _<>'New York'_ as condition and expects that Teiid Designer creates something like this in vbd.xml: {code} <permission> <resource-name>AccountsView.CUSTOMER</resource-name> <condition constraint="true">STATE<>'New York'</condition> </permission> {code} but, actually if you want to create +row-filtering+ you have to choose some +table+ as target (as for this example it should be AccountsView.CUSTOMER) and the condition should look like this _STATE<>'New York'_ > 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-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: ---------------------------------------- [https://docs.jboss.org/author/display/TEIID/XML+Definition] there are two separate examples one for row filtering (or row based security), one for the masking. I am not sure where the confusing part is, the above text is from row based security, the xml example is from masking. If you re-read my comment above, expression used in the condition is independent from the *resource* column/table. There is no restriction that it has to use same column. What document is saying is when condition is used, the expression must be able to evaluated against the parent table/view. Obviously you not can enter a Condition that uses table Y's columns, when you are defining a row filter or mask column on table X. > 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-2274) Row-based Security creates incorrect permission

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2274?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2274: ---------------------------------------- I think what's making this confusing is that the Teiid docs define *Row Based Scurity* as: *A permission against a fully qualified table/view/procedure may also specify a condition.....*. Yet in your XML example you define the following permission where the target is a column (i.e. *column1*): {code:xml} <permission> <resource-name>modelName.tblName.column1</resource-name> <condition>column2='x'</condition> <mask order="1">column1</mask> </permission> {code} Does the *condition* in the above example really apply to the table? (i.e. *tblName*) > 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-2321) java.lang.IllegalArgumentException: ImageRegistry key already in use at start-up with VDB Editor open

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2321?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2321 at 9/2/14 2:07 PM: ---------------------------------------------------------------- Done master: https://github.com/Teiid-Designer/teiid-designer/compare/27b69bde0b00...a... 8.3.x: https://github.com/Teiid-Designer/teiid-designer/commit/50d6a199bc258aa9e... was (Author: blafond): Done: https://github.com/Teiid-Designer/teiid-designer/compare/27b69bde0b00...a... > java.lang.IllegalArgumentException: ImageRegistry key already in use at start-up with VDB Editor open > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2321 > URL: https://issues.jboss.org/browse/TEIIDDES-2321 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Editors > Affects Versions: 8.5 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3.4, 8.6 > > > Stack Trace > {code} > Caused by: java.lang.IllegalArgumentException: ImageRegistry key already in use: icons/full/cview16/checked_box.png > at org.eclipse.jface.resource.ImageRegistry.put(ImageRegistry.java:254) > at org.teiid.designer.ui.common.AbstractUiPlugin.registerPluginImage(AbstractUiPlugin.java:291) > at org.teiid.designer.ui.common.UiPlugin$1.run(UiPlugin.java:95) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2321) java.lang.IllegalArgumentException: ImageRegistry key already in use at start-up with VDB Editor open

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2321?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2321: ----------------------------------- Fix Version/s: 8.3.4 > java.lang.IllegalArgumentException: ImageRegistry key already in use at start-up with VDB Editor open > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2321 > URL: https://issues.jboss.org/browse/TEIIDDES-2321 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Editors > Affects Versions: 8.5 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3.4, 8.6 > > > Stack Trace > {code} > Caused by: java.lang.IllegalArgumentException: ImageRegistry key already in use: icons/full/cview16/checked_box.png > at org.eclipse.jface.resource.ImageRegistry.put(ImageRegistry.java:254) > at org.teiid.designer.ui.common.AbstractUiPlugin.registerPluginImage(AbstractUiPlugin.java:291) > at org.teiid.designer.ui.common.UiPlugin$1.run(UiPlugin.java:95) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > {code} -- 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