June 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5357) creating a ddl table with two unique columns fails

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5357: ------------------------------------- Summary: creating a ddl table with two unique columns fails Key: TEIID-5357 URL: https://issues.jboss.org/browse/TEIID-5357 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.0, 10.3.2, 10.2.3 DDL such as: CREATE FOREIGN TABLE G1(e2 varchar(10) unique, e3 date not null unique); Will fail to validate properly as both columns will be add a unique index with the same name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[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)

7 years, 10 months

1
0
0 / 0

[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)

7 years, 10 months

1
0
0 / 0

[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)

7 years, 10 months

1
0
0 / 0

[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)

7 years, 10 months

1
0
0 / 0

[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... ] Work on TEIID-5355 started by Steven Hawkins. --------------------------------------------- > 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)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4520: ---------------------------------- Fix Version/s: (was: Open To Community) Rafal, when you are ready mark this as resolved. > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Rafal Korytkowski > Fix For: 11.0 > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Rafal Korytkowski (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Rafal Korytkowski commented on TEIID-4520: ------------------------------------------ New PR with fixes at https://github.com/teiid/teiid/pull/1081 > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Rafal Korytkowski > Fix For: 11.0, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2018