[JBoss JIRA] (TEIIDDES-1255) Execution plan without executing the query
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1255?page=com.atlassian.jira.plu... ]
Mark Drilling reopened TEIIDDES-1255:
-------------------------------------
Apparently the previous fix did not fully resolve the issue. I am re-opening and will attach a code patch for TeiidExplainSQLActionDelegate
> Execution plan without executing the query
> ------------------------------------------
>
> Key: TEIIDDES-1255
> URL: https://issues.jboss.org/browse/TEIIDDES-1255
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Transformations
> Affects Versions: 7.6
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 7.7, 7.4.4
>
> Attachments: patch-TeiidAdHocScriptRunnable.txt
>
>
> DTP execution panel, when user right clicks on the query and ask for execution plan then no execution plan is returned. Only if the user executes the query then the execution plan, then user requests for plan it is returned. A query plan can be retrived by excuting
> SET NOEXEC ON
> <query>
> SET NOEXEC OFF
> Also, when I tried to manually do the above steps in the DTP SQL Scrap Book, then it seemed like it is using a separate connection for each of the abouve commands. so to check that we did
> SET NOEXEC OFF
> SHOW NOEXEC -> result was -> NULL (should have been ON)
--
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
[JBoss JIRA] (TEIIDDES-1523) Source Function And Procedure Modeling And Terminology Is Confusing
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1523?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1523:
-----------------------------------
Attachment: new-procedure-wizard-properties.png
> Source Function And Procedure Modeling And Terminology Is Confusing
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1523
> URL: https://issues.jboss.org/browse/TEIIDDES-1523
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.8
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: new-procedure-wizard-parameters.png, new-procedure-wizard-properties.png
>
>
> It is very confusing that creating a "Source Function" and creating a "Procedure" both end up with model objects of type "Procedure." The source function wizard sets a procedure's "function" property to "true" and requires the user to create one or more inputs and one output. However, after finishing the wizard, the user is free to delete the inputs, delete the output, and set the "function" property to "false" if they so choose (in essence making it just a procedure). Alternatively, the user could start by creating a procedure, then set the "function" property to "true," add one or more inputs, add an output, and end up creating a "source function." Maybe the source function wizard could be adapted and used when creating procedures.
--
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
[JBoss JIRA] (TEIIDDES-1523) Source Function And Procedure Modeling And Terminology Is Confusing
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1523?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1523:
-----------------------------------
Attachment: new-procedure-wizard-parameters.png
> Source Function And Procedure Modeling And Terminology Is Confusing
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1523
> URL: https://issues.jboss.org/browse/TEIIDDES-1523
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.8
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: new-procedure-wizard-parameters.png, new-procedure-wizard-properties.png
>
>
> It is very confusing that creating a "Source Function" and creating a "Procedure" both end up with model objects of type "Procedure." The source function wizard sets a procedure's "function" property to "true" and requires the user to create one or more inputs and one output. However, after finishing the wizard, the user is free to delete the inputs, delete the output, and set the "function" property to "false" if they so choose (in essence making it just a procedure). Alternatively, the user could start by creating a procedure, then set the "function" property to "true," add one or more inputs, add an output, and end up creating a "source function." Maybe the source function wizard could be adapted and used when creating procedures.
--
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
[JBoss JIRA] (TEIIDDES-1555) Errors with Web Service model operation validation
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1555?page=com.atlassian.jira.plu... ]
Paul Richardson reassigned TEIIDDES-1555:
-----------------------------------------
Assignee: Ted Jones (was: Paul Richardson)
Can you take a look at the webservice validation problems that pop up on creation of a webservice please?
> 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
>
>
> 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
12 years
[JBoss JIRA] (TEIIDDES-1555) Errors with Web Service model operation validation
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1555?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1555:
-------------------------------------------
Webservices still produce validation errors, eg.
"The SELECT transformation is valid, but NOT fully reconciled: The number of transformation output symbols is zero."
for each generated Operation SQL.
Ted can you have a look?
> 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: Paul Richardson
> Fix For: 8.1
>
>
> 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
12 years
[JBoss JIRA] (TEIIDDES-1554) Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1554?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-1554:
----------------------------------
Fix Version/s: 8.1
> Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1554
> URL: https://issues.jboss.org/browse/TEIIDDES-1554
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations, Validation
> Affects Versions: 8.0
> Environment: jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar
> Designer 8 final release
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.1
>
> Attachments: portfolio.zip
>
>
> Taking a project set built in the latest JDBS 5 / Designer 7.x and trying to validate it in Designer 8.
> The MartketDataView.StockPrices view has this error:
> Found problems validating transformation defining MarketDataView/StockPrices, re-validate in the transformation editor.
> Unable to to get the error to go away after revalidating. Also tried the quick fix with no luck. Also tried typing in spaces to trigger revalidation, no luck.
> No error messages in the .log. Attached the project set.
--
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
[JBoss JIRA] (TEIIDDES-812) DDL Export XSLT files need to be upgraded/improved
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-812?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-812:
----------------------------------
Fix Version/s: Future
(was: 8.1)
Assignee: (was: Barry LaFond)
> DDL Export XSLT files need to be upgraded/improved
> --------------------------------------------------
>
> Key: TEIIDDES-812
> URL: https://issues.jboss.org/browse/TEIIDDES-812
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.1.1, 7.2, 7.3
> Reporter: Barry LaFond
> Priority: Critical
> Fix For: Future
>
>
> After working import issue TEIIDDES-215, it's become apparent that our XSLT's for various DB's need to be revisited.
> For instance, there is no logic in PostgreSQL version to check for integer types that have AUTOINCREMENT == TRUE. These should be exported as SERIAL datatypes. Same for BIGSERIAL.
> There is other missing logic.
> We need to:
> 1) Create a doc or series of docs describing what datatype conversions should be done on IMPORT JDBC and EXPORT DDL
> 2) Create sub-tasks for implementing these docs for all DB's
> 3) Possibly create extension point(s) to handle "new" DB types more effeciently
--
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