June 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1740) Create Data Source Should not Prompt for Password for Non-Secured WS Sources

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1740?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1740: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/183 > Create Data Source Should not Prompt for Password for Non-Secured WS Sources > ---------------------------------------------------------------------------- > > Key: TEIIDDES-1740 > URL: https://issues.jboss.org/browse/TEIIDDES-1740 > Project: Teiid Designer > Issue Type: Bug > Reporter: Ted Jones > Assignee: Ted Jones > > When creating a DS for an unsecured OData WS, I am forced to add a password which gets added the the resource adapter configuration. We should determine if authentication in NONE in the case of WS data sources and not prompt for a password in those cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1740) Create Data Source Should not Prompt for Password for Non-Secured WS Sources

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1740?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1740. --------------------------------- Fix Version/s: 8.2 Resolution: Done Added check to see if password was required before prompting for password during data source creation > Create Data Source Should not Prompt for Password for Non-Secured WS Sources > ---------------------------------------------------------------------------- > > Key: TEIIDDES-1740 > URL: https://issues.jboss.org/browse/TEIIDDES-1740 > Project: Teiid Designer > Issue Type: Bug > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > > When creating a DS for an unsecured OData WS, I am forced to add a password which gets added the the resource adapter configuration. We should determine if authentication in NONE in the case of WS data sources and not prompt for a password in those cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1760) Teiid Server Cache Does not Update After Adding Preview Source

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1760: ----------------------------------- Summary: Teiid Server Cache Does not Update After Adding Preview Source Key: TEIIDDES-1760 URL: https://issues.jboss.org/browse/TEIIDDES-1760 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview Affects Versions: 8.2 Reporter: Ted Jones Fix For: 8.2 After a preview source is added, the Teiid server cache is not updated until a manual refresh is invoked. This prevents previously previewed sources from being added since we attempt to re-add since we aren't aware it is already there (an error is received stating that the source already exists and we need to give it a new name). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1674) DDL Importer - does not handle extension properties

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1674?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1674: ----------------------------------------- Initial commit for the incorporation of extension property processing, after refactoring of the framework: https://github.com/Teiid-Designer/teiid-designer/pull/182 Will continue testing and refining the import process. > DDL Importer - does not handle extension properties > --------------------------------------------------- > > Key: TEIIDDES-1674 > URL: https://issues.jboss.org/browse/TEIIDDES-1674 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Priority: Blocker > Fix For: 8.2 > > > The DDL Importer currently does not fully support import of Function Procedures from Teiid DDL. An example: > CREATE VIRTUAL FUNCTION F4( > flag boolean, > msg varchar > ) RETURNS varchar > OPTIONS ( > CATEGORY 'misc', > DETERMINISM 'DETERMINISTIC', > "NULL-ON-NULL" 'true', > JAVA_CLASS 'foo', > JAVA_METHOD 'bar' > ); > The current DDL Importer cannot easily set properties which are implemented as extension properties. Examples are CATEGORY, JAVA_CLASS, JAVA_METHOD in the above example. > We should look into re-working the DDL Importer to use Barry's framework for creating relational objects. I believe that framework has built in support for the extension properties. > Importing for Salesforce connection will also not work, nor a simple DB where Native Query values are set on tables -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1759) DdlImporter throws illegal arg exceptions if model name is empty. Should be validation error and message in SelectTranslatorAndTargetPage

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1759: -------------------------------------- Summary: DdlImporter throws illegal arg exceptions if model name is empty. Should be validation error and message in SelectTranslatorAndTargetPage Key: TEIIDDES-1759 URL: https://issues.jboss.org/browse/TEIIDDES-1759 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Paul Richardson Fix For: 8.2 Setting the ddl source model name to non-null, then deleting the name results in an Illegal Arg exception rather than just an ERROR on the page (SelectTranslatorAndTargetPage) The DdlImporter is doing arg/validation checks in setModelName() but seems like the DdlImporter should create a MultiStatus() which can be used by the importer UI to show .... the status rather then throw/catch an exception -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1758) NPE in DDL Importer if Resource is Not Selected Prior to Import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1758?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1758. ------------------------------------ Resolution: Done added null model name check during UI construction > NPE in DDL Importer if Resource is Not Selected Prior to Import > --------------------------------------------------------------- > > Key: TEIIDDES-1758 > URL: https://issues.jboss.org/browse/TEIIDDES-1758 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.2 > > > If I try to import using Teiid Connection to Source Model, I receive an NPE if I have not selected a resource in the workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1758) NPE in DDL Importer if Resource is Not Selected Prior to Import

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1758?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1758: -------------------------------- Issue Type: Bug (was: Feature Request) > NPE in DDL Importer if Resource is Not Selected Prior to Import > --------------------------------------------------------------- > > Key: TEIIDDES-1758 > URL: https://issues.jboss.org/browse/TEIIDDES-1758 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ted Jones > Fix For: 8.2 > > > If I try to import using Teiid Connection to Source Model, I receive an NPE if I have not selected a resource in the workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1758) NPE in DDL Importer if Resource is Not Selected Prior to Import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1758?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1758: -------------------------------------- Assignee: Barry LaFond > NPE in DDL Importer if Resource is Not Selected Prior to Import > --------------------------------------------------------------- > > Key: TEIIDDES-1758 > URL: https://issues.jboss.org/browse/TEIIDDES-1758 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.2 > > > If I try to import using Teiid Connection to Source Model, I receive an NPE if I have not selected a resource in the workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1758) NPE in DDL Importer if Resource is Not Selected Prior to Import

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1758: ----------------------------------- Summary: NPE in DDL Importer if Resource is Not Selected Prior to Import Key: TEIIDDES-1758 URL: https://issues.jboss.org/browse/TEIIDDES-1758 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 8.2 Reporter: Ted Jones Fix For: 8.2 If I try to import using Teiid Connection to Source Model, I receive an NPE if I have not selected a resource in the workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1548: ---------------------------------------- {code:title=VDB with column masking} <?xml version="1.0" encoding="UTF-8"?> <vdb name="sample" version="1"> <model name="modelName"> <source name="source-name" translator-name="oracle" connection-jndi-name="java:myDS" /> </model> <data-role name="base-role" any-authenticated="true"> <description>Masking</description> <permission> <resource-name>modelName.tblName.column1</resource-name> <mask>CASE WHEN column1=user() THEN column1 END</mask> </permission> </data-role> <data-role name="RoleA"> <description>Read/Insert access.</description> <permission> <resource-name>modelName.tblName</resource-name> <allow-read>true</allow-read> <allow-create>true</allow-create> </permission> <permission> <resource-name>modelName.tblName.column1</resource-name> <condition>column2='x'</condition> <mask order="1">column1</mask> </permission> <mapped-role-name>role1</mapped-role-name> </data-role> </vdb> {code} > Add GUI handling for permission conditions > ------------------------------------------ > > Key: TEIIDDES-1548 > URL: https://issues.jboss.org/browse/TEIIDDES-1548 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.2 > > > A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: > <permission> > <resource-name>...</resource-name> > <condition>sql</condition> > ... > </permission> > The sql should resolve against the resource specified, ideally designer would check that as well. > See TEIID-2311 and the reference for how these conditions are applied. > {code:title=vdb.xml snippet} > <data-role name="base-role" any-authenticated="true"> > <description>Conditional access</description> > > <permission> > <resource-name>modelName.tblName</resource-name> > <condition constraint="false">column1=user()</condition> > </permission> > > </data-role> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2013