August 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2261) Creating condition(row-based security) on table creates also masking

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2261?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2261: ----------------------------------- Fix Version/s: 8.6 > Creating condition(row-based security) on table creates also masking > --------------------------------------------------------------------- > > Key: TEIIDDES-2261 > URL: https://issues.jboss.org/browse/TEIIDDES-2261 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.3 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 8.3.4, 8.6 > > Attachments: screen1.png, screen2.png, screen3.png, screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png, screenshot5.png > > > When I create condition on table, Teiid Designer also creates masking for that table. This masking is blank and has no effect, but Designer shows it in the Edit VDB Data Role dialogue. > The masking isn't added in vdb.xml > (screenshots) > JBDS 7.1.1.GA + Teiid Designer 8.3.3 Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2261) Creating condition(row-based security) on table creates also masking

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2261?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2261. ------------------------------------ Resolution: Done Reproduced and commited fixes. master: https://github.com/Teiid-Designer/teiid-designer/commit/27b69bde0b00de912... 8.3.x: https://github.com/Teiid-Designer/teiid-designer/commit/f478e479d84e8fe49... > Creating condition(row-based security) on table creates also masking > --------------------------------------------------------------------- > > Key: TEIIDDES-2261 > URL: https://issues.jboss.org/browse/TEIIDDES-2261 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.3 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 8.3.4 > > Attachments: screen1.png, screen2.png, screen3.png, screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png, screenshot5.png > > > When I create condition on table, Teiid Designer also creates masking for that table. This masking is blank and has no effect, but Designer shows it in the Edit VDB Data Role dialogue. > The masking isn't added in vdb.xml > (screenshots) > JBDS 7.1.1.GA + Teiid Designer 8.3.3 Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2261) Creating condition(row-based security) on table creates also masking

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2261?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2261: ----------------------------------- Attachment: screenshot1.png screenshot2.png screenshot3.png screenshot4.png screenshot5.png Screenshots that were attached to this JIRA were old, these are new. > Creating condition(row-based security) on table creates also masking > --------------------------------------------------------------------- > > Key: TEIIDDES-2261 > URL: https://issues.jboss.org/browse/TEIIDDES-2261 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.3 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 8.3.4 > > Attachments: screen1.png, screen2.png, screen3.png, screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png, screenshot5.png > > > When I create condition on table, Teiid Designer also creates masking for that table. This masking is blank and has no effect, but Designer shows it in the Edit VDB Data Role dialogue. > The masking isn't added in vdb.xml > (screenshots) > JBDS 7.1.1.GA + Teiid Designer 8.3.3 Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Ramesh Reddy edited comment on TEIIDDES-2256 at 8/28/14 11:21 PM: ------------------------------------------------------------------ [~van.halbert] I am not sure what you are disagreeing with nor the motivation behind feature request for TEIIDDES-2238 Let me see if I can recap.. Teiid exposes a limited set of runtime types, they have *defined* mappings to Design time data types in designer. Each design time data type also for modeling validation purposes map to XSD types. The core of *this* issue is, currently the mapping of integer is DT --> XSD --> RUNTIME integer --> xs:integer --> biginteger Which is wrong. I am saying it should be integer --> xs:long --> integer int --> xs:long --> integer biginteger --> xs:integer --> biginteger Now the mapping happens automatically during the import, because those are the types that Server defined according to the metadata exposed by the translator. If user changes the data type in the Designer, and not proper "convert" functions available then the query is certain to fail. So by default, we should map exactly as defined by translator. I do not see a need to provide a mapping *per* source that differs from translator type by default, which I see as gist of TEIIDDES-2238. BTW user can change data type manually anytime they want, I am not sure what is being mentioned in JBDVPL-149 which is not at all clear for me in its intent. was (Author: rareddy): [~van.halbert] I am not sure what you are disagreeing with nor the motivation behind feature request for TEIID-2238 Let me see if I can recap.. Teiid exposes a limited set of runtime types, they have *defined* mappings to Design time data types in designer. Each design time data type also for modeling validation purposes map to XSD types. The core of *this* issue is, currently the mapping of integer is DT --> XSD --> RUNTIME integer --> xs:integer --> biginteger Which is wrong. I am saying it should be integer --> xs:long --> integer int --> xs:long --> integer biginteger --> xs:integer --> biginteger Now the mapping happens automatically during the import, because those are the types that Server defined according to the metadata exposed by the translator. If user changes the data type in the Designer, and not proper "convert" functions available then the query is certain to fail. So by default, we should map exactly as defined by translator. I do not see a need to provide a mapping *per* source that differs from translator type by default, which I see as gist of TEIIDDES-2238. BTW user can change data type manually anytime they want, I am not sure what is being mentioned in JBDVPL-149 which is not at all clear for me in its intent. > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 8.7, 8.6.1 > > Attachments: full-datatypes-1.png, full-datatypes-2.png, set-datatype-dialog.png, set-datatype-dialog_2.png > > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2256: ---------------------------------------- [~van.halbert] I am not sure what you are disagreeing with nor the motivation behind feature request for TEIID-2238 Let me see if I can recap.. Teiid exposes a limited set of runtime types, they have *defined* mappings to Design time data types in designer. Each design time data type also for modeling validation purposes map to XSD types. The core of *this* issue is, currently the mapping of integer is DT --> XSD --> RUNTIME integer --> xs:integer --> biginteger Which is wrong. I am saying it should be integer --> xs:long --> integer int --> xs:long --> integer biginteger --> xs:integer --> biginteger Now the mapping happens automatically during the import, because those are the types that Server defined according to the metadata exposed by the translator. If user changes the data type in the Designer, and not proper "convert" functions available then the query is certain to fail. So by default, we should map exactly as defined by translator. I do not see a need to provide a mapping *per* source that differs from translator type by default, which I see as gist of TEIIDDES-2238. BTW user can change data type manually anytime they want, I am not sure what is being mentioned in JBDVPL-149 which is not at all clear for me in its intent. > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 8.7, 8.6.1 > > Attachments: full-datatypes-1.png, full-datatypes-2.png, set-datatype-dialog.png, set-datatype-dialog_2.png > > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2314?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2314: --------------------------------------------------- Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1133928|https://bugzilla.redhat.com/show_bug.cgi?id=1133928] from MODIFIED to VERIFIED > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2293) Issues with inputs in VDB model Source Binding Definition view

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2293?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2293: --------------------------------------------------- Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1131152|https://bugzilla.redhat.com/show_bug.cgi?id=1131152] from MODIFIED to VERIFIED > Issues with inputs in VDB model Source Binding Definition view > -------------------------------------------------------------- > > Key: TEIIDDES-2293 > URL: https://issues.jboss.org/browse/TEIIDDES-2293 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Editors > Affects Versions: 8.3.3 > Environment: Windows 7 > Reporter: Matus Makovy > Assignee: Mark Drilling > Fix For: 8.3.4, 8.6, 8.5.1 > > Attachments: screen.png > > > I can't change Translator Name or JDNI Name without clicking on the particular row in Source Name column -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2139) 2 Connections to same VDB in JBDS seem to share one password

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2139?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2139: --------------------------------------------------- Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1093617|https://bugzilla.redhat.com/show_bug.cgi?id=1093617] from MODIFIED to VERIFIED > 2 Connections to same VDB in JBDS seem to share one password > ------------------------------------------------------------ > > Key: TEIIDDES-2139 > URL: https://issues.jboss.org/browse/TEIIDDES-2139 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Teiid Integration > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.3.4, 8.6, 8.5.1 > > > Description of problem: > Connections to same VDB seem to share one password. > I have 2 connections to one VDB and each connection should use different username and password(one with longer password and the other one with shorter). > When I save the password in configuration of the first connection, the second connection doesn't work. In the preferences of the second one is obvious that the saved password is too long to be right, after retyping the password this connection works, but the other one doesn't... > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2260) Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2260?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2260: --------------------------------------------------- Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1122470|https://bugzilla.redhat.com/show_bug.cgi?id=1122470] from MODIFIED to VERIFIED > Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions) > -------------------------------------------------------------------------- > > Key: TEIIDDES-2260 > URL: https://issues.jboss.org/browse/TEIIDDES-2260 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.3 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.3.4, 8.6, 8.5.1 > > > I don't know if it is a bug or there is some reason for that. > When I create a condition for Data Role(& Save VDB) and then remove the condition(& Save VDB) Teiid Designer doesn't delete whole <permission> tag only the <condition> tag > For example: > Before removing > <permission> > <resource-name>Products_view.PRODUCTDATA</resource-name> > <condition constraint="true">ISAMEXINT=1</condition> > </permission> > After removing: > <permission> > <resource-name>Products_view.PRODUCTDATA</resource-name> > </permission> > In my opinion Teiid Designer should delete whole <permission> tag and leave nothing behind.. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2164) Editing teiid importer connection url can't be finished

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2164?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2164: --------------------------------------------------- Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1099078|https://bugzilla.redhat.com/show_bug.cgi?id=1099078] from NEW to VERIFIED > Editing teiid importer connection url can't be finished > ------------------------------------------------------- > > Key: TEIIDDES-2164 > URL: https://issues.jboss.org/browse/TEIIDDES-2164 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Assignee: Ted Jones > Priority: Blocker > Fix For: 8.5, 8.3.4 > > Attachments: bug.png > > > I have Teiid importer connection set up without authentication and when I try to edit its URL I get an error message "The User Name cannot be empty" (the same with password) but my connection doesn't need authentication, so I don't have any username or password. 'OK' button is disabled. > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2014