[JBoss JIRA] (TEIID-5089) Using Teiid Conn. importer in Designer, the cache name is set to "default"
by Van Halbert (JIRA)
Van Halbert created TEIID-5089:
----------------------------------
Summary: Using Teiid Conn. importer in Designer, the cache name is set to "default"
Key: TEIID-5089
URL: https://issues.jboss.org/browse/TEIID-5089
Project: Teiid
Issue Type: Bug
Components: Infinispan
Affects Versions: 8.12.x-6.4
Reporter: Van Halbert
Assignee: Ramesh Reddy
When using the Teiid Connection importer in Designer to reversen engineer the source table from an existing JDG cache. The following is an example of the DDL returned by teiid:
{code}
SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_ispn;
CREATE FOREIGN TABLE Person (
id integer OPTIONS (ANNOTATION '@Id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int32', "teiid_ispn:TAG" '1'),
name string OPTIONS (SEARCHABLE 'Searchable', NATIVE_TYPE 'string', "teiid_ispn:TAG" '2'),
salary double OPTIONS (SEARCHABLE 'Searchable', NATIVE_TYPE 'double', "teiid_ispn:TAG" '3'),
CONSTRAINT PK_ID PRIMARY KEY(id)
) OPTIONS (ANNOTATION '@Indexed', NAMEINSOURCE 'JDGPersonCache.Person', UPDATABLE TRUE, "teiid_ispn:CACHE" 'default');
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4356) Add asort of connection test for "connection definitions" of resource adapters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4356?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4356:
----------------------------------
Fix Version/s: 10.x
(was: 10.0)
> Add asort of connection test for "connection definitions" of resource adapters
> ------------------------------------------------------------------------------
>
> Key: TEIID-4356
> URL: https://issues.jboss.org/browse/TEIID-4356
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Marco Ardito
> Priority: Minor
> Fix For: 10.x
>
>
> Could a sort of "connection test" be implemented to verify if a "connection definition" specified for a resource adapter (eg: file, google, etc) is working, and can "connect" to the resource it's supposedly pointing to?
> Data sources(jdbc) already have this kind of test, and it is quite useful to test if there's any error in their connection definition.
> With resource adapters, one must define connection definitions, but it is not possible to test them, independently from later requests/queries (eg: reading data from .csv or .xls files, or oauth web services): one has to build all the chain and really try to get data from the source, using the vdb, hoping everything is correctly defined...
> Recently I am struggling with a custom rest oauth2 RA, and I need to define
> - security domain (with client id/secret, tokens, auth uri)
> - RA using that domain
> - a connection definition for the RA accessing the remote data source
> - a VDB using the connection definition
> - a client using the VDB to try get data in sql form
> any step could be wrong, but only the last allows to check if the whole chain is working, or not.
> For any error or failure, regular users (like me) can't do anything else than double check everything... a "test connection" button, for the connection definition, would do wonders to simplify setup debug...
> Marco
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4558) Query Plan Analyzer
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4558?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4558:
----------------------------------
Fix Version/s: 10.x
(was: Open To Community)
(was: 10.0)
> Query Plan Analyzer
> -------------------
>
> Key: TEIID-4558
> URL: https://issues.jboss.org/browse/TEIID-4558
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Affects Versions: 9.2
> Reporter: Van Halbert
> Fix For: 10.x
>
>
> Provide a tool that would take a query plan and provide feed back.
> Example:
> - indicate where there maybe a problem in the structure of the query that may impact performance
> - indicate in the plan where there maybe issues (like table scan, no rows, etc.)
> - provide recommendations for improving performance
> etc..
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-3454) Dependent Join optimizations for Netezza and Hive
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3454?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3454:
-------------------------------------
Fix Version/s: 10.x
(was: 10.0)
Assignee: (was: Steven Hawkins)
> Dependent Join optimizations for Netezza and Hive
> -------------------------------------------------
>
> Key: TEIID-3454
> URL: https://issues.jboss.org/browse/TEIID-3454
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.10
> Reporter: John Muller
> Fix For: 10.x
>
>
> Currently, dependent joins create 1 or more IN clauses. Many MPP / NoSQL systems can have drastically better performance by creating temp tables that match key distributions. Two examples I know of would be Netezza and Hive.
> In Netezza, if the incoming dependent join (small dimension; here "Customer" using Northwind data model concepts) has a key that will be joined to to a big fact table that is DISTRIBUTED ON or ORGANIZED BY 'ed then creating a temp table that matches this distribution will result in ~100x query performance. Sometimes, if the dimension is small enough, this doesn't make a big difference as Netezza will perform a broadcast join, but it's never a bad idea to create the temp table.
> Similarly, Hive DDL has both partitions and buckets (pre-sorted).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4452) Pushdown SQL/XML
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4452?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4452:
----------------------------------
Fix Version/s: 10.x
(was: 10.0)
> Pushdown SQL/XML
> ----------------
>
> Key: TEIID-4452
> URL: https://issues.jboss.org/browse/TEIID-4452
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Affects Versions: 9.x
> Reporter: Tom Arnold
> Fix For: 10.x
>
>
> It would be helpful to pushdown SQL/XML functions for JDBC databases that support them.
> Databases:
> - Oracle
> - Postgres
> Functions:
> - XMLELEMENT
> - XMLATTRIBUTES
> - XMLAGG
> - XMLCONCAT
> We have an application that uses these functions and we support Oracle, Postgres, and Teiid (to integrate external data sources). Here's an example query generated by this application:
> {code:xml}
> select
> "ITEMS"."ITEM_ID" "ITEM_ID",
> (
> select xmlelement (
> name "attributes",
> xmlagg(
> xmlelement(
> name "attribute",
> xmlattributes(
> "ITEM_ATTRIBUTES"."ATTR_NAME" as "name",
> "ITEM_ATTRIBUTES"."ATTR_VALUE" as "value"
> )
> )
> )
> )
> from "ITEM_ATTRIBUTES" "ITEM_ATTRIBUTES"
> where (
> "ITEMS"."ITEM_ID" = "ITEM_ATTRIBUTES"."ITEM_ID"
> )
> ) "ITEM_ATTRIBUTES"
> {code}
> {code}
> ITEM_ID ITEM_ATTRIBUTES
> 3 <attributes><attribute name="foo" value="bar"></attribute><attribute name="baz" value="blah"></attribute></attributes>
> 4 <attributes><attribute name="foo" value="123"></attribute><attribute name="baz" value="456"></attribute></attributes>
> {code}
> When we are using Teiid queries like this do not work well because they cannot be pushed down, so we get N-many queries (one per row) and the query ends up taking much longer than if performed directly against Oracle/Postgres.
> Since SQL/XML is standard and supported by both Oracle/Postgres it would be good if queries like this could be pushed in their entirety so that there would be no performance difference between going through Teiid and native.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months