[JBoss JIRA] (TEIID-3715) MongoDB metadata import fails
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIID-3715:
-------------------------------------
Summary: MongoDB metadata import fails
Key: TEIID-3715
URL: https://issues.jboss.org/browse/TEIID-3715
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.7.1.6_2
Reporter: Andrej Šmigala
Assignee: Ramesh Reddy
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.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3715) MongoDB metadata import fails
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIID-3715?page=com.atlassian.jira.plugin... ]
Andrej Šmigala updated TEIID-3715:
----------------------------------
Fix Version/s: (was: 8.7.1.6_2)
(was: 8.12)
> MongoDB metadata import fails
> -----------------------------
>
> Key: TEIID-3715
> URL: https://issues.jboss.org/browse/TEIID-3715
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
>
> 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.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3715) MongoDB metadata import fails
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIID-3715?page=com.atlassian.jira.plugin... ]
Andrej Šmigala updated TEIID-3715:
----------------------------------
Labels: (was: Beta1 ER5)
> MongoDB metadata import fails
> -----------------------------
>
> Key: TEIID-3715
> URL: https://issues.jboss.org/browse/TEIID-3715
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
>
> 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.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3636) SalesForce.com aggregate function query issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3636?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3636:
---------------------------------------
Rather than working a newer api version specific solution, the simplest thing to do is to offer a translator property to disable group by push down support.
> SalesForce.com aggregate function query issues
> ----------------------------------------------
>
> Key: TEIID-3636
> URL: https://issues.jboss.org/browse/TEIID-3636
> Project: Teiid
> Issue Type: Quality Risk
> 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: Minor
> Fix For: 8.12
>
>
> 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.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2729:
---------------------------------------
> IMO, validation out weighs the convenience. Granted we can remove validation, then we need to do certain tasks in code, which seems counter intuitive.
I don't quite follow you. As long as the parsing correctly validates (which is already does to a certain extent - only expected child elements can be processed), then having the extra xsd validation is simply an extra step.
> May be can put choice block around property, duplicate it before and after like
Can you take a wack at the xsd approach? If it doesn't work, I'll just take a pass through the parsing logic and see how cumbersome it would be to have additional validation.
> Dynamic VDB xml requires sibling elements to be in a certain order
> ------------------------------------------------------------------
>
> Key: TEIID-2729
> URL: https://issues.jboss.org/browse/TEIID-2729
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> In my *-vdb.xml, I have a model defined per following snippet:
> <model name="myModel" type="PHYSICAL" visible="true">
> <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" />
> <property name="trimColumnNames" value="true" />
> </model>
> The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked.
> I don't think element ordering should matter in this case?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3707) Wrong Data returned when a procedure is executed in the SELECT clause
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3707?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3707:
---------------------------------------
With the 1.7 JDK I was able to reproduce this. It's a unit test issue corrected by https://github.com/teiid/teiid/commit/5df19a2c1cea6f23912b9c1262ada5dc752...
A mock logger was being left on for the test which was storing the invocations, which led to gc issues.
> Wrong Data returned when a procedure is executed in the SELECT clause
> ---------------------------------------------------------------------
>
> Key: TEIID-3707
> URL: https://issues.jboss.org/browse/TEIID-3707
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.6
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.12, 8.11.5, 8.7.5
>
> Attachments: highcpu-threads.png, out.1, out.2, out.3, sample_coords.sql, wrong_data.jpg
>
>
> I've found the following problem when executing a stored procedure in the SELECT clause. It calculates wrong data in a seemingly random fashion.
> This is a stored procedure which was created to determine whether a given coordinate lies within a specific rectangle. If this procedure is tested in a simple manner (SELECT .. FROM (EXEC ..)) the results are correctly retuned (0 = outside the rectangle and 1 otherwise).
> {code:sql}
> CREATE virtual procedure point_inside_store (
> pos_x float
> ,pos_y float
> ) RETURNS (
> "insideFence" integer
> ) AS
> BEGIN
> DECLARE integer insideFence = 0 ;
> DECLARE float lowerLimit = 0.0 ;
> DECLARE float upperLimit = 17.0 ;
> DECLARE float leftLimit = 0.0 ;
> DECLARE float rightLimit = 53.0 ;
> IF (
> pos_x >= leftLimit
> AND pos_x <= rightLimit
> AND pos_y >= lowerLimit
> AND pos_y <= upperLimit
> )
> BEGIN
> insideFence = 1 ;
> END
> SELECT
> insideFence ;
> END
> {code}
> If now the same procedure is included in a SELECT clause of a query:
> {code:sql}
> SELECT
> "citmp.KoordX"
> ,"citmp.KoordY"
> ,(
> SELECT
> "store.insideFence"
> FROM
> (
> EXEC procs.point_inside_store (
> CAST (
> "citmp.KoordX" AS float
> )
> ,CAST (
> "citmp.KoordY" AS float
> )
> )
> ) as "store"
> ) as "insideStore"
> ,(
> SELECT
> "firstsection.insideFence"
> FROM
> (
> EXEC procs.point_inside_store (
> CAST (
> "citmp.KoordX" AS float
> )
> ,CAST (
> "citmp.KoordY" AS float
> )
> )
> ) as "firstsection"
> ) as "insideFirstsection"
> FROM
> "test.sample_coords" as "citmp"
> ORDER BY
> insideStore ASC
> ,insideFirstsection DESC;;
> {code}
> it calculates different results. The same coordinates that yielded 0 before now yield 1.
> !wrong_data.jpg|thumbnail!
> Note that the main query has 2 columns executing the exact same procedure but there are result sets, that have different values in the last two columns. This should not be possible.
> In attachment you will find sample_coords table with a sample of coordinates.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3711) Teiid XML Plan not showing Aggregate function
by Sathish Kumaran Vairavelu (JIRA)
Sathish Kumaran Vairavelu created TEIID-3711:
------------------------------------------------
Summary: Teiid XML Plan not showing Aggregate function
Key: TEIID-3711
URL: https://issues.jboss.org/browse/TEIID-3711
Project: Teiid
Issue Type: Bug
Components: Embedded, Query Engine
Affects Versions: 8.11.4
Reporter: Sathish Kumaran Vairavelu
Assignee: Steven Hawkins
The SQL contains aggregation function but the aggregation function(count, sum, etc) is missing from Teiid Plan. The plan should provide which aggregate functions is being worked on.
Below is the SQL and the plan.
SQL:
select a.ACCOUNT_ID as ACCOUNT_ID, b.company_name as company_name, c.ssn as ssn, count(a.shares_count) as total_shares
from UbuntuMySQL.PORTFOLIO.HOLDINGS a, UbuntuMySQL.PORTFOLIO.PRODUCT b,HadoopSrcModel.default.account c
WHERE a.PRODUCT_ID = b.ID and a.ACCOUNT_ID = c.ACCOUNT_ID GROUP BY a.ACCOUNT_ID,b.company_name, c.ssn
XML Plan:
<?xml version="1.0" encoding="UTF-8" ?>
- <node name="ProjectNode">
- <property name="Relational Node ID">
<value>3</value>
</property>
- <property name="Output Columns">
<value>ACCOUNT_ID (integer)</value>
<value>company_name (string)</value>
<value>ssn (string)</value>
<value>total_shares (integer)</value>
</property>
- <property name="Cost Estimates">
<value>Estimated Node Cardinality: -1.0</value>
</property>
- <property name="Child 0">
- <node name="GroupingNode">
- <property name="Relational Node ID">
<value>4</value>
</property>
- <property name="Output Columns">
<value>gcol0 (integer)</value>
<value>gcol1 (string)</value>
<value>gcol2 (string)</value>
<value>agg0 (long)</value>
</property>
- <property name="Cost Estimates">
<value>Estimated Node Cardinality: -1.0</value>
</property>
- <property name="Child 0">
- <node name="JoinNode">
- <property name="Relational Node ID">
<value>5</value>
</property>
- <property name="Output Columns">
<value>gcol1 (integer)</value>
<value>gcol2 (string)</value>
<value>ssn (string)</value>
<value>agg0 (integer)</value>
</property>
- <property name="Cost Estimates">
<value>Estimated Node Cardinality: -1.0</value>
</property>
- <property name="Child 0">
- <node name="GroupingNode">
- <property name="Relational Node ID">
<value>6</value>
</property>
- <property name="Output Columns">
<value>gcol0 (string)</value>
<value>gcol1 (integer)</value>
<value>gcol2 (string)</value>
<value>agg0 (integer)</value>
</property>
- <property name="Cost Estimates">
<value>Estimated Node Cardinality: -1.0</value>
</property>
- <property name="Child 0">
- <node name="AccessNode">
- <property name="Relational Node ID">
<value>7</value>
</property>
- <property name="Output Columns">
<value>expr (string)</value>
<value>ACCOUNT_ID (integer)</value>
<value>COMPANY_NAME (string)</value>
<value>SHARES_COUNT (integer)</value>
</property>
- <property name="Cost Estimates">
<value>Estimated Node Cardinality: -1.0</value>
</property>
- <property name="Query">
<value>SELECT convert(g_0.ACCOUNT_ID, string), g_0.ACCOUNT_ID, g_1.COMPANY_NAME, g_0.SHARES_COUNT FROM UbuntuMySQL.PORTFOLIO.HOLDINGS AS g_0, UbuntuMySQL.PORTFOLIO.PRODUCT AS g_1 WHERE g_0.PRODUCT_ID = g_1.ID</value>
</property>
- <property name="Model Name">
<value>UbuntuMySQL</value>
</property>
</node>
</property>
- <property name="Grouping Columns">
<value>convert(a.ACCOUNT_ID, string)</value>
<value>a.ACCOUNT_ID</value>
<value>b.COMPANY_NAME</value>
</property>
- <property name="Sort Mode">
<value>false</value>
</property>
</node>
</property>
- <property name="Child 1">
- <node name="AccessNode">
- <property name="Relational Node ID">
<value>8</value>
</property>
- <property name="Output Columns">
<value>account_id (string)</value>
<value>ssn (string)</value>
</property>
- <property name="Cost Estimates">
<value>Estimated Node Cardinality: -1.0</value>
</property>
- <property name="Query">
<value>SELECT g_0.account_id AS c_0, g_0.ssn AS c_1 FROM HadoopSrcModel."default".account AS g_0 ORDER BY c_0</value>
</property>
- <property name="Model Name">
<value>HadoopSrcModel</value>
</property>
</node>
</property>
- <property name="Join Strategy">
<value>ENHANCED SORT JOIN RAN AS SORT MERGE (ALREADY_SORTED/ALREADY_SORTED)</value>
</property>
- <property name="Join Type">
<value>INNER JOIN</value>
</property>
- <property name="Join Criteria">
<value>anon_grp2.gcol0=c.account_id</value>
</property>
</node>
</property>
- <property name="Grouping Columns">
<value>anon_grp2.gcol1</value>
<value>anon_grp2.gcol2</value>
<value>c.ssn</value>
</property>
- <property name="Sort Mode">
<value>false</value>
</property>
</node>
</property>
- <property name="Select Columns">
<value>anon_grp1.gcol0 AS ACCOUNT_ID</value>
<value>anon_grp1.gcol1 AS company_name</value>
<value>anon_grp1.gcol2 AS ssn</value>
<value>IFNULL(convert(anon_grp1.agg0, integer), 0) AS total_shares</value>
</property>
- <property name="Data Bytes Sent">
<value>0</value>
</property>
- <property name="Planning Time">
<value>149</value>
</property>
</node>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months