March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3390) Improve SQL/XML generation performance and limit disk usage

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3390?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3390: --------------------------------------- Similar changes will be needed for JSON as well. > Improve SQL/XML generation performance and limit disk usage > ----------------------------------------------------------- > > Key: TEIID-3390 > URL: https://issues.jboss.org/browse/TEIID-3390 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Deeply nested large xml documents generated by SQL/XML can create a lot of temporary disk backed objects. These objects can have slow cleanup based upon when their references get cleared. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3390) Improve SQL/XML generation performance and limit disk usage

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3390?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3390: ------------------------------------- Would this also include the enhancements you mentioned about the context passing around between SQL/XML constructs? > Improve SQL/XML generation performance and limit disk usage > ----------------------------------------------------------- > > Key: TEIID-3390 > URL: https://issues.jboss.org/browse/TEIID-3390 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Deeply nested large xml documents generated by SQL/XML can create a lot of temporary disk backed objects. These objects can have slow cleanup based upon when their references get cleared. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3391) Double value is truncated in Where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3391?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3391: --------------------------------------- Teiid would not truncate unless the modeled type for the column is actually a float. How did you obtain the metadata and are you sure that the modeled type is a double? > Double value is truncated in Where clause > ----------------------------------------- > > Key: TEIID-3391 > URL: https://issues.jboss.org/browse/TEIID-3391 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Blocker > > I'm using Teiid 8.10.0 Final over H2 Database. > I have an H2 table containing a field of Type Double. > When i add a where condition over this field with a double value, this value is truncated by Teiid and the query returns no records. > You find below the query executed with Teiid and the execution plan: > select "Locations"."Sheet0_EPr_090315_Lat" as "LAT_MapCalculatedField","Locations"."Sheet0_EPr_090315_Long" as "LNG_MapCalculatedField","Locations"."Sheet0_EPr_090315_SDView_INC" as "Locations_Sheet0_EPr_090315_1",COUNT( distinct "IM123View"."SDView_INCIDENTSM1_INCIDENT_") as "IM123View_SDView_INCIDENTSM1" from "implifyBusinessModel"."IM123View" "IM123View" LEFT JOIN "implifyBusinessModel"."Locations" "Locations" ON "IM123View"."SDView_INCIDENTSM1_LOCATION_" = "Locations"."Sheet0_EPr_090315_SDView_INC" > where ("Locations"."Sheet0_EPr_090315_Lat" IN (31.953582763671875) ) group by "Locations"."Sheet0_EPr_090315_Lat","Locations"."Sheet0_EPr_090315_Long","Locations"."Sheet0_EPr_090315_SDView_INC" > -----Teiid Show Plan ---- > <?xml version='1.0' encoding='UTF-8'?><node name="AccessNode"><property name="Relational Node ID"><value>1</value></property><property name="Output Columns"><value>LAT_MapCalculatedField (float)</value><value>LNG_MapCalculatedField (float)</value><value>Locations_Sheet0_EPr_090315_1 (string)</value><value>IM123View_SDView_INCIDENTSM1 (integer)</value></property><property name="Statistics"><value>Node Output Rows: 0</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 0</value><value>Node Cumulative Process Time: 16</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value> > SELECT g_1.Sheet0_EPr_090315_Lat, g_1.Sheet0_EPr_090315_Long, g_1.Sheet0_EPr_090315_SDView_INC, COUNT(DISTINCT g_0.SDView_INCIDENTSM1_INCIDENT_) > FROM implify_viewModel.implify_view.IM123View AS g_0, implify_viewModel.implify_view.Locations AS g_1 WHERE (g_0.SDView_INCIDENTSM1_LOCATION_ = g_1.Sheet0_EPr_090315_SDView_INC) AND (g_1.Sheet0_EPr_090315_Lat = 31.953583) GROUP BY g_1.Sheet0_EPr_090315_Lat, g_1.Sheet0_EPr_090315_Long, g_1.Sheet0_EPr_090315_SDView_INC</value></property><property name="Model Name"><value>implify_viewModel</value></property><property name="Data Bytes Sent"><value>0</value></property></node> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3391) Double value is truncated in Where clause

by Mark Tawk (JIRA)

