September 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3701) In the JDBC Importer properties, should support "%" wildcard pattern to include/exclude

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3701?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3701. ----------------------------------- Resolution: Rejected There's nothing that prevents the use of wildcards. Ultimately the support is up to the driver. > In the JDBC Importer properties, should support "%" wildcard pattern to include/exclude > --------------------------------------------------------------------------------------- > > Key: TEIID-3701 > URL: https://issues.jboss.org/browse/TEIID-3701 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver > Reporter: Van Halbert > Assignee: Steven Hawkins > > When specifying the JDBC importer properties, should support the use of the jdbc pattern (%) wildcard to include/exclude tables/columns. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3701) In the JDBC Importer properties, should support "%" wildcard pattern to include/exclude

by Van Halbert (JIRA)

Van Halbert created TEIID-3701: ---------------------------------- Summary: In the JDBC Importer properties, should support "%" wildcard pattern to include/exclude Key: TEIID-3701 URL: https://issues.jboss.org/browse/TEIID-3701 Project: Teiid Issue Type: Enhancement Components: JDBC Driver Reporter: Van Halbert Assignee: Steven Hawkins When specifying the JDBC importer properties, should support the use of the jdbc pattern (%) wildcard to include/exclude tables/columns. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3513) make saxon dependency optional for embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3513?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3513. ----------------------------------- Fix Version/s: (was: 8.12) Resolution: Deferred Marking as deferred since designer has forked and we're moving away from the embedded kit. It would be nice to not be tightly dependent upon saxon, but that's a low priority. > make saxon dependency optional for embedded > ------------------------------------------- > > Key: TEIID-3513 > URL: https://issues.jboss.org/browse/TEIID-3513 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > To further modularize embedded saxon should be an optional dependency. Currently the ties into the object model and validation are not isolated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3700) Add a type mapping for impala decimal

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3700?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3700. ----------------------------------- Resolution: Done committed the pull request and updated the logic to move adding the type mapping into the initcapabilities method. > Add a type mapping for impala decimal > ------------------------------------- > > Key: TEIID-3700 > URL: https://issues.jboss.org/browse/TEIID-3700 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > The Impala logic will allow the importer to import decimal types mapped to big decimal, but will not allow the pushdown of a conversion to big decimal. > Support for decimal was added for Imapla 2.1. So we would need to conditionally add support for decimal or update the docs to say change our Impala support which currently starts at 1.2.1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3553: ------------------------------------------------ Michal Sanitrak <msanitra(a)redhat.com> changed the Status of [bug 1234724|https://bugzilla.redhat.com/show_bug.cgi?id=1234724] from ON_QA to VERIFIED > Odata - if table name is ambiguous, teiid returns result from first table > ------------------------------------------------------------------------- > > Key: TEIID-3553 > URL: https://issues.jboss.org/browse/TEIID-3553 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.12 > > > If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3700) Add a type mapping for impala decimal

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3700: ------------------------------------- Summary: Add a type mapping for impala decimal Key: TEIID-3700 URL: https://issues.jboss.org/browse/TEIID-3700 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 The Impala logic will allow the importer to import decimal types mapped to big decimal, but will not allow the pushdown of a conversion to big decimal. Support for decimal was added for Imapla 2.1. So we would need to conditionally add support for decimal or update the docs to say change our Impala support which currently starts at 1.2.1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3553: ------------------------------------------------ Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1234724|https://bugzilla.redhat.com/show_bug.cgi?id=1234724] from MODIFIED to ON_QA > Odata - if table name is ambiguous, teiid returns result from first table > ------------------------------------------------------------------------- > > Key: TEIID-3553 > URL: https://issues.jboss.org/browse/TEIID-3553 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.12 > > > If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3662) IN predicate against a materialized/temp table index without an order by returns wrong results

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3662?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3662: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1257964|https://bugzilla.redhat.com/show_bug.cgi?id=1257964] from ON_QA to VERIFIED > IN predicate against a materialized/temp table index without an order by returns wrong results > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3662 > URL: https://issues.jboss.org/browse/TEIID-3662 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.7.1.6_2, 8.12, 8.11.3 > > > Seeing strange behavior when doing a simple select from {{SPATIAL_REF_SYS}}. > This works as expected: > {code} > select srid, proj4text from spatial_ref_sys where srid in (3875,4326); > srid | proj4text > ------+---------------------------------------------------------------------------------------------------------------- > 3875 | +proj=tmerc +lat_0=0 +lon_0=21 +k=1 +x_0=21500000 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs > 4326 | +proj=longlat +datum=WGS84 +no_defs > (2 rows) > {code} > Swapping the values in the IN causes only one row to be returned. > {code} > select srid, proj4text from spatial_ref_sys where srid in (4326,3875); > srid | proj4text > ------+------------------------------------- > 4326 | +proj=longlat +datum=WGS84 +no_defs > (1 row) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3698) non-selectable columns will cause OData failures

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3698?page=com.atlassian.jira.plugin... ] Ramesh Reddy reopened TEIID-3698: --------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) Re-opening to apply to OData V4 code > non-selectable columns will cause OData failures > ------------------------------------------------ > > Key: TEIID-3698 > URL: https://issues.jboss.org/browse/TEIID-3698 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.12 > > > An odata table/view with a non-selectable column will return an error if it is returned as an odata entity without the $select option to exclude the non-selectable column. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3698) non-selectable columns will cause OData failures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3698?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3698: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1262827 Bugzilla Update: Perform > non-selectable columns will cause OData failures > ------------------------------------------------ > > Key: TEIID-3698 > URL: https://issues.jboss.org/browse/TEIID-3698 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > An odata table/view with a non-selectable column will return an error if it is returned as an odata entity without the $select option to exclude the non-selectable column. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015