June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3503: ---------------------------------- Forum Reference: https://developer.jboss.org/message/932452 Also, this has been expressed in the general teiid development scenarios as well. Beyond the reassurance that alpha / preview EAP releases correspond to stable community releases there may be more that needs to be done here. > Use of ModelMetaData required teiid-admin jar > --------------------------------------------- > > Key: TEIID-3503 > URL: https://issues.jboss.org/browse/TEIID-3503 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Affects Versions: 8.10 > Reporter: Michael Davies > Assignee: Ramesh Reddy > Priority: Minor > > We are using Embedded and specifically ModelMetaData, for specifying VDB. > ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo. > For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 > So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo. > Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3503: ------------------------------------- Issue Type: Quality Risk (was: Bug) Assignee: Ramesh Reddy (was: Steven Hawkins) Since the transitive dependencies aren't needed for the embedded runtime we can do something here as lightweight as providing a bom correct? > Use of ModelMetaData required teiid-admin jar > --------------------------------------------- > > Key: TEIID-3503 > URL: https://issues.jboss.org/browse/TEIID-3503 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Affects Versions: 8.10 > Reporter: Michael Davies > Assignee: Ramesh Reddy > Priority: Minor > > We are using Embedded and specifically ModelMetaData, for specifying VDB. > ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo. > For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 > So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo. > Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3491) Add support for REGEXP_REPLACE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3491?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3491: --------------------------------------- Because they are thread safe, we may look at using a more global pattern cache. For pushdown support it does look like we'll have to be careful. Many of the other implementations appear to replace all by default, have support for different or no flags, and the have variations in the regex syntax as you highlight with the back references. More than likely this means we'll need to add a method where the translator can be asked if it supports a given pattern. > Add support for REGEXP_REPLACE > ------------------------------ > > Key: TEIID-3491 > URL: https://issues.jboss.org/browse/TEIID-3491 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > > Add support for REGEXP_REPLACE function like in Postgres. > http://www.postgresql.org/docs/9.3/static/functions-string.html > Pushdown version might be tricky. > * MySQL - No support. > * Postgres - Good. > * Oracle - Good, but "g" flag to replace all matches is set by positional params instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3474) Inconsistent results of RIGHT function for different datasources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3474?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3474: --------------------------------------- It looks like there are 4 columns in the result and 3 columns in the query, is that correct? > Inconsistent results of RIGHT function for different datasources > ---------------------------------------------------------------- > > Key: TEIID-3474 > URL: https://issues.jboss.org/browse/TEIID-3474 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Environment: OS: Fedora 20 > arch: x86_64 > java: oracle 1.8 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > The RIGHT function returns different results for different datasources. Some of those results are inconsistent with definition of the RIGHT(x,y) function. > ======= > +*Query: SELECT intkey, RIGHT(intkey, 1) FROM table ORDER BY intkey*+ > *Teradata, SQLServer, Sybase, Ingres, MySQL, Oracle (this result is OK):* > 0 0 > 1 1 > 2 2 > ... > 10 0 > 11 1 > ... > 100 0 > 101 1 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " > ===== > +*Query:SELECT intkey, RIGHT(intkey, 2) FROM table ORDER BY intkey*+ > *SQLServer, Sybase, Ingress, MySQL, Teradata (this result is OK):* > 0 0 > 1 1 > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Oracle:* > 0 <null> > 1 <null> > 2 <null> > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3502) Teiid returns number of type "byte" which ist out of range

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3502?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3502: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1226936|https://bugzilla.redhat.com/show_bug.cgi?id=1226936] from NEW to CLOSED > Teiid returns number of type "byte" which ist out of range > ---------------------------------------------------------- > > Key: TEIID-3502 > URL: https://issues.jboss.org/browse/TEIID-3502 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid returns for query (1) a number which is out of range for type "byte" (2). The source column has the data type that is wider than byte (3), but e.g. Oracle does not support such small data type as byte so teiid should take care of it. Same with the data type "short". > (1) SELECT bytenum, abs(bytenum) FROM <table>; > (2) > -128 128 > -127 127 > ... > (3) oracle: bytenum - number > teiid: bytenum - byte -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar

