[JBoss JIRA] (TEIIDDES-1974) Source Function/UDF wizards issues
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-1974:
--------------------------------------
Summary: Source Function/UDF wizards issues
Key: TEIIDDES-1974
URL: https://issues.jboss.org/browse/TEIIDDES-1974
Project: Teiid Designer
Issue Type: Bug
Components: Dialogs
Reporter: Ramesh Reddy
#1 Right now Source Function and UDF has "Update Count" selections, these need to be removed. This option only need to exist in the "procedures"
#2 Non-Prepared is also property of procedure, not functions
#3 UDF can not return resultset, remove the tab
#4 Source Function - Needs all the
- Deterministic, Returns Null on Null, Variable arguments
- Aggregate properties as in UDF
#5 possible change the main menu item from just Procedure to "procedure/function"
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1973) Designer VDB Deployment rules too restrictive
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1973:
--------------------------------------
Summary: Designer VDB Deployment rules too restrictive
Key: TEIIDDES-1973
URL: https://issues.jboss.org/browse/TEIIDDES-1973
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Blocker
Fix For: 8.3
VdbDeployer fails deployment if...
* translator is missing for a source
* connection profile is missing for a source model
Should be....
* translator is REQUIRED by vdb schema
* JNDI name can be NULL
Fix should include:
* Validation rule added for VDB's to check for translator == NULL (ERROR)
* Validation rule added for VDB's to check for JNDI name == NULL (Warning)
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1911?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1911:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1024875|https://bugzilla.redhat.com/show_bug.cgi?id=1024875] from MODIFIED to ON_QA
> Teiid Connection lacks a way to define importer properties
> ----------------------------------------------------------
>
> Key: TEIIDDES-1911
> URL: https://issues.jboss.org/browse/TEIIDDES-1911
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> In Teiid Connection importer, it lacks a way to define the "import" properties that makes usage cumbersome for user to define to import specific parts of schema, or sometimes impossible (see TEIID-1905)
> basically, when user chooses the "translator", after they should be able define some custom key/value pairs as properties, when then should be converted as model import properties in "importVDB-vdb.xml" file. Some sample properties are defined here
> https://docs.jboss.org/author/display/TEIID/JDBC+Translator
> see "importer" properties. Do not confuse similar "execution properties" which are translator overrides. The sample vdb is like this
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="hive" version="1">
> <description>Shows how to query HiveVDB using Hive</description>
> <property name="UseConnectorMetadata" value="cached"/>
> <model name="hive">
> <property name="importer.trimColumnNames" value="true"/>
> <source name="Hive conector" translator-name="hive" connection-jndi-name="java:/hive-ds"/>
> </model>
> </vdb>
> {code}
> As per GUI concerned it should be added in "Select the translator and target model" panel, after the selection of translator
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1905:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1024875|https://bugzilla.redhat.com/show_bug.cgi?id=1024875] from MODIFIED to ON_QA
> TrimColumn names should be enabled with hive translator metadata import
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1905
> URL: https://issues.jboss.org/browse/TEIIDDES-1905
> Project: Teiid Designer
> Issue Type: Bug
> Environment: DV Beta
> Teiid Designer 8.3.Beta2
> Reporter: Filip Nguyen
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> *Problem*
> Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names.
> *Why*
> There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1947) Text area is initially too large
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1947?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1947.
---------------------------------------
Resolution: Done
> Text area is initially too large
> --------------------------------
>
> Key: TEIIDDES-1947
> URL: https://issues.jboss.org/browse/TEIIDDES-1947
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Environment: KDE 4, Fedora 17, JBDS 7.1.0.CR1
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Priority: Minor
> Attachments: create-table-wizard-ubuntu.png, issue.png, xml-importer-using-guide-action-post-workaround.png, xml-importer-using-guide-action.png, xml-importer-using-import-wizard-post-workaround.png, xml-importer-using-import-wizard.png
>
>
> When creating a child table on model and clicking on the Transformation SQL tab, I see the SQL Definition text area blocking out the heading. If I resize the dialog it looks ok.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1947) Text area is initially too large
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1947?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1947:
-------------------------------------------
Merged branch and pushed to master.
> Text area is initially too large
> --------------------------------
>
> Key: TEIIDDES-1947
> URL: https://issues.jboss.org/browse/TEIIDDES-1947
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Environment: KDE 4, Fedora 17, JBDS 7.1.0.CR1
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Priority: Minor
> Attachments: create-table-wizard-ubuntu.png, issue.png, xml-importer-using-guide-action-post-workaround.png, xml-importer-using-guide-action.png, xml-importer-using-import-wizard-post-workaround.png, xml-importer-using-import-wizard.png
>
>
> When creating a child table on model and clicking on the Transformation SQL tab, I see the SQL Definition text area blocking out the heading. If I resize the dialog it looks ok.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1957) Odd behavior after "Save AS" and refactor
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1957?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1957.
---------------------------------------
Resolution: Cannot Reproduce Bug
> Odd behavior after "Save AS" and refactor
> -----------------------------------------
>
> Key: TEIIDDES-1957
> URL: https://issues.jboss.org/browse/TEIIDDES-1957
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Fix For: 8.3
>
> Attachments: project.zip
>
>
> Used Save AS to copy one model to another project. Then attempted to enter transformation sql, the sql contained references using a different model name so I refactored the new model. The open transformation editor would not revalidate. After closing, reopening, and rebuilding I then see "Unresolved reference errors". And those seem to be cleared after clearing those by simply reopening the editor.
--
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
10 years, 7 months