March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3388) Different null ordering for float and double numbers with RADIANS function (Oracle 12)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3388?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3388. ----------------------------------- Resolution: Rejected The models are different between these two cases such that we'll push the order by for the ora 12 query, but not ora 10 (there is a conversion on floatnum for example that doesn't exist in ora 12). In any case this results in the different null orderings as null ordering is not guaranteed unless you add a nulls first/last clause to the order key: order by floatnum nulls first See https://docs.jboss.org/author/display/TEIID/ORDER+BY+Clause > Different null ordering for float and double numbers with RADIANS function (Oracle 12) > -------------------------------------------------------------------------------------- > > Key: TEIID-3388 > URL: https://issues.jboss.org/browse/TEIID-3388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server_ora10.log, server_ora12.log > > > Queries: > 1. SELECT RADIANS(DoubleNum) FROM BQT1.SmallA ORDER BY DoubleNum; > 2. SELECT RADIANS(FloatNum) FROM BQT1.SmallA ORDER BY FloatNum; > Both queries return different null ordering. In case of DoubleNum nulls are first. In the second case nulls are last records. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3388) Different null ordering for float and double numbers with RADIANS function (Oracle 12)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3388?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3388: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1203128 > Different null ordering for float and double numbers with RADIANS function (Oracle 12) > -------------------------------------------------------------------------------------- > > Key: TEIID-3388 > URL: https://issues.jboss.org/browse/TEIID-3388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server_ora10.log, server_ora12.log > > > Queries: > 1. SELECT RADIANS(DoubleNum) FROM BQT1.SmallA ORDER BY DoubleNum; > 2. SELECT RADIANS(FloatNum) FROM BQT1.SmallA ORDER BY FloatNum; > Both queries return different null ordering. In case of DoubleNum nulls are first. In the second case nulls are last records. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3388) Different null ordering for float and double numbers with RADIANS function (Oracle 12)

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3388: ----------------------------------- Summary: Different null ordering for float and double numbers with RADIANS function (Oracle 12) Key: TEIID-3388 URL: https://issues.jboss.org/browse/TEIID-3388 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1 Reporter: Juraj Duráni Assignee: Steven Hawkins Attachments: server_ora10.log, server_ora12.log Queries: 1. SELECT RADIANS(DoubleNum) FROM BQT1.SmallA ORDER BY DoubleNum; 2. SELECT RADIANS(FloatNum) FROM BQT1.SmallA ORDER BY FloatNum; Both queries return different null ordering. In case of DoubleNum nulls are first. In the second case nulls are last records. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3388) Different null ordering for float and double numbers with RADIANS function (Oracle 12)

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3388?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3388: -------------------------------- Attachment: server_ora10.log server_ora12.log Server logs. > Different null ordering for float and double numbers with RADIANS function (Oracle 12) > -------------------------------------------------------------------------------------- > > Key: TEIID-3388 > URL: https://issues.jboss.org/browse/TEIID-3388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server_ora10.log, server_ora12.log > > > Queries: > 1. SELECT RADIANS(DoubleNum) FROM BQT1.SmallA ORDER BY DoubleNum; > 2. SELECT RADIANS(FloatNum) FROM BQT1.SmallA ORDER BY FloatNum; > Both queries return different null ordering. In case of DoubleNum nulls are first. In the second case nulls are last records. -- 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)

[ https://issues.jboss.org/browse/TEIID-3385?page=com.atlassian.jira.plugin... ] Juraj Duráni edited comment on TEIID-3385 at 3/18/15 3:09 AM: -------------------------------------------------------------- Comment removed - misunderstanding. was (Author: jdurani): Yes I know that column label should be used. But I expect if I use AS clause to rename column in the result then ResultSetMetaData should return column's label that was declared in AS clause not original name of the column. ResultSet rs = connection.prepareStatement("SELECT IntKey AS a FROM mytable").executeQuery(); ResultSetMetaData md = rs.getMetaData(); String name = md.getColumnName(1); Now the variable 'name' contains "IntKey", but I think that it should contain "a". > 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-3386) Mixed resutl with (double) full outer join and where clause

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3386?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3386: -------------------------------- Attachment: server.log Server log in the attachment. > 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 > Attachments: server.log > > > 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 Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3385?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3385: ------------------------------------- Yes I know that column label should be used. But I expect if I use AS clause to rename column in the result then ResultSetMetaData should return column's label that was declared in AS clause not original name of the column. ResultSet rs = connection.prepareStatement("SELECT IntKey AS a FROM mytable").executeQuery(); ResultSetMetaData md = rs.getMetaData(); String name = md.getColumnName(1); Now the variable 'name' contains "IntKey", but I think that it should contain "a". > 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-3387) MongoDB resource adapter doesn't support all authentication mechanisms

by Burak Serdar (JIRA)

[ https://issues.jboss.org/browse/TEIID-3387?page=com.atlassian.jira.plugin... ] Burak Serdar commented on TEIID-3387: ------------------------------------- MongoDB authentication doc: http://docs.mongodb.org/manual/core/authentication/ Code in lightblue-mongo that implements these options: https://github.com/lightblue-platform/lightblue-mongo/blob/master/config/... > MongoDB resource adapter doesn't support all authentication mechanisms > ---------------------------------------------------------------------- > > Key: TEIID-3387 > URL: https://issues.jboss.org/browse/TEIID-3387 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > 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 Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3387?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3387: -------------------------------- Issue Type: Enhancement (was: Bug) Any supporting links? > MongoDB resource adapter doesn't support all authentication mechanisms > ---------------------------------------------------------------------- > > Key: TEIID-3387 > URL: https://issues.jboss.org/browse/TEIID-3387 > Project: Teiid > Issue Type: Enhancement > 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 Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3387?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3387: -------------------------------- Component/s: Misc. Connectors > MongoDB resource adapter doesn't support all authentication mechanisms > ---------------------------------------------------------------------- > > Key: TEIID-3387 > URL: https://issues.jboss.org/browse/TEIID-3387 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015