[JBoss JIRA] (TEIID-5657) VDB Migration Tool
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-5657.
--------------------------------
Fix Version/s: 12.1
Resolution: Done
The migration tool is now available in the teiid-openshift-examples. The README.md explains its usage.
> VDB Migration Tool
> ------------------
>
> Key: TEIID-5657
> URL: https://issues.jboss.org/browse/TEIID-5657
> Project: Teiid
> Issue Type: Feature Request
> Components: Documentation, Quick Starts, Tooling
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
> Fix For: 12.1
>
>
> A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs.
> We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided.
> There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts:
> 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught.
> 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example.
> 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc.
> To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project.
> This could possibly be included in the quickstarts as a means to facilitate its use.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5636) Planning error. Could not find symbol disiz__1.DischargeTime
by Mark Tawk (Jira)
[ https://issues.jboss.org/browse/TEIID-5636?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-5636:
----------------------------------
our version is 10.2.1 and we implemented the fix done
> Planning error. Could not find symbol disiz__1.DischargeTime
> ------------------------------------------------------------
>
> Key: TEIID-5636
> URL: https://issues.jboss.org/browse/TEIID-5636
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.3.4
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 12.1, 12.0.1, 11.2.3
>
> Attachments: Planning Error 21-02-2019.txt, planning_error.txt
>
>
> Hi,
> We're running into this exception. It happens when adding "LEFT OUTER JOIN izisprod.P_DischargeData". I unfortunitaly have no smaller example. We use this table all the time without any previous errors.
> 2019-01-31 15:32:36,438 ERROR [org.teiid.PROCESSOR] (Worker172_QueryProcessorQueue57002) JesgvCmnKfP5 TEIID30019 Unexpected exception for request JesgvCmnKfP5.187: org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol: disiz__1.DischargeTime
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:363)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:129)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:92)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:87)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:223)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:135)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:480)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:47)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5647) reserve information_schema for future use
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5647?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5647.
-----------------------------------
Resolution: Done
Added information_schema to the name exclusion list, but added the property org.teiid.allow_information_schema to allow it.
> reserve information_schema for future use
> -----------------------------------------
>
> Key: TEIID-5647
> URL: https://issues.jboss.org/browse/TEIID-5647
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> Most vendors support the information_schema. We should reserve that schema name for internal use only - although there will be potential conflicts with the specialized pg_catalog.information_schema introduced for odbc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5657) VDB Migration Tool
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5657:
------------------------------------
With latest PR, changed it so the VDB Migration Utility is executable from the root directory. Also, updated the README.md.
> VDB Migration Tool
> ------------------
>
> Key: TEIID-5657
> URL: https://issues.jboss.org/browse/TEIID-5657
> Project: Teiid
> Issue Type: Feature Request
> Components: Documentation, Quick Starts, Tooling
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
>
> A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs.
> We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided.
> There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts:
> 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught.
> 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example.
> 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc.
> To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project.
> This could possibly be included in the quickstarts as a means to facilitate its use.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5657) VDB Migration Tool
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-5657:
-------------------------------
Git Pull Request: https://github.com/teiid/teiid-openshift-examples/pull/12 (was: https://github.com/teiid/teiid-openshift-examples/pull/10)
> VDB Migration Tool
> ------------------
>
> Key: TEIID-5657
> URL: https://issues.jboss.org/browse/TEIID-5657
> Project: Teiid
> Issue Type: Feature Request
> Components: Documentation, Quick Starts, Tooling
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
>
> A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs.
> We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided.
> There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts:
> 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught.
> 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example.
> 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc.
> To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project.
> This could possibly be included in the quickstarts as a means to facilitate its use.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5636) Planning error. Could not find symbol disiz__1.DischargeTime
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5636?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5636:
---------------------------------------
> But we are still reproducing the planning error with another query.
I can't reproduce that on master. What version did you reproduce this against?
> Planning error. Could not find symbol disiz__1.DischargeTime
> ------------------------------------------------------------
>
> Key: TEIID-5636
> URL: https://issues.jboss.org/browse/TEIID-5636
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.3.4
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 12.1, 12.0.1, 11.2.3
>
> Attachments: Planning Error 21-02-2019.txt, planning_error.txt
>
>
> Hi,
> We're running into this exception. It happens when adding "LEFT OUTER JOIN izisprod.P_DischargeData". I unfortunitaly have no smaller example. We use this table all the time without any previous errors.
> 2019-01-31 15:32:36,438 ERROR [org.teiid.PROCESSOR] (Worker172_QueryProcessorQueue57002) JesgvCmnKfP5 TEIID30019 Unexpected exception for request JesgvCmnKfP5.187: org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol: disiz__1.DischargeTime
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:363)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:129)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:92)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:87)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:223)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:135)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:480)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:47)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month