[JBoss JIRA] (TEIIDDES-2630) Procedure Writing in Teiid
by Jayesh Garg (JIRA)
Jayesh Garg created TEIIDDES-2630:
-------------------------------------
Summary: Procedure Writing in Teiid
Key: TEIIDDES-2630
URL: https://issues.jboss.org/browse/TEIIDDES-2630
Project: Teiid Designer
Issue Type: Bug
Reporter: Jayesh Garg
Priority: Critical
I created a Procedure using Cassandra as the Datasource. The procedure has 1 input and 2 outputs. I use the input to run a query which retrieves me a unique identifier which is the input for the 2nd table. When I fire another query on the 2nd table, data is retrieved but I am unable to assign it to my OUT parameters.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2340) UI issues with Luna Target Platform
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2340?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2340.
----------------------------------
> UI issues with Luna Target Platform
> -----------------------------------
>
> Key: TEIIDDES-2340
> URL: https://issues.jboss.org/browse/TEIIDDES-2340
> Project: Teiid Designer
> Issue Type: Bug
> Components: Eclipse Integration
> Affects Versions: 8.6
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 9.0, 8.6.1
>
>
> Due to the upgrade to the Luna target-platform, a few UI anomalies have started to occur, including:
> * Open VDB Editor and select "Advanced" tab and it's EMPTY. Re-size and it shows up;
> * Open Data Role Wizard and click on Row FIlter or Column Masking tabs and only the "NAME" column is displayed. the others aren't there;
> * Same Data Role Wizard "Options" tab is empty until resizing;
> * VDB Editor Source Binding Definition tab doesn't show selection or columns.
> These need fixing before release to Luna integration stack.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2375) Combo Box issues with Eclipse Luna
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2375?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2375.
----------------------------------
> Combo Box issues with Eclipse Luna
> ----------------------------------
>
> Key: TEIIDDES-2375
> URL: https://issues.jboss.org/browse/TEIIDDES-2375
> Project: Teiid Designer
> Issue Type: Bug
> Components: Eclipse Integration
> Affects Versions: 9.0
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.0, 8.6.1
>
>
> Combo box drop-downs show incomplete and overlapping lists.
> The attached JDBC importer's Connection Profile drop-down should show 20 items, but show multiple item text in same item spots.
> WidgetUtil.setComboItems() seems to be adding the proper String items to the combo widget.
> I did check other UI components, in luna and most seem to use Combo.setItems() rather than add them 1 at a time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2629) Updating data source import resets translator to jdbc-simple for Netezza
by Bas Piepers (JIRA)
Bas Piepers created TEIIDDES-2629:
-------------------------------------
Summary: Updating data source import resets translator to jdbc-simple for Netezza
Key: TEIIDDES-2629
URL: https://issues.jboss.org/browse/TEIIDDES-2629
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.3.4
Reporter: Bas Piepers
Priority: Minor
Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png
If you update an existing source model while the translator is set to "Netezza", Teiid Designer resets the translator to "jdbc-simple". You have to manually set the translator back to "Netezza".
See "Steps to reproduce" to get a better view of what happens.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2628) Issue when using JDBC importer to import from a Teiid VDB and only 1 model (schema) is created
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2628:
-------------------------------------
Summary: Issue when using JDBC importer to import from a Teiid VDB and only 1 model (schema) is created
Key: TEIIDDES-2628
URL: https://issues.jboss.org/browse/TEIIDDES-2628
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Reporter: Van Halbert
When using the JDBC Importer to import from a VDB, only one model is being created.
This scenario is: The VDB has 3 models (schemas) and when going thru the JDBC importer, it presents the 3 schemas to be selected. Upon selecting the 3, only 1 model is created. Expected 3 Models.
In discussing with Barry, the importer doesn't account for creating mulitple models with 1 pass thru the JDBC importer.
At a minimum, we should indicate this issue on the schema selection panel to say that you will need to make several passes (selecting only 1 schema) in order to get the 3 different models created.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2626) Additional makedep/makeind syntax
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2626?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2626:
------------------------------------------
I should add that the query OPTION clause and post symbol hint syntax may require modeshape parsing changes as well. I'm assuming that the comment form of the hint won't need any additional support.
> Additional makedep/makeind syntax
> ---------------------------------
>
> Key: TEIIDDES-2626
> URL: https://issues.jboss.org/browse/TEIIDDES-2626
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Transformations
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> For TEIID-3515 the following changes were made:
> MAKEIND was added as a reserved word (for consistency with the usage of the MAKEDEP reserved word)
> A from clause can now have a MAKEIND post option supporting the same syntax as MAKEDEP:
> ... from foo MAKEDEP ...
> ... from foo MAKEIND ...
> And the same is true for the option clause:
> ... OPTION MAKEDEP x, ...
> ... OPTION MAKEIND x, ...
> There is also now the option to not push down the entire join:
> MAKEDEP(NO JOIN)
> MAKENOTDEP(NO JOIN)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months