by Michael Davies (JIRA)

Michael Davies created TEIID-3503: ------------------------------------- Summary: Use of ModelMetaData required teiid-admin jar Key: TEIID-3503 URL: https://issues.jboss.org/browse/TEIID-3503 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 8.10 Reporter: Michael Davies Assignee: Steven Hawkins Priority: Minor We are using Embedded and specifically ModelMetaData, for specifying VDB. ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo. For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo. Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3502) Teiid returns number of type "byte" which ist out of range

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3502?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3502. ----------------------------------- Resolution: Rejected This is not something that we should compensate for - the source model should use types that are wide enough to represent the source data such that any conversions are then explicitly in a view. > Teiid returns number of type "byte" which ist out of range > ---------------------------------------------------------- > > Key: TEIID-3502 > URL: https://issues.jboss.org/browse/TEIID-3502 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid returns for query (1) a number which is out of range for type "byte" (2). The source column has the data type that is wider than byte (3), but e.g. Oracle does not support such small data type as byte so teiid should take care of it. Same with the data type "short". > (1) SELECT bytenum, abs(bytenum) FROM <table>; > (2) > -128 128 > -127 127 > ... > (3) oracle: bytenum - number > teiid: bytenum - byte -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3474) Inconsistent results of RIGHT function for different datasources

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3474?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3474: ------------------------------------- Maybe another interesting case: teradata: *SELECT doublenum, RIGHT(doublenum, 1), cast(doublenum as string) FROM bqt1.smalla ORDER BY intkey* -24 1 -2.40000000000000E 001 -23 1 -2.30000000000000E 001 ... > Inconsistent results of RIGHT function for different datasources > ---------------------------------------------------------------- > > Key: TEIID-3474 > URL: https://issues.jboss.org/browse/TEIID-3474 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Environment: OS: Fedora 20 > arch: x86_64 > java: oracle 1.8 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > The RIGHT function returns different results for different datasources. Some of those results are inconsistent with definition of the RIGHT(x,y) function. > ======= > +*Query: SELECT intkey, RIGHT(intkey, 1) FROM table ORDER BY intkey*+ > *Teradata, SQLServer, Sybase, Ingres, MySQL, Oracle (this result is OK):* > 0 0 > 1 1 > 2 2 > ... > 10 0 > 11 1 > ... > 100 0 > 101 1 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " > ===== > +*Query:SELECT intkey, RIGHT(intkey, 2) FROM table ORDER BY intkey*+ > *SQLServer, Sybase, Ingress, MySQL, Teradata (this result is OK):* > 0 0 > 1 1 > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Oracle:* > 0 <null> > 1 <null> > 2 <null> > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3502) Teiid returns number of type "byte" which ist out of range

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3502: ----------------------------------- Summary: Teiid returns number of type "byte" which ist out of range Key: TEIID-3502 URL: https://issues.jboss.org/browse/TEIID-3502 Project: Teiid Issue Type: Bug Reporter: Juraj Duráni Assignee: Steven Hawkins Teiid returns for query (1) a number which is out of range for type "byte" (2). The source column has the data type that is wider than byte (3), but e.g. Oracle does not support such small data type as byte so teiid should take care of it. Same with the data type "short". (1) SELECT bytenum, abs(bytenum) FROM <table>; (2) -128 128 -127 127 ... (3) oracle: bytenum - number teiid: bytenum - byte -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3502) Teiid returns number of type "byte" which ist out of range

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3502?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3502: -------------------------------- Affects Version/s: 8.7.1.6_2 > Teiid returns number of type "byte" which ist out of range > ---------------------------------------------------------- > > Key: TEIID-3502 > URL: https://issues.jboss.org/browse/TEIID-3502 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid returns for query (1) a number which is out of range for type "byte" (2). The source column has the data type that is wider than byte (3), but e.g. Oracle does not support such small data type as byte so teiid should take care of it. Same with the data type "short". > (1) SELECT bytenum, abs(bytenum) FROM <table>; > (2) > -128 128 > -127 127 > ... > (3) oracle: bytenum - number > teiid: bytenum - byte -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015