[JBoss JIRA] (TEIIDDES-1636) Unable to create multiple source functions under one physical model in Teiid Designer
by Debbie Steigner (JIRA)
Debbie Steigner created TEIIDDES-1636:
-----------------------------------------
Summary: Unable to create multiple source functions under one physical model in Teiid Designer
Key: TEIIDDES-1636
URL: https://issues.jboss.org/browse/TEIIDDES-1636
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 7.7
Reporter: Debbie Steigner
Unable to create multiple source functions under one physical model in EDS Teiid Designer. I want to create multiple source functions say LTRIM, RTRIM, TRUNC etc under one physical model and noticed that once I create the first source function by using (right click on model name -> New Child -> Create Source Function) the "Create Source Function" menu item is no longer available to create others.
--
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-1555) Errors with Web Service model operation validation
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1555?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-1555.
---------------------------------
Resolution: Done
All generated procedures now resolve
> Errors with Web Service model operation validation
> --------------------------------------------------
>
> Key: TEIIDDES-1555
> URL: https://issues.jboss.org/browse/TEIIDDES-1555
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Transformations
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Ted Jones
> Fix For: 8.1
>
> Attachments: stateService.wsdl
>
>
> Created WS model from simple relational model.
> Validation results in the following T-editor message:
> _ERROR: TEIID30387 Could not load UDF "+", since its invocation class "org.teiid.query.function.FunctionMethods" could not be found._
> And a ClassCastException
> java.lang.ClassCastException: org.teiid82.sql.impl.xml.MappingNodeImpl cannot be cast to org.teiid.designer.xml.IMappingElement
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1116)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1196)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createDocumentNode(MappingDocumentFormatter.java:702)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:748)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMappingString(MappingDocumentFormatter.java:821)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformation(TreeMappingRootSqlAspect.java:285)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformationInfo(TreeMappingRootSqlAspect.java:333)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172)
> at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311)
> at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164)
> at org.teiid.designer.core.index.Index.add(Index.java:127)
> at org.teiid.designer.core.index.ModelIndexer.indexResource(ModelIndexer.java:240)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResource(ModelBuildUtil.java:308)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:333)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:324)
> at org.teiid.designer.core.builder.ModelBuildUtil.buildResources(ModelBuildUtil.java:123)
> at org.teiid.designer.core.builder.ModelBuilder$1.run(ModelBuilder.java:138)
--
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-1549) Web service (and possibly other) procedures fail validation
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1549?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1549.
------------------------------------
Resolution: Done
with fix to TEIIDDES-1614 ... imported attached project, revalidated the model and the errors were removed.
Marking as fixed
> Web service (and possibly other) procedures fail validation
> -----------------------------------------------------------
>
> Key: TEIIDDES-1549
> URL: https://issues.jboss.org/browse/TEIIDDES-1549
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: PartsBeforeLunch_MPS.zip
>
>
> Paul created the attached model project set and received an error complaining that the web service operation procedure did not project any symbols. More than likely the CreateProcedureCommand.getResultSetColumns needs to be consulted to see if the procedure returns a result set.
> There was a change in the Teiid 8.2 code that clarified the difference between the projected symbols and result set columns for a procedure and remove the notion of the user command.
> The projected columns are expected to match the containing call, which can project out/inout/return parameters, while the result set columns must match the metadata if specified. When no result set columns have been set, Teiid assumes will set the result set columns to the results of one of the returnable statements and validate that all other returnable statements must match that result.
--
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 resolved TEIIDDES-1616.
---------------------------------
Release Notes Text:
Added support for header parameters in the generated REST WAR. The parameter names can be added to the new 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).
Resolution: Done
Added HEADER support to 8.x branch
> 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
[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1614.
------------------------------------
Resolution: Done
Done
> Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1614
> URL: https://issues.jboss.org/browse/TEIIDDES-1614
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Validation
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: DynamicSQLMPS.zip
>
>
> Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT * FROM PARTS;
> END
> Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
> When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type
--
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-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1614:
----------------------------------------
* added a getResultSetColumns() method to ICommand in SPI plugin
* added getResultSetColumns() method to Command on 7.7.x branch to return getProjectedSymbols()
* added helper class, CommandHelper with one static method: getProjectedSymbols(command)
** method accumulates and returns list of getProjectedSymbols() + getResultSetColumns() (no duplicates)
** replaced all direct command.getProjectedSymbols() in Designer to use CommandHelper.getProjectedSymbols(command)
Resulting changes fixes this issue of discovering result set and columns during reconcileTargetAttributes() calls.
> Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1614
> URL: https://issues.jboss.org/browse/TEIIDDES-1614
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Validation
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: DynamicSQLMPS.zip
>
>
> Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT * FROM PARTS;
> END
> Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
> When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type
--
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