[JBoss JIRA] (TEIID-2558) Add translator support for dependent join pushdown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2558?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2558:
---------------------------------------
Added initial support for the sources listed above except for informix/ingres/teradata. Oracle support when under a transaction uses a pl/sql block to call execute immediate in an autonomous transaction to create the temp table. The cardinality hint for oracle and additional source hinting in general, and index creation will still be need to be investigated.
> Add translator support for dependent join pushdown
> --------------------------------------------------
>
> Key: TEIID-2558
> URL: https://issues.jboss.org/browse/TEIID-2558
> Project: Teiid
> Issue Type: Sub-task
> Components: Connector API
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> JDBC translators should offer built-in support for dependent join pushdown - possibly with index creation and other options.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2578) Provide API to add schema elements at translator layer
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2578:
--------------------------------
Fix Version/s: 8.5
> Provide API to add schema elements at translator layer
> ------------------------------------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> Currently the translator API is can expose the source schema they represent, however there are no facilities to create the schema elements like
> * table
> * procedure
> the function support is available, but this needs be re-factored under this interface (may be this can be a follow on task)
> Using this feature, query engine should be able to ad-hoc create tables or procedures. The motivation for the feature is to provide a more comprehensive materialization feature.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2578) Provide API to add schema elements at translator layer
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2578:
--------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Provide API to add schema elements at translator layer
> ------------------------------------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.5
>
>
> Currently the translator API is can expose the source schema they represent, however there are no facilities to create the schema elements like
> * table
> * procedure
> the function support is available, but this needs be re-factored under this interface (may be this can be a follow on task)
> Using this feature, query engine should be able to ad-hoc create tables or procedures. The motivation for the feature is to provide a more comprehensive materialization feature.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2558) Add translator support for dependent join pushdown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2558?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2558:
---------------------------------------
A quick scan of sources would break down as:
No Issues:
h2
teiid/mm
db2 (declare)
hsql
mysql
pg (but will need a post creation analyze call)
sqlserver
Transaction Issues:
oracle (may need a cardinality hint, but at least for 9ir2+ the default of dynamic sampling should suffice)
Possible Transactional Issues:
informix
ingres
teradata
> Add translator support for dependent join pushdown
> --------------------------------------------------
>
> Key: TEIID-2558
> URL: https://issues.jboss.org/browse/TEIID-2558
> Project: Teiid
> Issue Type: Sub-task
> Components: Connector API
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> JDBC translators should offer built-in support for dependent join pushdown - possibly with index creation and other options.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2578) Provide API to add schema elements at translator layer
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2578:
-----------------------------------
Summary: Provide API to add schema elements at translator layer
Key: TEIID-2578
URL: https://issues.jboss.org/browse/TEIID-2578
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Currently the translator API is can expose the source schema they represent, however there are no facilities to create the schema elements like
* table
* procedure
the function support is available, but this needs be re-factored under this interface (may be this can be a follow on task)
Using this feature, query engine should be able to ad-hoc create tables or procedures. The motivation for the feature is to provide a more comprehensive materialization feature.
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2566) standalone-teiid.xml and the CLI scripts point to different caches in the teiid subsystem
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2566?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2566.
---------------------------------
Resolution: Done
Updated the script to include the correct cache name
> standalone-teiid.xml and the CLI scripts point to different caches in the teiid subsystem
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-2566
> URL: https://issues.jboss.org/browse/TEIID-2566
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Minor
> Fix For: 8.4.1, 8.5
>
>
> In the standalone-teiid.xml configuration, teiid subsystem:
> <resultset-cache infinispan-container="teiid" name="resultset"/>
> <preparedplan-cache infinispan-container="teiid" name="preparedplan"/>
> In the CLI script, it contains the following:
> /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=teiid-cache, preparedplan-cache-infinispan-container=teiid-cache, policy-decider-module=org.jboss.teiid)
> and looks like the following when loaded:
> <resultset-cache infinispan-container="teiid-cache"/>
> <preparedplan-cache infinispan-container="teiid-cache"/>
>
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2559) Add additional make dep hint options
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2559?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2559:
---------------------------------------
min has been removed as an option as by pushing the pushdown processing to the dependentcriteriaprocessor we can reuse the logic to perform duplication removal and detect if multiple commands will be issued which triggers the pushdown.
> Add additional make dep hint options
> ------------------------------------
>
> Key: TEIID-2559
> URL: https://issues.jboss.org/browse/TEIID-2559
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> make dep hints should support additional options to facilitate TEIID-2249. This includes:
> min - the minimum number of rows to trigger a dependent join full pushdown
> max - the maximum number of rows allowed before rejecting the dependent join (this would apply in both full pushdown and partial non-pushdown scenarios - in the latter though it will likely refer to the number of distinct values)
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2538) Validate Apache Hive 0.11 version of Driver
by Filip Nguyen (JIRA)
[ https://issues.jboss.org/browse/TEIID-2538?page=com.atlassian.jira.plugin... ]
Filip Nguyen commented on TEIID-2538:
-------------------------------------
Need more information on this one. Is this referring to standard metadata-load that is happening during the VDB startup? I see no problem with this, but it is necessary to use the new "importer.trimColumNames" property, because there is a bug associated with 0.11 version of Hive driver.
My test setup is as follows. I am using Hortonworks sandbox Hortonworks+Sandbox+1.3+VirtualBox+RC6.ova. Then I overlayed modules in the AS by those that can be found in hortonworks tarball distro [1] (AFAIK it is not possible to get those Jars directly from SANDBOX VM). After starting the sandbox I deploy the driver to AS and a VDB with the "importer.trimColumNames" set to true. I am then able to query the VDB using standard JDBC client:
{noformat}
./run.sh localhost 31000 hadoop "select * from sample_07"
Executing using the TeiidDriver
Results
1: 00-0000,All Occupations,134354250,40690
2: 11-0000,Management occupations,6003930,96150
...
{noformat}
[1] http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.3.1/bk_installing_man...
> Validate Apache Hive 0.11 version of Driver
> -------------------------------------------
>
> Key: TEIID-2538
> URL: https://issues.jboss.org/browse/TEIID-2538
> Project: Teiid
> Issue Type: Task
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Filip Nguyen
> Fix For: 8.4.1
>
>
> There are report that the metadata does not load properly when used with Apache Hive 0.11 version of the JDBC driver. This needs to be validated and make any changes that are required.
> Test with Hive driver that comes with the Hortonworks Sandbox distro
--
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
11 years, 5 months
[JBoss JIRA] (TEIID-2558) Add translator support for dependent join pushdown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2558?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2558:
---------------------------------------
> May be hybrid approach based on cardinality of push size? May be JDBC driver is contributing to performance of creation of table?
Compared to the overall join the creation of a temp table or array/struct types is not that expensive - however for the particular database, such as Oracle, it's really considered an anti-pattern to issue DDL on an ad hoc basis. This is a general problem for any databases that has similar restrictions (only global temp tables, forcing commit when issuing ddl, etc.).
So for Oracle what I'm really saying is that for reasonably sized single column string or number based join the array method using an existing system array type is the only method that works without issuing DDL.
> Add translator support for dependent join pushdown
> --------------------------------------------------
>
> Key: TEIID-2558
> URL: https://issues.jboss.org/browse/TEIID-2558
> Project: Teiid
> Issue Type: Sub-task
> Components: Connector API
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> JDBC translators should offer built-in support for dependent join pushdown - possibly with index creation and other options.
--
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
11 years, 5 months