[JBoss JIRA] (TEIID-5356) Infer field metadata from the source columns
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5356?page=com.atlassian.jira.plugin... ]
Work on TEIID-5356 started by Steven Hawkins.
---------------------------------------------
> Infer field metadata from the source columns
> --------------------------------------------
>
> Key: TEIID-5356
> URL: https://issues.jboss.org/browse/TEIID-5356
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Chandra Akkinepalli
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> This is an observation made in dynamic vdbs.
> When a view is defined without column name , data type, length as in the example below
> create view xyz as (
> select a, b, c from view_model.example
> );
> instead of inferring the column metadata from view_model, the string columns are created with length =4000, this is causing issues when querying such views from visualization tools like Tableau, these fields are forced to be converted to text and failing in the process.
> I would like to request an enhancement for dynamic vdbs to infer metadata from sources in such cases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5356) Infer field metadata from the source columns
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5356?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5356:
----------------------------------
Component/s: Query Engine
Fix Version/s: 11.0
> Infer field metadata from the source columns
> --------------------------------------------
>
> Key: TEIID-5356
> URL: https://issues.jboss.org/browse/TEIID-5356
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Chandra Akkinepalli
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> This is an observation made in dynamic vdbs.
> When a view is defined without column name , data type, length as in the example below
> create view xyz as (
> select a, b, c from view_model.example
> );
> instead of inferring the column metadata from view_model, the string columns are created with length =4000, this is causing issues when querying such views from visualization tools like Tableau, these fields are forced to be converted to text and failing in the process.
> I would like to request an enhancement for dynamic vdbs to infer metadata from sources in such cases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5356) Infer field metadata from the source columns
by Chandra Akkinepalli (JIRA)
Chandra Akkinepalli created TEIID-5356:
------------------------------------------
Summary: Infer field metadata from the source columns
Key: TEIID-5356
URL: https://issues.jboss.org/browse/TEIID-5356
Project: Teiid
Issue Type: Enhancement
Reporter: Chandra Akkinepalli
Assignee: Steven Hawkins
This is an observation made in dynamic vdbs.
When a view is defined without column name , data type, length as in the example below
create view xyz as (
select a, b, c from view_model.example
);
instead of inferring the column metadata from view_model, the string columns are created with length =4000, this is causing issues when querying such views from visualization tools like Tableau, these fields are forced to be converted to text and failing in the process.
I would like to request an enhancement for dynamic vdbs to infer metadata from sources in such cases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5355) Allow for additional partitioning columns in multisource
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5355?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5355.
-----------------------------------
Resolution: Done
Added an extension metadata property teiid_rel:multisource.partitioned that can be set to true on source columns that are partitioned.
> Allow for additional partitioning columns in multisource
> --------------------------------------------------------
>
> Key: TEIID-5355
> URL: https://issues.jboss.org/browse/TEIID-5355
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> In multi-source planning only the multi-source column is recognized as partitioned. It would be beneficial to allow other source columns to be seen as fully partitioned across their respective sources - even if we don't fully capture the partitioning scheme.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months