March 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2063) Is there a way to provide option to change data types for virtual tables or procedures when source data type is changed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2063?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2063: ----------------------------------- Summary: Is there a way to provide option to change data types for virtual tables or procedures when source data type is changed (was: Is there a way to provide option to change views when source data type is changed) > Is there a way to provide option to change data types for virtual tables or procedures when source data type is changed > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2063 > URL: https://issues.jboss.org/browse/TEIIDDES-2063 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.3.1 > Reporter: Van Halbert > Fix For: Future > > > Also at issue is when a data source column type needs to be changed in the source model, but the views also need to be changed. Is there a way to replicate the change upstream (so to speak) to all the dependent views? -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1898) Connection Profile requires a password for preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1898?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1898: ----------------------------------- Fix Version/s: 8.5 Assignee: Mark Drilling > Connection Profile requires a password for preview > -------------------------------------------------- > > Key: TEIIDDES-1898 > URL: https://issues.jboss.org/browse/TEIIDDES-1898 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Fix For: 8.5 > > > Some data sources can work without user name and/or password for connecting to the source. So, those properties are not mandatory and requiring them for preview is unnecessary if they are not defined. > In this example, Hive Connection profile was created with username but with out password, when the Teiid Connection importer used and them a connection profile is set on it to use the preview, it failed until a dummy password is provided -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2070) add search/replace to the Teiid Designer-->search transformations feature

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2070?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2070: ----------------------------------- Fix Version/s: 8.5 > add search/replace to the Teiid Designer-->search transformations feature > ------------------------------------------------------------------------- > > Key: TEIIDDES-2070 > URL: https://issues.jboss.org/browse/TEIIDDES-2070 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > Fix For: 8.5 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2070) add search/replace to the Teiid Designer-->search transformations feature

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2070?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2070: ----------------------------------- Assignee: Paul Richardson > add search/replace to the Teiid Designer-->search transformations feature > ------------------------------------------------------------------------- > > Key: TEIIDDES-2070 > URL: https://issues.jboss.org/browse/TEIIDDES-2070 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > Assignee: Paul Richardson > Fix For: 8.5 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2070) add search/replace to the Teiid Designer-->search transformations feature

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2070?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2070: ----------------------------------- Component/s: Editors Transformations > add search/replace to the Teiid Designer-->search transformations feature > ------------------------------------------------------------------------- > > Key: TEIIDDES-2070 > URL: https://issues.jboss.org/browse/TEIIDDES-2070 > Project: Teiid Designer > Issue Type: Feature Request > Components: Editors, Transformations > Reporter: Tom Johnston > Assignee: Paul Richardson > Fix For: 8.5 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2072) Teiid connection import generates invalid DDL for hsql data source

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2072?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2072: ---------------------------------------- This is issue with Modeshape's Teiid DDL Parser Logic > Teiid connection import generates invalid DDL for hsql data source > ------------------------------------------------------------------ > > Key: TEIIDDES-2072 > URL: https://issues.jboss.org/browse/TEIIDDES-2072 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Environment: JBTIS 4.1.3.Final, JBDS 7.1.0.GA, DV 6 CR2, Fedora 19 > Reporter: Lucie Fabrikova > Attachments: ds1.script, hsqlDDL.ddl > > > Teiid importer teiid connection >> source model generates invalid DDL for HSQL data source. > Message: The DDL failed to parse with message: > "Unparsable options clause". - The problem line is highlighted below (if found). IS_NULLABLE string(3) OPTIONS (ANNOTATION 'is column nullable?: { YES (might allow) | NO (definitely not) | '''' (unknown) }', NAMEINSOURCE '"IS_NULLABLE"', NATIVE_TYPE 'VARCHAR'), -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2074) Improve the Teiid Connection importer usability

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2074?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2074: ----------------------------------- Fix Version/s: 8.5 > Improve the Teiid Connection importer usability > ----------------------------------------------- > > Key: TEIIDDES-2074 > URL: https://issues.jboss.org/browse/TEIIDDES-2074 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Van Halbert > Fix For: 8.5 > > > Teiid Connection importer needs to be easier to use. Currently, the user has to open the documentation to know what properties to enter so that, for example, the jdbc import is filtering on tables types, schemas, etc. Otherwise, the importer will grab everything. For JDBC, it should be as easy as the current JDBC importer. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2081) Usability: When creating datasource for VDB under Teiid server, indicate to the user what JNDI name to use

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2081?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2081. ------------------------------------ Resolution: Done Done > Usability: When creating datasource for VDB under Teiid server, indicate to the user what JNDI name to use > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2081 > URL: https://issues.jboss.org/browse/TEIIDDES-2081 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dialogs > Affects Versions: 8.3.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Attachments: server-view-with-jndi-names.png > > > In the Teiid Server view, and selecting the VDB to create the datasource, need to indicate to user what the JNDI name will be so that they can use it. Maybe, since there is a standard pattern for creating the JNDI name, show the pattern and where the VDB name will be substituted: example: java:/{VDBName} > JNDI name already exists on the DS label. > Need to add the formatting to the Create VDB DS dialog -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2081) Usability: When creating datasource for VDB under Teiid server, indicate to the user what JNDI name to use

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2081?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2081: ----------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/308 > Usability: When creating datasource for VDB under Teiid server, indicate to the user what JNDI name to use > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2081 > URL: https://issues.jboss.org/browse/TEIIDDES-2081 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dialogs > Affects Versions: 8.3.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Attachments: server-view-with-jndi-names.png > > > In the Teiid Server view, and selecting the VDB to create the datasource, need to indicate to user what the JNDI name will be so that they can use it. Maybe, since there is a standard pattern for creating the JNDI name, show the pattern and where the VDB name will be substituted: example: java:/{VDBName} > JNDI name already exists on the DS label. > Need to add the formatting to the Create VDB DS dialog -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2079) Add valdiation of REST extension properties for virtual procedures

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2079?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2079. ------------------------------------ Resolution: Done Done > Add valdiation of REST extension properties for virtual procedures > ------------------------------------------------------------------ > > Key: TEIIDDES-2079 > URL: https://issues.jboss.org/browse/TEIIDDES-2079 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling, Validation > Affects Versions: 8.4 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.5 > > > The recognition of REST extension properties keys off of both REST METHOD and REST URI properties either both being present or both null. > Workspace Validation: Create a RestPropertiesValidationRule to create a problem marker if this is not the case > Procedure Wizard validation: > * Add CHARSET and HEADERS property Widgets to ViewProcedureEditorPanel > * Add charset and header instance variables to RelationalViewProcedure object (include getter/setter methods) > * Add validation to ViewProcedureEditorPanel to verify the same. > Thinking in both instances we should default the severity to WARNING and not error. -- 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

12 years

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 March 2014