[JBoss JIRA] (TEIID-3637) Query Plan/Execution Plan Enhancements
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-3637?page=com.atlassian.jira.plugin... ]
Jorge Herrera commented on TEIID-3637:
--------------------------------------
This should be presented in gui form for a better user experience as not many ppl would have access to the actual logs on the server. In addition to the gui any sql client should also display more detailed information doing something like "explain salect a from b", so that sql developers can debug their code.
> Query Plan/Execution Plan Enhancements
> --------------------------------------
>
> Key: TEIID-3637
> URL: https://issues.jboss.org/browse/TEIID-3637
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Priority: Critical
>
> Query Plan / Execution plan, for any particular query is lacking more explicit information about what the query engine is doing for each query. Would like to know if its JDV doing the processing vs doing push down optimization, and what is the path it takes if its internal to JDV, and also the costs associated with every step.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3638) Analytical Functions Push-down Optimization
by Jorge Herrera (JIRA)
Jorge Herrera created TEIID-3638:
------------------------------------
Summary: Analytical Functions Push-down Optimization
Key: TEIID-3638
URL: https://issues.jboss.org/browse/TEIID-3638
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.7.1
Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
JBoss Data Virtualization 6.1.0.ER4
Reporter: Jorge Herrera
Assignee: Steven Hawkins
Enhancements and/or more documentation as to how Analytical functions work from JDV perspective.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3637) Query Plan/Execution Plan Enhancements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3637?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3637:
---------------------------------------
What you are more interested in is the query debug log. It shows each planning step, has high level statements about pushdown decisions, shows more about costing etc.
> Query Plan/Execution Plan Enhancements
> --------------------------------------
>
> Key: TEIID-3637
> URL: https://issues.jboss.org/browse/TEIID-3637
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Priority: Critical
>
> Query Plan / Execution plan, for any particular query is lacking more explicit information about what the query engine is doing for each query. Would like to know if its JDV doing the processing vs doing push down optimization, and what is the path it takes if its internal to JDV, and also the costs associated with every step.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3621) HBase translator - UPDATE statement requires primary key
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3621?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3621.
-----------------------------------
Fix Version/s: 8.12
Resolution: Done
The net change was simply to remove the assertionerror. The doc change highlights that a pk is needed for insert/update.
> HBase translator - UPDATE statement requires primary key
> --------------------------------------------------------
>
> Key: TEIID-3621
> URL: https://issues.jboss.org/browse/TEIID-3621
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Environment: Hbase: 1.1.1
> Phoenix: 4.5.0-HBase-1.1
> Reporter: Juraj Duráni
> Assignee: Kylin Soong
> Fix For: 8.12
>
>
> The HBase translator requires table to have a primary key defined. Is the PK really needed? If the table has no PK defined, then all columns are PK. E.g. query *UPDATE hbase.SmallA SET StringNum = '555' WHERE hbase.SmallA.StringNum IS NULL* is translated as *UPSERT INTO smalla (stringnum, intkey) SELECT '555', smalla.intkey FROM smalla WHERE smalla.stringnum IS NULL* (intkey is PK). Teiid can simply add all columns (except those defined in 'SET').
> Yes, I know that HBase requires the PK to be defined, but what happen if a user decide to change PK in VDB [1]? It could be a problem whether PK is in VDB defined or not.
> I suggest to add a hbase-translator-specific execution property which define PK in the source table and remove AssertionError [2].
> [1]
> *HBase table:* create table mytable(id integer primary key, nickname varchar(1))
> *Teiid table:* create table mytable(id integer, username varchar(1) primary key)
> Both, id and username, are valid PK (artificial/natural).
> [2]
> https://github.com/teiid/teiid/blob/master/connectors/translator-hbase/sr...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3637) Query Plan/Execution Plan Enhancements
by Jorge Herrera (JIRA)
Jorge Herrera created TEIID-3637:
------------------------------------
Summary: Query Plan/Execution Plan Enhancements
Key: TEIID-3637
URL: https://issues.jboss.org/browse/TEIID-3637
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.7.1
Reporter: Jorge Herrera
Assignee: Steven Hawkins
Priority: Critical
Query Plan / Execution plan, for any particular query is lacking more explicit information about what the query engine is doing for each query. Would like to know if its JDV doing the processing vs doing push down optimization, and what is the path it takes if its internal to JDV, and also the costs associated with every step.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3637) Query Plan/Execution Plan Enhancements
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-3637?page=com.atlassian.jira.plugin... ]
Jorge Herrera updated TEIID-3637:
---------------------------------
Environment:
RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
JBoss Data Virtualization 6.1.0.ER4
> Query Plan/Execution Plan Enhancements
> --------------------------------------
>
> Key: TEIID-3637
> URL: https://issues.jboss.org/browse/TEIID-3637
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Priority: Critical
>
> Query Plan / Execution plan, for any particular query is lacking more explicit information about what the query engine is doing for each query. Would like to know if its JDV doing the processing vs doing push down optimization, and what is the path it takes if its internal to JDV, and also the costs associated with every step.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3636) SalesForce.com aggregate function query issues
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-3636?page=com.atlassian.jira.plugin... ]
Jorge Herrera updated TEIID-3636:
---------------------------------
Affects Version/s: (was: 8.4.3)
Environment:
RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
JBoss Data Virtualization 6.1.0.ER4
> SalesForce.com aggregate function query issues
> ----------------------------------------------
>
> Key: TEIID-3636
> URL: https://issues.jboss.org/browse/TEIID-3636
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Priority: Blocker
>
> When executing a query against salesforce.com with an aggregate function (select max(), min(), sum() ) With a 'group by' clause with a 'SalesForce ID' returns with the following error:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 SalesForce_Sales: com.sforce.soap.partner.UnexpectedErrorFault: EXCEEDED_ID_LIMIT: Aggregate query does not support queryMore(), use LIMIT to restrict the results to a single batch [SQL State=50000, DB Errorcode=30504]
> Example Queries That FAIL:
> ----------
> SELECT accountid, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01'
> group by accountid;
> ----------
> SELECT aid, sum(amt) from (
> SELECT accountid aid, amount amt FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01'
> ) as tmp group by aid;
> Queries that DO Work:
> SELECT closedate, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by closedate
> ;
> SELECT isdeleted, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by isdeleted
> ;
> SELECT campaignid, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by campaignid
> ;
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3636) SalesForce.com aggregate function query issues
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-3636?page=com.atlassian.jira.plugin... ]
Jorge Herrera updated TEIID-3636:
---------------------------------
Affects Version/s: 8.7.1
> SalesForce.com aggregate function query issues
> ----------------------------------------------
>
> Key: TEIID-3636
> URL: https://issues.jboss.org/browse/TEIID-3636
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.4.3, 8.7.1
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Priority: Blocker
>
> When executing a query against salesforce.com with an aggregate function (select max(), min(), sum() ) With a 'group by' clause with a 'SalesForce ID' returns with the following error:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 SalesForce_Sales: com.sforce.soap.partner.UnexpectedErrorFault: EXCEEDED_ID_LIMIT: Aggregate query does not support queryMore(), use LIMIT to restrict the results to a single batch [SQL State=50000, DB Errorcode=30504]
> Example Queries That FAIL:
> ----------
> SELECT accountid, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01'
> group by accountid;
> ----------
> SELECT aid, sum(amt) from (
> SELECT accountid aid, amount amt FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01'
> ) as tmp group by aid;
> Queries that DO Work:
> SELECT closedate, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by closedate
> ;
> SELECT isdeleted, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by isdeleted
> ;
> SELECT campaignid, sum(amount)
> FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by campaignid
> ;
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3636) SalesForce.com aggregate function query issues
by Jorge Herrera (JIRA)
Jorge Herrera created TEIID-3636:
------------------------------------
Summary: SalesForce.com aggregate function query issues
Key: TEIID-3636
URL: https://issues.jboss.org/browse/TEIID-3636
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.4.3
Reporter: Jorge Herrera
Assignee: Steven Hawkins
Priority: Blocker
When executing a query against salesforce.com with an aggregate function (select max(), min(), sum() ) With a 'group by' clause with a 'SalesForce ID' returns with the following error:
TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 SalesForce_Sales: com.sforce.soap.partner.UnexpectedErrorFault: EXCEEDED_ID_LIMIT: Aggregate query does not support queryMore(), use LIMIT to restrict the results to a single batch [SQL State=50000, DB Errorcode=30504]
Example Queries That FAIL:
----------
SELECT accountid, sum(amount)
FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01'
group by accountid;
----------
SELECT aid, sum(amt) from (
SELECT accountid aid, amount amt FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01'
) as tmp group by aid;
Queries that DO Work:
SELECT closedate, sum(amount)
FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by closedate
;
SELECT isdeleted, sum(amount)
FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by isdeleted
;
SELECT campaignid, sum(amount)
FROM salesforce_sales.salesforce.opportunity where closedate > '2016-02-01' group by campaignid
;
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3589) MongoDB metadata import fails with NPE
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3589?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3589:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1246153|https://bugzilla.redhat.com/show_bug.cgi?id=1246153] from ASSIGNED to MODIFIED
> MongoDB metadata import fails with NPE
> --------------------------------------
>
> Key: TEIID-3589
> URL: https://issues.jboss.org/browse/TEIID-3589
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Labels: Beta1, ER5
> Fix For: 8.7.1.6_2, 8.12
>
>
> Deploying the following dynamic vdb fails with a NullPointerException when Teiid Connection importer is used:
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="mongo" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <property name="deployment-name" value="mongo-vdb.xml" />
> <model name="importVDBSrcModel">
> <source name="importVDBSrcModel" translator-name="mongodb" connection-jndi-name="java:/mongoDS" />
> </model>
> </vdb>
> {code}
> The resource adapter is defined as:
> {code}
> <resource-adapter id="mongoDS">
> <module slot="main" id="org.jboss.teiid.resource-adapter.mongodb"/>
> <transaction-support>NoTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.mongodb.MongoDBManagedConnectionFactory" jndi-name="java:/mongoDS" enabled="true" use-java-context="true" pool-name="mongoDS">
> <config-property name="Database">
> bqt
> </config-property>
> <config-property name="RemoteServerList">
> vmgdb01.mw.lab.eng.bos.redhat.com:27017
> </config-property>
> <config-property name="Username">
> dv
> </config-property>
> <config-property name="Password">
> dv
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> Server log:
> {code}
> 16:46:49,793 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "mongo-vdb.xml" (runtime-name: "mongo-vdb.xml")
> 16:46:49,809 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-5) VDB mongo-vdb.xml has been parsed.
> 16:46:49,835 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mongo.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 7/23/15 4:46 PM
> 16:46:49,869 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015859: Deployed "mongo-vdb.xml" (runtime-name : "mongo-vdb.xml")
> 16:46:50,626 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB mongo.1 model "importVDBSrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.addTable(MongoDBMetadataProcessor.java:92)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:57)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:38)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:935) [teiid-api-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months