November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3810) Updating teiid-tools archetypes

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3810?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3810: ------------------------------- Git Pull Request: https://github.com/teiid/teiid-tools/pull/20 > Updating teiid-tools archetypes > -------------------------------- > > Key: TEIID-3810 > URL: https://issues.jboss.org/browse/TEIID-3810 > Project: Teiid > Issue Type: Task > Components: Tools > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x > > > Updating teiid-tools archetypes to be based on Teiid 8.12.0.Final > Adding in a docs section to be included with the jboss-as7 distribution. > Adding a default ResourceAdapter for the connector. > Adding an example ExecutionFactory unit test that provides a starting point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3810) Updating teiid-tools archetypes

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3810?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3810: ------------------------------- Fix Version/s: 8.12.x > Updating teiid-tools archetypes > -------------------------------- > > Key: TEIID-3810 > URL: https://issues.jboss.org/browse/TEIID-3810 > Project: Teiid > Issue Type: Task > Components: Tools > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x > > > Updating teiid-tools archetypes to be based on Teiid 8.12.0.Final > Adding in a docs section to be included with the jboss-as7 distribution. > Adding a default ResourceAdapter for the connector. > Adding an example ExecutionFactory unit test that provides a starting point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3810) Updating teiid-tools archetypes

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3810?page=com.atlassian.jira.plugin... ] Work on TEIID-3810 stopped by Van Halbert. ------------------------------------------ > Updating teiid-tools archetypes > -------------------------------- > > Key: TEIID-3810 > URL: https://issues.jboss.org/browse/TEIID-3810 > Project: Teiid > Issue Type: Task > Components: Tools > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > > Updating teiid-tools archetypes to be based on Teiid 8.12.0.Final > Adding in a docs section to be included with the jboss-as7 distribution. > Adding a default ResourceAdapter for the connector. > Adding an example ExecutionFactory unit test that provides a starting point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3817) HANA FLOOR and CELING functions not applicable to boolean

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3817?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3817: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1279727 Bugzilla Update: Perform > HANA FLOOR and CELING functions not applicable to boolean > --------------------------------------------------------- > > Key: TEIID-3817 > URL: https://issues.jboss.org/browse/TEIID-3817 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > SAP HANA doesn't support FLOOR and CEILING functions for BOOLEAN type. > Compared to postgresql, which also has BOOLEAN data type, it seems inconsistent. > When querying postgres directly: > {code:sql} > SELECT CEILING(BooleanValue) FROM BQT1.SmallA > {code} > is not valid query. > But through Teiid, it returns double values corresponding to the boolean value provided: > 0.0 for CEILING(false) > 1.0 for CELING(true) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3812) HANA MIN and MAX functions not applicable on boolean

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-3812?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-3812: ------------------------------------ Based on Steven's comment I created https://issues.jboss.org/browse/TEIID-3817 > HANA MIN and MAX functions not applicable on boolean > ---------------------------------------------------- > > Key: TEIID-3812 > URL: https://issues.jboss.org/browse/TEIID-3812 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > SAP HANA doesn't support MIN and MAX functions for BOOLEAN type. > Compared to postgresql, which also has BOOLEAN data type, it seems inconsistent, as postgresql translator mimics MIN and MAX functions by translating them using PostgreSQL specific constructs: > min(BooleanValue) as bool_and(BooleanValue) > max(BooleanValue) as bool_or(BooleanValue) > Similar issue is with CEILING and FLOOR functions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3817) HANA FLOOR and CELING functions not applicable to boolean

by Jan Stastny (JIRA)