Mark Tawk created TEIID-3391: -------------------------------- Summary: Double value is truncated in Where clause Key: TEIID-3391 URL: https://issues.jboss.org/browse/TEIID-3391 Project: Teiid Issue Type: Feature Request Reporter: Mark Tawk Assignee: Steven Hawkins Priority: Blocker I'm using Teiid 8.10.0 Final over H2 Database. I have an H2 table containing a field of Type Double. When i add a where condition over this field with a double value, this value is truncated by Teiid and the query returns no records. You find below the query executed with Teiid and the execution plan: select "Locations"."Sheet0_EPr_090315_Lat" as "LAT_MapCalculatedField","Locations"."Sheet0_EPr_090315_Long" as "LNG_MapCalculatedField","Locations"."Sheet0_EPr_090315_SDView_INC" as "Locations_Sheet0_EPr_090315_1",COUNT( distinct "IM123View"."SDView_INCIDENTSM1_INCIDENT_") as "IM123View_SDView_INCIDENTSM1" from "implifyBusinessModel"."IM123View" "IM123View" LEFT JOIN "implifyBusinessModel"."Locations" "Locations" ON "IM123View"."SDView_INCIDENTSM1_LOCATION_" = "Locations"."Sheet0_EPr_090315_SDView_INC" where ("Locations"."Sheet0_EPr_090315_Lat" IN (31.953582763671875) ) group by "Locations"."Sheet0_EPr_090315_Lat","Locations"."Sheet0_EPr_090315_Long","Locations"."Sheet0_EPr_090315_SDView_INC" -----Teiid Show Plan ---- <?xml version='1.0' encoding='UTF-8'?><node name="AccessNode"><property name="Relational Node ID"><value>1</value></property><property name="Output Columns"><value>LAT_MapCalculatedField (float)</value><value>LNG_MapCalculatedField (float)</value><value>Locations_Sheet0_EPr_090315_1 (string)</value><value>IM123View_SDView_INCIDENTSM1 (integer)</value></property><property name="Statistics"><value>Node Output Rows: 0</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 0</value><value>Node Cumulative Process Time: 16</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value> SELECT g_1.Sheet0_EPr_090315_Lat, g_1.Sheet0_EPr_090315_Long, g_1.Sheet0_EPr_090315_SDView_INC, COUNT(DISTINCT g_0.SDView_INCIDENTSM1_INCIDENT_) FROM implify_viewModel.implify_view.IM123View AS g_0, implify_viewModel.implify_view.Locations AS g_1 WHERE (g_0.SDView_INCIDENTSM1_LOCATION_ = g_1.Sheet0_EPr_090315_SDView_INC) AND (g_1.Sheet0_EPr_090315_Lat = 31.953583) GROUP BY g_1.Sheet0_EPr_090315_Lat, g_1.Sheet0_EPr_090315_Long, g_1.Sheet0_EPr_090315_SDView_INC</value></property><property name="Model Name"><value>implify_viewModel</value></property><property name="Data Bytes Sent"><value>0</value></property></node> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3390) Improve SQL/XML generation performance and limit disk usage

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3390: ------------------------------------- Summary: Improve SQL/XML generation performance and limit disk usage Key: TEIID-3390 URL: https://issues.jboss.org/browse/TEIID-3390 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 Deeply nested large xml documents generated by SQL/XML can create a lot of temporary disk backed objects. These objects can have slow cleanup based upon when their references get cleared. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3389) Teiid JDBC Driver does not participate in Kerberos delegation

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3389?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3389: -------------------------------- Attachment: DelegationJDBCClient.java client.conf > Teiid JDBC Driver does not participate in Kerberos delegation > ------------------------------------------------------------- > > Key: TEIID-3389 > URL: https://issues.jboss.org/browse/TEIID-3389 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.11 > > Attachments: client.conf, DelegationJDBCClient.java > > > The current JDBC driver can negotiate a static kerberos based connection, but it currently does not have capability participate in kerberos delegation scenarios. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3389) Teiid JDBC Driver does not participate in Kerberos delegation

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3389?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3389. --------------------------------- Resolution: Done Added code to MakeGss.java, where it can utilize Subject when connection is made using {code} Subject.doAS(subject, new Action(){ // get Teiid Connection. }); {code} then it will detect the subject in the context, and will try to use the delegated credential for negotiating with server. > Teiid JDBC Driver does not participate in Kerberos delegation > ------------------------------------------------------------- > > Key: TEIID-3389 > URL: https://issues.jboss.org/browse/TEIID-3389 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.11 > > > The current JDBC driver can negotiate a static kerberos based connection, but it currently does not have capability participate in kerberos delegation scenarios. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3389) Teiid JDBC Driver does not participate in Kerberos delegation

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3389: ----------------------------------- Summary: Teiid JDBC Driver does not participate in Kerberos delegation Key: TEIID-3389 URL: https://issues.jboss.org/browse/TEIID-3389 Project: Teiid Issue Type: Enhancement Components: JDBC Driver Affects Versions: 8.7 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.11 The current JDBC driver can negotiate a static kerberos based connection, but it currently does not have capability participate in kerberos delegation scenarios. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

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 an oracle bug. Our source query: SELECT g_1.INTKEY AS c_0, g_2.INTKEY AS c_1, g_0.INTKEY AS c_2 FROM LargeB g_0 LEFT OUTER JOIN (SmallA g_1 FULL OUTER JOIN MediumB g_2 ON g_1.INTKEY = g_2.INTKEY) ON g_2.INTKEY = g_0.INTKEY WHERE g_0.INTKEY < 1500 ORDER BY c_2, c_1, c_0 Will produce the correct results against a different database, such as SQL Server. The same is true even if we preserve the full outer join: SELECT g_1.INTKEY AS c_0, g_2.INTKEY AS c_1, g_0.INTKEY AS c_2 FROM LargeB g_0 FULL OUTER JOIN (SmallA g_1 FULL OUTER JOIN MediumB g_2 ON g_1.INTKEY = g_2.INTKEY) ON g_2.INTKEY = g_0.INTKEY WHERE g_0.INTKEY < 1500 ORDER BY c_2, c_1, c_0 Reversing the full outer join, does produce the correct results against Oracle 10: SELECT g_1.INTKEY AS c_0, g_2.INTKEY AS c_1, g_0.INTKEY AS c_2 FROM (SmallA g_1 FULL OUTER JOIN MediumB g_2 ON g_1.INTKEY = g_2.INTKEY) FULL OUTER JOIN LargeB g_0 ON g_2.INTKEY = g_0.INTKEY WHERE g_0.INTKEY < 1500 ORDER BY c_2, c_1, c_0 So that's obviously a bug as the results from a full outer join should be the same either way. I'm not finding good information on how to categorize this type of oracle bug other than seeing that there are a lot of known issues even through Oracle 10 with full outer joins. And this has been fixed in Oracle 11. So I'm not sure what we should do to resolve this at the moment. > 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)

9 years, 9 months

1
0
0 / 0

[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)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015