[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
[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
[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