Jan Stastny created TEIID-3817: ---------------------------------- Summary: HANA FLOOR and CELING functions not applicable to boolean Key: TEIID-3817 URL: https://issues.jboss.org/browse/TEIID-3817 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.7.1.6_2 Reporter: Jan Stastny Assignee: Steven Hawkins SAP HANA doesn't support FLOOR and CEILING functions for BOOLEAN type. Compared to postgresql, which also has BOOLEAN data type, it seems inconsistent. When querying postgres directly: {code:sql} SELECT CEILING(BooleanValue) FROM BQT1.SmallA {code} is not valid query. But through Teiid, it returns double values corresponding to the boolean value provided: 0.0 for CEILING(false) 1.0 for CELING(true) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3811) Teiid Embedded with remote JDBC susceptible to exploit with common-collections in classpath

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3811?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3811. ----------------------------------- Fix Version/s: 8.12.2 8.13 Resolution: Done Explicitly disallowed the class resolution of offending classes. Will post a note in the embedded guide about having offending libraries in the class path. > Teiid Embedded with remote JDBC susceptible to exploit with common-collections in classpath > ------------------------------------------------------------------------------------------- > > Key: TEIID-3811 > URL: https://issues.jboss.org/browse/TEIID-3811 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12.2, 8.13 > > > This issue is to add at least a documentation note warning against - http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-j... > While remote JDBC is not enabled by default and common-collections is not in the classpath it is possible that common-collections could be picked up from the environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3805) HANA SUBSTRING function inconsistent with teiid behaviour

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3805?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3805. ----------------------------------- Resolution: Deferred Added a release note and updated the docs, will mark the issue as deferred until it's needed to be addressed by a customer case. > HANA SUBSTRING function inconsistent with teiid behaviour > --------------------------------------------------------- > > Key: TEIID-3805 > URL: https://issues.jboss.org/browse/TEIID-3805 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > When querying HANA using hana translator, there is an inconsistency in handling SUBSTRING with similar parameters: > {code:sql} > SELECT SUBSTRING('sth',20,1) FROM tablename > {code} > That is, when the starting offset supplied to SUBSTRING function is greater than the length of the string value, Teiid returns NULL in this case. > But when I run: > {code:sql} > SELECT SUBSTRING(STRINGNUM,20,1) FROM bqt1.smalla > {code} > (it is pushed to HANA and STRINGNUM column contains strings of length <=2) > I get empty strings instead of NULL values, which is default in Teiid. > This inconsistency is caused by different handling of such situation on HANA's side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3812) HANA MIN and MAX functions not applicable on boolean

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3812?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3812: --------------------------------------- Floor/Ceiling expect the argument to be a double, so that would be a different issue. Can you log that separately? > HANA MIN and MAX functions not applicable on boolean > ---------------------------------------------------- > > Key: TEIID-3812 > URL: https://issues.jboss.org/browse/TEIID-3812 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > SAP HANA doesn't support MIN and MAX functions for BOOLEAN type. > Compared to postgresql, which also has BOOLEAN data type, it seems inconsistent, as postgresql translator mimics MIN and MAX functions by translating them using PostgreSQL specific constructs: > min(BooleanValue) as bool_and(BooleanValue) > max(BooleanValue) as bool_or(BooleanValue) > Similar issue is with CEILING and FLOOR functions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3796) It is much more slow to get the table record through TEIID from postgresql DB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3796?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3796: --------------------------------------- Is there any update on the details here? If not we'll resolve as incomplete description for now. > It is much more slow to get the table record through TEIID from postgresql DB > ----------------------------------------------------------------------------- > > Key: TEIID-3796 > URL: https://issues.jboss.org/browse/TEIID-3796 > Project: Teiid > Issue Type: Bug > Reporter: Xian Liu > Assignee: Steven Hawkins > > There is a table about 1000K+ record > Postgresql Version: server 9.2.7 > Postgresql DB JDBC Driver Version: postgresql-9.3-1103.jdbc4.jar > The table definition: > {code} > | Type | Modifiers > ------------+-----------------------------+------------------------------------------------------------ > | integer | not null > | integer | > | integer | not null > | timestamp without time zone | not null > | integer | not null > | text | > | text | > | bigint | > | bigint | not null > | integer | > {code} > I set driver connection parameter to disableLocalTxn=true;FetchSize=10; > 1. When I make this table available in Mysql, and select * from it in Teiid, It will quickly get the data stream after around 30s. > 2. But when I make this table in Postgresql DB, and query through Teiid, it is so slow and will get about 8min+ client can not get the data stream, > when I try to directly connect this table in Postgresql table, it is much more faster, I do not know the reason. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2015