[JBoss JIRA] (TEIIDDES-1571) Designer SQL expressions that differ between runtime client versions must be correct to the default server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1571?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1571:
-----------------------------------
Assignee: Paul Richardson
> Designer SQL expressions that differ between runtime client versions must be correct to the default server
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1571
> URL: https://issues.jboss.org/browse/TEIIDDES-1571
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> Designer provides text for Text, XML and Web Service SQL transformations. Historically, this has been updated according to the included runtime client. However, with the advent of multiple runtime clients, the text must be crafted according to the active/default teiid server / runtime client.
> For example, [1570|https://issues.jboss.org/browse/TEIIDDES-1570] details a fix required for the invokeHttp method's parameters in remote XML modelling. Adding a 4th parameter is correct for an 8.2 runtime client but is not correct for 7.7.
> Ideally, a new service should be created, eg. IProcedureService, obtainable from the runtime clients' QueryServices. This service will allow each runtime client to return their own version of the procedure text and all such procedures in the code should delegate to this service.
--
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 month
[JBoss JIRA] (TEIIDDES-1348) Investigate Adding Additional VDB Properties
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1348?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1348:
----------------------------------------
UseConnectorMetadata - currently only used for dynamic VDBs. This has to do more with either to load metadata from sources when VDB is deployed and make use of it in subsequent server restarts or not
> Investigate Adding Additional VDB Properties
> --------------------------------------------
>
> Key: TEIIDDES-1348
> URL: https://issues.jboss.org/browse/TEIIDDES-1348
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: VDB & Execution
> Affects Versions: 7.7
> Reporter: Ted Jones
> Assignee: Dan Florian
> Priority: Minor
> Fix For: 8.1
>
>
> We currently allow the user to set the query timeout on the VDB. We had a request from the field to see if there were other properties we could set at that level and add to the tab.
--
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 month
[JBoss JIRA] (TEIIDDES-987) Add ability to edit/generate Create Virtual Procedure SQL statements for RestEasy XML, File and Web Service Translator procedures
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-987?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-987:
----------------------------------
Fix Version/s: Future
(was: 8.1)
Assignee: (was: Mark Drilling)
This is a nice to have and will take quite a bit of work. Pushing to future
> Add ability to edit/generate Create Virtual Procedure SQL statements for RestEasy XML, File and Web Service Translator procedures
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-987
> URL: https://issues.jboss.org/browse/TEIIDDES-987
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors, Transformations
> Affects Versions: 7.4
> Reporter: Barry LaFond
> Fix For: Future
>
>
> Designer includes "Generate xxxx procedures" options in the New Model Wizard.
> Also have a RestEasy use-case that requires getXXXX virtual procedures that contain SQL like:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT XMLELEMENT(NAME parts, XMLAGG(XMLELEMENT(NAME part, XMLFOREST(VirtualParts_Supplier.PARTS.PART_ID, VirtualParts_Supplier.PARTS.PART_NAME, VirtualParts_Supplier.PARTS.PART_COLOR, VirtualParts_Supplier.PARTS.PART_WEIGHT)))) AS result FROM VirtualParts_Supplier.PARTS WHERE VirtualParts_Supplier.getParts.partId_in = VirtualParts_Supplier.PARTS.PART_ID;
> END
> Would be nice to have a framework where "wizards" can be accessed to create/edit the content of this SQL if the basic structure is a Set Query (SELECT * FROM XXX)for these specific use-cases.
--
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 month
[JBoss JIRA] (TEIIDDES-1164) CLONE - Index metadata should not treat cardinality 0 as unknown
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1164?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1164.
------------------------------------
Assignee: Barry LaFond (was: Paul Richardson)
Resolution: Done
Changed default cardinality to -1
Changed lower limit to -1
Upped the current index version to 10
> CLONE - Index metadata should not treat cardinality 0 as unknown
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1164
> URL: https://issues.jboss.org/browse/TEIIDDES-1164
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Teiid Integration
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> The default cardinality is currently 0, which is treated as unknown, however it would be better if the default were something like -1 instead. This will require introducing a new index file version (so that older vdbs with a value of 0 can be understood as meaning unknown) and updating the teiid/designer metadata defaults for cardinality as -1.
--
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 month
[JBoss JIRA] (TEIIDDES-1571) Designer SQL expressions that differ between runtime client versions must be correct to the default server
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1571?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-1571:
--------------------------------------
Description:
Designer provides text for Text, XML and Web Service SQL transformations. Historically, this has been updated according to the included runtime client. However, with the advent of multiple runtime clients, the text must be crafted according to the active/default teiid server / runtime client.
For example, [1570|https://issues.jboss.org/browse/TEIIDDES-1570] details a fix required for the invokeHttp method's parameters in remote XML modelling. Adding a 4th parameter is correct for an 8.2 runtime client but is not correct for 7.7.
Ideally, a new service should be created, eg. IProcedureService, obtainable from the runtime clients' QueryServices. This service will allow each runtime client to return their own version of the procedure text and all such procedures in the code should delegate to this service.
was:
Designer provides text for Text, XML and Web Service SQL transformations. Historically, this has been updated according to the included runtime client. However, with the advent of multiple runtime clients, the text must be crafted according to the active/default teiid server / runtime client.
For example, #1570 details a fix required for the invokeHttp method's parameters in remote XML modelling. Adding a 4th parameter is correct for an 8.2 runtime client but is not correct for 7.7.
Ideally, a new service should be created, eg. IProcedureService, obtainable from the runtime clients' QueryServices. This service will allow each runtime client to return their own version of the procedure text and all such procedures in the code should delegate to this service.
> Designer SQL expressions that differ between runtime client versions must be correct to the default server
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1571
> URL: https://issues.jboss.org/browse/TEIIDDES-1571
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Fix For: 8.1
>
>
> Designer provides text for Text, XML and Web Service SQL transformations. Historically, this has been updated according to the included runtime client. However, with the advent of multiple runtime clients, the text must be crafted according to the active/default teiid server / runtime client.
> For example, [1570|https://issues.jboss.org/browse/TEIIDDES-1570] details a fix required for the invokeHttp method's parameters in remote XML modelling. Adding a 4th parameter is correct for an 8.2 runtime client but is not correct for 7.7.
> Ideally, a new service should be created, eg. IProcedureService, obtainable from the runtime clients' QueryServices. This service will allow each runtime client to return their own version of the procedure text and all such procedures in the code should delegate to this service.
--
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 month
[JBoss JIRA] (TEIIDDES-1571) Designer SQL expressions that differ between runtime client versions must be correct to the default server
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-1571:
-----------------------------------------
Summary: Designer SQL expressions that differ between runtime client versions must be correct to the default server
Key: TEIIDDES-1571
URL: https://issues.jboss.org/browse/TEIIDDES-1571
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 8.1
Reporter: Paul Richardson
Fix For: 8.1
Designer provides text for Text, XML and Web Service SQL transformations. Historically, this has been updated according to the included runtime client. However, with the advent of multiple runtime clients, the text must be crafted according to the active/default teiid server / runtime client.
For example, #1570 details a fix required for the invokeHttp method's parameters in remote XML modelling. Adding a 4th parameter is correct for an 8.2 runtime client but is not correct for 7.7.
Ideally, a new service should be created, eg. IProcedureService, obtainable from the runtime clients' QueryServices. This service will allow each runtime client to return their own version of the procedure text and all such procedures in the code should delegate to this service.
--
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 month