[JBoss JIRA] (TEIID-3509) Consolidate internal and external materialization management
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3509?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-3509:
------------------------------------
> 1) The execution looks correct, what is the error you are seeing?
The Procedure definition
{code}
CREATE FOREIGN PROCEDURE refreshMatViewRow(OUT RowsUpdated integer NOT NULL RESULT, IN ViewName string NOT NULL, IN Key object NOT NULL, VARIADIC KeyOther object) OPTIONS (UPDATECOUNT 1)
{code}
have define a VARIADIC, but it not allow multiple pk added, for example, if execute
{code}
"EXEC SYSADMIN.refreshMatViewRow('TestInterMat.SAMPLEMATVIEW', '100', '101', '102')";
{code}
An exception will throw:
{code}
Caused by: org.teiid.api.exception.query.QueryProcessingException: TEIID30231 Materialized view TestInterMat.SAMPLEMATVIEW cannot have a row refreshed because the number of primary key elements 1 does not match the number of key arguments 3.
at org.teiid.query.tempdata.TempTableDataManager.updateMatviewRows(TempTableDataManager.java:437)
at org.teiid.query.tempdata.TempTableDataManager.handleSystemProcedures(TempTableDataManager.java:412)
at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:195)
{code}
This should be a bug, either update the Procedure definition remove VARIADIC, or update runtime make sure multiple rows can be updated, I prefer the later one.
I got confused from the document, according to
https://teiid.gitbooks.io/documents/content/reference/sysadmin_schema.html
SYSADMIN.refreshMatViewRow is for refreshing one row, and SYSADMIN.refreshMatViewRows is for refreshing multiple rows, but this is wrong, if look more about the procedures definition
{code}
CREATE FOREIGN PROCEDURE refreshMatViewRow(OUT RowsUpdated integer NOT NULL RESULT, IN ViewName string NOT NULL, IN Key object NOT NULL, VARIADIC KeyOther object)
CREATE FOREIGN PROCEDURE refreshMatViewRows(OUT RowsUpdated integer NOT NULL RESULT, IN ViewName string NOT NULL, VARIADIC Key object[] NOT NULL)
{code}
* refreshMatViewRow is for updating one or more rows and PK only have one column
* refreshMatViewRows is for updating one or more rows and PK have more columns, a group og PK columns form a object array.
> Consolidate internal and external materialization management
> ------------------------------------------------------------
>
> Key: TEIID-3509
> URL: https://issues.jboss.org/browse/TEIID-3509
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.7
> Reporter: Ramesh Reddy
> Assignee: Kylin Soong
> Fix For: 9.0
>
>
> - Currently there separate SYSADMIN procedures for internal and external materialization to refresh them, we need to provide single set
> - The management of the (usage of status table) is not fully utilized by the internal materialization this needs to addressed such that both external and internal use this table to keep track of load status
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-4205) send results proactively under a cursor as it looks like the ODBC client requires a transaction.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4205?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-4205 at 5/17/16 5:21 PM:
--------------------------------------------------------------
I think if we can positively target the BEGIN with CURSOR we can strip them, otherwise I think we should honor it. I do NOT think switch is required during in the CURSOR walking.
was (Author: rareddy):
I think if we can positively target the BEGIN with CURSOR we can strip them, otherwise I think we should honor it. I think switch is required during in the CURSOR walking.
> send results proactively under a cursor as it looks like the ODBC client requires a transaction.
> ------------------------------------------------------------------------------------------------
>
> Key: TEIID-4205
> URL: https://issues.jboss.org/browse/TEIID-4205
> Project: Teiid
> Issue Type: Feature Request
> Components: ODBC, Server
> Affects Versions: 8.7.5.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Currently when querying large resultsets with ODBC the results are not sent as soon as the batch is logically available (like we do for JDBC)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-4202) Support Lateral join and procedure pushdown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4202?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4202.
-----------------------------------
Resolution: Done
Added the initial support targeting both procedure and lateral join pushdown to Teiid sources, and lateral join pushdown to newer postgresql. There are still more targets that can added for pushdown, but that can be done with additional issues.
> Support Lateral join and procedure pushdown
> -------------------------------------------
>
> Key: TEIID-4202
> URL: https://issues.jboss.org/browse/TEIID-4202
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> Lateral joins of the form:
> select ... from x inner join lateral (... x.col ...) as y on ...
> Have been supported for some time, but not the ability to push them to source.
> A highly related scenario is to be able to push procedures used directly or in lateral joins with the rest of their plan:
> select ... from x inner join lateral (call proc(.. x.col ...)) as y on ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-4203) QueryResolverException thow in resolving loadMatView
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4203?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4203.
-----------------------------------
Resolution: Done
Marking as resolved with Kylin's commit.
> QueryResolverException thow in resolving loadMatView
> -----------------------------------------------------
>
> Key: TEIID-4203
> URL: https://issues.jboss.org/browse/TEIID-4203
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 9.0
>
> Attachments: server.log
>
>
> The Change in 9.0.0.Beta2-SNAPSHOT cause loadMatView resolving failed
> {code}
> Caused by: org.teiid.api.exception.query.QueryResolverException: TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: VDBVersion = DVARS.vdbVersion
> at org.teiid.query.resolver.util.ResolverVisitor.resolveCompareCriteria(ResolverVisitor.java:999)
> at org.teiid.query.resolver.util.ResolverVisitor.visit(ResolverVisitor.java:249)
> at org.teiid.query.sql.lang.CompareCriteria.acceptVisitor(CompareCriteria.java:130)
> at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:54)
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:61)
> at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.postVisitVisitor(SimpleQueryResolver.java:223)
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:135)
> at org.teiid.query.sql.lang.CompareCriteria.acceptVisitor(CompareCriteria.java:130)
> at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63)
> at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:76)
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:139)
> at org.teiid.query.sql.lang.CompoundCriteria.acceptVisitor(CompoundCriteria.java:235)
> at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63)
> at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:238)
> at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:70)
> at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:273)
> at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:127)
> at org.teiid.query.processor.proc.ExecDynamicSqlInstruction.process(ExecDynamicSqlInstruction.java:171)
> ... 22 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-3999) more aspects of materialization metadata should be validated
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3999?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3999:
----------------------------------
Fix Version/s: 9.0
(was: 9.1)
Given TEIID-4203 it will be friendlier to users to have the validations done upfront. Let's see what we can do in 9.0 first.
> more aspects of materialization metadata should be validated
> ------------------------------------------------------------
>
> Key: TEIID-3999
> URL: https://issues.jboss.org/browse/TEIID-3999
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Kylin Soong
> Priority: Minor
> Fix For: 9.0
>
>
> * During metadata load we should check if the status table and the materialization scripts are valid, so there is at least a log of the issue rather than waiting for the exception to occur once the vdb is active.
> * According to TEIID-4203, add an initial validation that validate the status table definition matches the expectation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-4112) ORA-32039: recursive WITH clause must have column alias list
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4112?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4112:
------------------------------------------------
Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1322935|https://bugzilla.redhat.com/show_bug.cgi?id=1322935] from MODIFIED to ON_QA
> ORA-32039: recursive WITH clause must have column alias list
> ------------------------------------------------------------
>
> Key: TEIID-4112
> URL: https://issues.jboss.org/browse/TEIID-4112
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector, Query Engine
> Affects Versions: 8.7.2.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.7.6.6_2
>
>
> If running a WITH table AS(...) query to Oracle and the query schema name is the same as the subquery name i.e. EWI. you receive the Oracle error:
> ORA-32039: recursive WITH clause must have column alias list
> If you modify the query to
> WITH EWI1 AS ....
> then it works.
> f.ex:
> breaking: WITH tbl AS (
> where tbl = a common table name in the current schema and the common table definition as (...) references a view in that schema. Oracle will complain with this erroneous error.
> work-around: WITH tbl_1 AS(
> where tbl_1 does not exist as a current schema/table name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-3708) Undeployable dynamic VDB at start-up time removes all previously deployed artifacts
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3708?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3708.
-----------------------------------
Fix Version/s: 8.13
Resolution: Done
> Undeployable dynamic VDB at start-up time removes all previously deployed artifacts
> -----------------------------------------------------------------------------------
>
> Key: TEIID-3708
> URL: https://issues.jboss.org/browse/TEIID-3708
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 8.12.5, 8.13
>
>
> If standalone/deployments directory contains undeployable dynamic VDB at start-up (reload) time all deployments previously deployed via mangement CLI are undeployed.
> Log:
> {code:text}
> 13:42:48,993 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) starting
> ...
> ...
> ...
> 13:42:53,258 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "oo-vdb.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1"}}
> 13:42:53,300 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015859: Deployed "QT_MySql55_Push.vdb" (runtime-name : "QT_MySql55_Push.vdb")
> 13:42:53,301 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "oo-vdb.xml" (runtime-name : "oo-vdb.xml")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-cmis.war" (runtime-name : "modeshape-cmis.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "integration-platform-console.war" (runtime-name : "integration-platform-console.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-webdav.war" (runtime-name : "modeshape-webdav.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-rest.war" (runtime-name : "modeshape-rest.war")
> 13:42:53,303 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 13:42:53,331 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) started (with errors) in 4336ms - Started 619 of 664 services (1 services failed or missing dependencies, 100 services are lazy, passive or on-demand)
> 13:42:53,529 INFO [org.jboss.web] (ServerService Thread Pool -- 26) JBAS018224: Unregister web context: /modeshape-rest
> 13:42:53,538 INFO [org.jboss.web] (ServerService Thread Pool -- 19) JBAS018224: Unregister web context: /modeshape-webdav
> 13:42:53,540 INFO [org.jboss.web] (ServerService Thread Pool -- 18) JBAS018224: Unregister web context: /modeshape-cmis
> 13:42:53,544 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "QT_MySql55_Push.1[Source{Source=Source, mysql5, MySQL55_PushDS}, XQTRecursiveSchema{}, BQT2{}, SP{SP=SP, mysql5, MySQL55_PushDS}, VirtProcs{}, XQTSchema{}, XQTRecursiveDoc{}, XQT{}, BQT1{}, VQT{}, XQTNestedDoc{}, XQTDoc{}]" undeployed.
> 13:42:53,569 INFO [javax.enterprise.resource.webservices.jaxws.servlet.http] (ServerService Thread Pool -- 18) WSSERVLET15: JAX-WS servlet destroyed
> 13:42:53,572 INFO [javax.enterprise.resource.webservices.jaxws.server.http] (ServerService Thread Pool -- 18) WSSERVLET13: JAX-WS context listener destroyed
> 13:42:53,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment modeshape-rest.war (runtime-name: modeshape-rest.war) in 50ms
> 13:42:53,580 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 43ms
> 13:42:53,582 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-webdav.war (runtime-name: modeshape-webdav.war) in 45ms
> 13:42:53,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment QT_MySql55_Push.vdb (runtime-name: QT_MySql55_Push.vdb) in 46ms
> 13:42:53,607 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-cmis.war (runtime-name: modeshape-cmis.war) in 70ms
> 13:42:53,647 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "oo-vdb.xml" (runtime-name: "oo-vdb.xml")
> 13:42:53,648 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/45/9c1839c446e700d7f0b713f5f949b068fbeb24/content
> 13:42:53,648 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "QT_MySql55_Push.vdb" (runtime-name: "QT_MySql55_Push.vdb")
> 13:42:53,649 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/a3/b37a584c66a65d33bf194ffa9fc0e93c83b9ca/content
> 13:42:53,649 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-webdav.war" (runtime-name: "modeshape-webdav.war")
> 13:42:53,651 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/f2/00c83231bcb7a63276d49ac9e01bcbbde30424/content
> 13:42:53,651 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-cmis.war" (runtime-name: "modeshape-cmis.war")
> 13:42:53,652 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/2b/4d8dbcf74227d075e54215d1f330da494a4b22/content
> 13:42:53,657 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-rest.war" (runtime-name: "modeshape-rest.war")
> 13:42:53,658 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months