[JBoss JIRA] (TEIID-4261) Hive: Add support for array type
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4261?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4261:
-------------------------------------
Fix Version/s: 11.x
(was: 11.2)
Assignee: (was: Steven Hawkins)
We need to add general JDBC array support, then look at Hive in particular. Since we recommend using the JDBC metadata for hive the base support should hopefully work.
> Hive: Add support for array type
> --------------------------------
>
> Key: TEIID-4261
> URL: https://issues.jboss.org/browse/TEIID-4261
> Project: Teiid
> Issue Type: Sub-task
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Priority: Major
> Fix For: 11.x
>
>
> Hive 0.14 added support for Array and Map types. Supporting array types to translator will be good.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-5502) Add better JDBC array support
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5502:
-------------------------------------
Summary: Add better JDBC array support
Key: TEIID-5502
URL: https://issues.jboss.org/browse/TEIID-5502
Project: Teiid
Issue Type: Enhancement
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.2
JDBC import and value retrieval will use the object type and getObject respectively with an array type. It should use the most specific type possible and typically getArray.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-5501) Add a json support for SQL Server
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5501:
-------------------------------------
Summary: Add a json support for SQL Server
Key: TEIID-5501
URL: https://issues.jboss.org/browse/TEIID-5501
Project: Teiid
Issue Type: Sub-task
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.x
SQL Server json support should be mapped to the json runtime type.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2476:
---------------------------------------
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1609306
A question brought up on the BZ was about the visibility of schema entries - yes that is a known limitation of this initial implementation. The basic problem is highlighted by the code comment:
//TODO - schemas cannot be hidden - unless we traverse them and find that nothing is accessible
That is you can have no general access to a schema, but turn on access to a particular table. In which case we cannot omit the schema from the metadata. So at worst you are leaking the names of all of the schema in the vdb. An issue can be opened on this if needed.
> Exclude hidden tables/columns from metadata
> -------------------------------------------
>
> Key: TEIID-2476
> URL: https://issues.jboss.org/browse/TEIID-2476
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 9.0, 8.12.15.6_4
>
>
> We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-5500) Improve OData performance
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5500:
-------------------------------------
Summary: Improve OData performance
Key: TEIID-5500
URL: https://issues.jboss.org/browse/TEIID-5500
Project: Teiid
Issue Type: Enhancement
Components: OData, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.x
See https://developer.jboss.org/thread/277783
There is a significant overhead for OData vs. JDBC for a single client especially in terms of latency.
We should investigate pre-building additional batch results and entity caching in general.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months