June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3528) Solr translator - batched update with more than one query gets stack

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3528?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3528: -------------------------------- Description: PreparedStatement.executeBatch() with more than one query gets stack (but data are stored in Solr). For more details see server.log. However batch of size 1 and Statement.executeBatch() run without problems. The issue is not present in 6.1.1 version. was: PreparedStatement.executeBatch() with more than one query gets stack. For more details see server.log. However batch of size 1 and Statement.executeBatch() run without problems. The issue is not present in 6.1.1 version. > Solr translator - batched update with more than one query gets stack > -------------------------------------------------------------------- > > Key: TEIID-3528 > URL: https://issues.jboss.org/browse/TEIID-3528 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server.log > > > PreparedStatement.executeBatch() with more than one query gets stack (but data are stored in Solr). For more details see server.log. > However batch of size 1 and Statement.executeBatch() run without problems. > The issue is not present in 6.1.1 version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3528) Solr translator - batched update with more than one query gets stack

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3528?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3528: -------------------------------- Attachment: server.log Server log. Note: I canceled the query at ~13:11:43 [line ~5550] > Solr translator - batched update with more than one query gets stack > -------------------------------------------------------------------- > > Key: TEIID-3528 > URL: https://issues.jboss.org/browse/TEIID-3528 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server.log > > > PreparedStatement.executeBatch() with more than one query gets stack. For more details see server.log. > However batch of size 1 and Statement.executeBatch() run without problems. > The issue is not present in 6.1.1 version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3528) Solr translator - batched update with more than one query gets stack

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3528: ----------------------------------- Summary: Solr translator - batched update with more than one query gets stack Key: TEIID-3528 URL: https://issues.jboss.org/browse/TEIID-3528 Project: Teiid Issue Type: Bug Affects Versions: 8.7.3 Reporter: Juraj Duráni Assignee: Steven Hawkins PreparedStatement.executeBatch() with more than one query gets stack. For more details see server.log. However batch of size 1 and Statement.executeBatch() run without problems. The issue is not present in 6.1.1 version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3527) Missing ODBC port number in the log during shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3527?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3527: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1231613 > Missing ODBC port number in the log during shutdown > --------------------------------------------------- > > Key: TEIID-3527 > URL: https://issues.jboss.org/browse/TEIID-3527 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Trivial > > There is missing ODBC port number in the log during shutdown: > INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50039 Teiid JDBC - Name = jdbc, Host = localhost, Port = 31000 has been shutdown. > INFO [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID50040 Teiid ODBC - Name = localhost, Host = 35432, Port = {2} has been shutdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3527) Missing ODBC port number in the log during shutdown

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3527: ----------------------------------- Summary: Missing ODBC port number in the log during shutdown Key: TEIID-3527 URL: https://issues.jboss.org/browse/TEIID-3527 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1.6_2 Reporter: Juraj Duráni Assignee: Steven Hawkins Priority: Trivial There is missing ODBC port number in the log during shutdown: INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50039 Teiid JDBC - Name = jdbc, Host = localhost, Port = 31000 has been shutdown. INFO [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID50040 Teiid ODBC - Name = localhost, Host = 35432, Port = {2} has been shutdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3526) SQL Server does not support insert with query expression and a common table expression

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3526: ------------------------------------- Summary: SQL Server does not support insert with query expression and a common table expression Key: TEIID-3526 URL: https://issues.jboss.org/browse/TEIID-3526 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 SQL Server will not support a source query of the form: insert into tbl with ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3525) dependent join handling of multi-way joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3525?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3525. ----------------------------------- Resolution: Done Updated the handling in cases without access patterns to detect when duplicate columns are being used and to ensure that only 1 will be utilized. > dependent join handling of multi-way joins > ------------------------------------------ > > Key: TEIID-3525 > URL: https://issues.jboss.org/browse/TEIID-3525 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > In scenarios where the same column is used multiple times in a multi-way dependent join, it's affect may be duplicated in source predicates. > For example: > select pm1.g1.e1, pm1.g1.e2, pm2.g1.e2 FROM pm1.g2, pm1.g1, /*+ makedep */ pm2.g1 where pm1.g1.e1 = pm2.g1.e1 and pm1.g2.e1 = pm2.g1.e1 > Should have a source query of the form: > SELECT g_0.e1 AS c_0, g_0.e2 AS c_1 FROM pm2.g1 AS g_0 WHERE g_0.e1 IN (<dependent values>) ORDER BY c_0 > Rather than having multiple dependent values predicates. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3511: --------------------------------------- I haven't made too much progress yet on fully recreating this scenario. Any possiblity of providing post execution query plans showing row counts and/or executing with fewer joins? It does appear that the bad plan is affected by TEIID-3525 which has been addressed for 8.12. That may not be the cause of the issue, but it is a minor simplification. If needed we can also get that into 8.11.1. > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan_bitand.txt, debugplan_bitand_correct.txt, debugplan_nobitand.txt, debugplan_nobitand_correct.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3525) dependent join handling of multi-way joins

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3525: ------------------------------------- Summary: dependent join handling of multi-way joins Key: TEIID-3525 URL: https://issues.jboss.org/browse/TEIID-3525 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 In scenarios where the same column is used multiple times in a multi-way dependent join, it's affect may be duplicated in source predicates. For example: select pm1.g1.e1, pm1.g1.e2, pm2.g1.e2 FROM pm1.g2, pm1.g1, /*+ makedep */ pm2.g1 where pm1.g1.e1 = pm2.g1.e1 and pm1.g2.e1 = pm2.g1.e1 Should have a source query of the form: SELECT g_0.e1 AS c_0, g_0.e2 AS c_1 FROM pm2.g1 AS g_0 WHERE g_0.e1 IN (<dependent values>) ORDER BY c_0 Rather than having multiple dependent values predicates. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3513) make saxon dependency optional for embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3513?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3513: --------------------------------------- After some cursory investigation, this will be more difficult than I had anticipated. It would be nice to have the saxon/xom/nux dependencies as optional - but logic from them is used through out our xml processing - document models, system functions, xmltable, etc. in both static and non-static ways. Just isolating will be a good sized effort. To get to the point where there are intelligible error messages would be a major undertaking, so lowering the priority. > make saxon dependency optional for embedded > ------------------------------------------- > > Key: TEIID-3513 > URL: https://issues.jboss.org/browse/TEIID-3513 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12 > > > To further modularize embedded saxon should be an optional dependency. Currently the ties into the object model and validation are not isolated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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