[JBoss JIRA] (TEIIDDES-472) Support multi-source bindings
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ]
Barry LaFond resolved TEIIDDES-472.
-----------------------------------
Resolution: Done
Done
> Support multi-source bindings
> -----------------------------
>
> Key: TEIIDDES-472
> URL: https://issues.jboss.org/browse/TEIIDDES-472
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 6.3
> Reporter: John Verhaeg
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation.
> The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names.
--
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
13 years
[JBoss JIRA] (TEIIDDES-1620) Add Multi-source bindings editing feature to VDB Editor
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1620?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1620.
------------------------------------
Release Notes Docs Status: Not Yet Documented
Release Notes Text:
Teiid VDB's support multi-source bindings for each source (PHYSICAL) model.
The VDB editor was modified to allow users to add/delete/edit Source objects comprised of a name, connection-jndi-name and translator-name.
User selects a model in the Model table on the left
Model details are displayed in the Model Details tab on the right
On the Source Bindings Definition tab on the right...
Check the "Multi-source" option to allow adding multiple source definitions
Check the "Add Column" box to "make the multi-source column present in the system metadata"
Enter a "Column Alias" value if you wish to override the default name : SOURCE_NAME
Note that multi-source definition is not yet a feature outside of the VDB Editor
Resolution: Done
> Add Multi-source bindings editing feature to VDB Editor
> -------------------------------------------------------
>
> Key: TEIIDDES-1620
> URL: https://issues.jboss.org/browse/TEIIDDES-1620
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Editors, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.1
>
> Attachments: VDB Editor - Multi-Source-Bindings.bmml, vdb-editor-model-selected.png, vdb-editor-source-binding-tab.png
>
>
> Current VDB Editor is designed to manage a single source definition (name, jndi-name and translator-name) for each source model.
> The UI/Editor needs to allow for defining multiple "sources" for a each source model.
--
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
13 years
[JBoss JIRA] (TEIIDDES-1623) validation problems with trim and concat used together.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1623?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1623:
-----------------------------------
Fix Version/s: (was: 7.7.3)
> validation problems with trim and concat used together.
> -------------------------------------------------------
>
> Key: TEIIDDES-1623
> URL: https://issues.jboss.org/browse/TEIIDDES-1623
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 7.7
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: Trimtest.zip
>
>
> Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip).
> On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error.
> [1]
> SELECT
> ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
> [2]
> SELECT
> ((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
--
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
13 years
[JBoss JIRA] (TEIIDDES-1623) validation problems with trim and concat used together.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1623?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1623.
------------------------------------
Resolution: Done
Done.
Cloned to TEIIDDES-1632 to apply to 7.7.x branch
> validation problems with trim and concat used together.
> -------------------------------------------------------
>
> Key: TEIIDDES-1623
> URL: https://issues.jboss.org/browse/TEIIDDES-1623
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 7.7
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: Trimtest.zip
>
>
> Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip).
> On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error.
> [1]
> SELECT
> ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
> [2]
> SELECT
> ((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
--
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
13 years
[JBoss JIRA] (TEIIDDES-1632) validation problems with trim and concat used together - 7.7.x
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1632?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1632:
-----------------------------------
Fix Version/s: (was: 8.1)
> validation problems with trim and concat used together - 7.7.x
> --------------------------------------------------------------
>
> Key: TEIIDDES-1632
> URL: https://issues.jboss.org/browse/TEIIDDES-1632
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 7.7
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 7.7.3
>
> Attachments: Trimtest.zip
>
>
> Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip).
> On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error.
> [1]
> SELECT
> ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
> [2]
> SELECT
> ((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
--
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
13 years
[JBoss JIRA] (TEIIDDES-1632) validation problems with trim and concat used together - 7.7.x
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1632?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1632:
-----------------------------------
Assignee: Johnathon Lee (was: Barry LaFond)
> validation problems with trim and concat used together - 7.7.x
> --------------------------------------------------------------
>
> Key: TEIIDDES-1632
> URL: https://issues.jboss.org/browse/TEIIDDES-1632
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 7.7
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
> Fix For: 7.7.3
>
> Attachments: Trimtest.zip
>
>
> Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip).
> On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error.
> [1]
> SELECT
> ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
> [2]
> SELECT
> ((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
--
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
13 years
[JBoss JIRA] (TEIIDDES-1632) validation problems with trim and concat used together - 7.7.x
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1632:
--------------------------------------
Summary: validation problems with trim and concat used together - 7.7.x
Key: TEIIDDES-1632
URL: https://issues.jboss.org/browse/TEIIDDES-1632
Project: Teiid Designer
Issue Type: Bug
Components: Validation
Affects Versions: 7.7
Reporter: Johnathon Lee
Assignee: Barry LaFond
Fix For: 7.7.3, 8.1
Attachments: Trimtest.zip
Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip).
On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error.
[1]
SELECT
ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME
FROM
CCH.MEMMAS AS Memb
[2]
SELECT
((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME
FROM
CCH.MEMMAS AS Memb
--
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
13 years
[JBoss JIRA] (TEIIDDES-1616) Add Header Support to Generated REST WAR
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1616?page=com.atlassian.jira.plu... ]
Ted Jones commented on TEIIDDES-1616:
-------------------------------------
Added support for header parameters. The parameter names can be added to the REST:Headers extended property using a semi-colon delimiter. Ex. header1;header2;header3
When header parameters are used, the underlying procedure should expect those values first. Other parameters from URI path, query params, or input documents will be passed in after the header parameters (in that order).
I cannot test end-to-end in 8.1 due to TEIIDDES-1598.
> Add Header Support to Generated REST WAR
> ----------------------------------------
>
> Key: TEIIDDES-1616
> URL: https://issues.jboss.org/browse/TEIIDDES-1616
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Web Services Support
> Affects Versions: 7.8
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 7.7.3, 8.1
>
>
> Need to add support for using headers in the generated REST WAR. The headers will be used as parameters to the target procedure for an operation.
--
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
13 years