March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3387) MongoDB resource adapter doesn't support all authentication mechanisms

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3387?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3387: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > MongoDB resource adapter doesn't support all authentication mechanisms > ---------------------------------------------------------------------- > > Key: TEIID-3387 > URL: https://issues.jboss.org/browse/TEIID-3387 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.10 > Reporter: Burak Serdar > Assignee: Ramesh Reddy > > It appears like mongodb resource adapter only supports Database, Username, Password, and RemoteServerList properties. It does not support: > - SSL connections > - a way to specify authenticationDatabase for MONGODB-CR mechanism -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3387) MongoDB resource adapter doesn't support all authentication mechanisms

by Burak Serdar (JIRA)

Burak Serdar created TEIID-3387: ----------------------------------- Summary: MongoDB resource adapter doesn't support all authentication mechanisms Key: TEIID-3387 URL: https://issues.jboss.org/browse/TEIID-3387 Project: Teiid Issue Type: Bug Affects Versions: 8.10 Reporter: Burak Serdar Assignee: Steven Hawkins It appears like mongodb resource adapter only supports Database, Username, Password, and RemoteServerList properties. It does not support: - SSL connections - a way to specify authenticationDatabase for MONGODB-CR mechanism -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3386) Mixed resutl with (double) full outer join and where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3386?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3386: --------------------------------------- This is not reproducible for me at least with Teiid latest. Can you also attach the source query that is being issued? It looks like it would be a full pushdown scenario as the models are using the same translator/connection. > Mixed resutl with (double) full outer join and where clause > ----------------------------------------------------------- > > Key: TEIID-3386 > URL: https://issues.jboss.org/browse/TEIID-3386 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If a query contains double FULL OUTER JOIN and WHERE clause that contains condition on column from last table, teiid returns mixed result (underlying oracle10). > Query: > SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey > FROM (BQT1.SmallA FULL OUTER JOIN BQT2.MediumB ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey) FULL OUTER JOIN BQT2.LargeB ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey > WHERE BQT2.LargeB.IntKey < 1500 ORDER BY LargeB_IntKey, MediumB_IntKey, SmallA_IntKey; > Actual result: > 0 0 0 > 1 1 1 > 2 2 2 > 3 3 3 > ... ... ... > 49 49 49 > 50 50 50 > ... ... ... > 999 999 999 > <null> <null> 1000 > ... ... ... > <null> <null> 1499 > Expected result: > 0 0 0 > 1 1 1 > 2 2 2 > 3 3 3 > ... ... ... > 49 49 49 > <null> 50 50 > ... ... ... > 999 999 999 > <null> <null> 1000 > ... ... ... > <null> <null> 1499 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3386) Mixed resutl with (double) full outer join and where clause

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3386: ----------------------------------- Summary: Mixed resutl with (double) full outer join and where clause Key: TEIID-3386 URL: https://issues.jboss.org/browse/TEIID-3386 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1 Reporter: Juraj Duráni Assignee: Steven Hawkins If a query contains double FULL OUTER JOIN and WHERE clause that contains condition on column from last table, teiid returns mixed result (underlying oracle10). Query: SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey FROM (BQT1.SmallA FULL OUTER JOIN BQT2.MediumB ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey) FULL OUTER JOIN BQT2.LargeB ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey WHERE BQT2.LargeB.IntKey < 1500 ORDER BY LargeB_IntKey, MediumB_IntKey, SmallA_IntKey; Actual result: 0 0 0 1 1 1 2 2 2 3 3 3 ... ... ... 49 49 49 50 50 50 ... ... ... 999 999 999 <null> <null> 1000 ... ... ... <null> <null> 1499 Expected result: 0 0 0 1 1 1 2 2 2 3 3 3 ... ... ... 49 49 49 <null> 50 50 ... ... ... 999 999 999 <null> <null> 1000 ... ... ... <null> <null> 1499 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3385) ResultSetMetaData returns wrong column name after renaming (using AS)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3385?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3385: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1202830|https://bugzilla.redhat.com/show_bug.cgi?id=1202830] from NEW to CLOSED > ResultSetMetaData returns wrong column name after renaming (using AS) > --------------------------------------------------------------------- > > Key: TEIID-3385 > URL: https://issues.jboss.org/browse/TEIID-3385 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Query: SELECT IntKey AS a FROM <table>; > Issues: > - ResultSetMetaData object returns name of the column "IntKey", but it should return "a". > - method ResultSet.getString("IntKey") thows an exception (org.teiid.jdbc.TeiidSQLException: Column name "INTKEY" does not exist.), but ResultSet.getString("a") returns the correct result. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3385) ResultSetMetaData returns wrong column name after renaming (using AS)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3385?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3385. ----------------------------------- Resolution: Rejected See TEIID-1651 Note that getString specifies that the column label should be used http://docs.oracle.com/javase/7/docs/api/java/sql/ResultSet.html#getStrin... > ResultSetMetaData returns wrong column name after renaming (using AS) > --------------------------------------------------------------------- > > Key: TEIID-3385 > URL: https://issues.jboss.org/browse/TEIID-3385 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Query: SELECT IntKey AS a FROM <table>; > Issues: > - ResultSetMetaData object returns name of the column "IntKey", but it should return "a". > - method ResultSet.getString("IntKey") thows an exception (org.teiid.jdbc.TeiidSQLException: Column name "INTKEY" does not exist.), but ResultSet.getString("a") returns the correct result. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3385) ResultSetMetaData returns wrong column name after renaming (using AS)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3385?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3385: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1202830 > ResultSetMetaData returns wrong column name after renaming (using AS) > --------------------------------------------------------------------- > > Key: TEIID-3385 > URL: https://issues.jboss.org/browse/TEIID-3385 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Query: SELECT IntKey AS a FROM <table>; > Issues: > - ResultSetMetaData object returns name of the column "IntKey", but it should return "a". > - method ResultSet.getString("IntKey") thows an exception (org.teiid.jdbc.TeiidSQLException: Column name "INTKEY" does not exist.), but ResultSet.getString("a") returns the correct result. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3385) ResultSetMetaData returns wrong column name after renaming (using AS)

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3385: ----------------------------------- Summary: ResultSetMetaData returns wrong column name after renaming (using AS) Key: TEIID-3385 URL: https://issues.jboss.org/browse/TEIID-3385 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1 Reporter: Juraj Duráni Assignee: Steven Hawkins Query: SELECT IntKey AS a FROM <table>; Issues: - ResultSetMetaData object returns name of the column "IntKey", but it should return "a". - method ResultSet.getString("IntKey") thows an exception (org.teiid.jdbc.TeiidSQLException: Column name "INTKEY" does not exist.), but ResultSet.getString("a") returns the correct result. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3376) SQL Server 2008/2012 - incompatible data types in comparison after cast/convert

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3376?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3376 at 3/16/15 7:29 PM: ---------------------------------------------------------------- Added another commit to fix an issue with the SQL Server start method. We are now defaulting the database version to an exception if not set so that the behavior is more clear. With the old logic the translator would start with the default version and not see that the time type was available, then once it initialized the capabilities would see that the time type was available and the scenario from this issue would fail. Also added a minor of synchronization around modifications to the executionfactory state to ensure consistency. Although there may need to be some additional locking on the the other executionfactory method calls to ensure full consistency. was (Author: shawkins): Added another commit to fix an issue with the SQL Server start method. We are now defaulting the database version to an exception if not set so that the behavior is more clear. With the old logic the translator would start with the default version and not see that the time type was available, then once it initialized the capabilities would see that the time type was available and the scenario from this issue would fail. Also added a minor of synchronization around modifications to the executionfactory state to ensure consistency. > SQL Server 2008/2012 - incompatible data types in comparison after cast/convert > ------------------------------------------------------------------------------- > > Key: TEIID-3376 > URL: https://issues.jboss.org/browse/TEIID-3376 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora 20 > java: oracle 1.7 > arch: x86_64 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.11 > > > If user want to cast/convert timestamp-value to time and then use it in comparison, Teiid throws an Exception: > "SQLServerException: The data types datetime and time are incompatible in the greater than operator." > Expected behavior: > The query should return correct result as the SQL Server is able to handle similar queries (teiid does not have any problem with same query with oracle, postgres, mysql,...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3376) SQL Server 2008/2012 - incompatible data types in comparison after cast/convert

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3376?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3376: --------------------------------------- Added another commit to fix an issue with the SQL Server start method. We are now defaulting the database version to an exception if not set so that the behavior is more clear. With the old logic the translator would start with the default version and not see that the time type was available, then once it initialized the capabilities would see that the time type was available and the scenario from this issue would fail. Also added a minor of synchronization around modifications to the executionfactory state to ensure consistency. > SQL Server 2008/2012 - incompatible data types in comparison after cast/convert > ------------------------------------------------------------------------------- > > Key: TEIID-3376 > URL: https://issues.jboss.org/browse/TEIID-3376 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora 20 > java: oracle 1.7 > arch: x86_64 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.11 > > > If user want to cast/convert timestamp-value to time and then use it in comparison, Teiid throws an Exception: > "SQLServerException: The data types datetime and time are incompatible in the greater than operator." > Expected behavior: > The query should return correct result as the SQL Server is able to handle similar queries (teiid does not have any problem with same query with oracle, postgres, mysql,...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015