June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3532) Infinispan-dsl-cache translator: Exception is thrown when order by clause is used

by Filip Elias (JIRA)

[ https://issues.jboss.org/browse/TEIID-3532?page=com.atlassian.jira.plugin... ] Filip Elias updated TEIID-3532: ------------------------------- Attachment: server.log > Infinispan-dsl-cache translator: Exception is thrown when order by clause is used > --------------------------------------------------------------------------------- > > Key: TEIID-3532 > URL: https://issues.jboss.org/browse/TEIID-3532 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Filip Elias > Assignee: Steven Hawkins > Attachments: server.log > > > Infinispan-dsl-cache translator will fail if order by clause is pushed down. > Sample query: > {code} > select intKey from smalla where intkey > 1 order by intKey > {code} > Exception: > {code} > Connector worker process failed for atomic-request=iLuNd1gO/2N0.4.0.7: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[38] returned server error (status=0x85): org.hibernate.hql.ParsingException: HQLPARSER000002: The query FROM org.jboss.qe.jdg_remote.protobuf.SmallA _gen0 WHERE _gen0.intKey > 1 ORDER BY _gen0.null ASC is not valid; Parser error messages: [[statement, statementElement, selectStatement, orderByClause, sortSpecification, sortKey, concatenation, additiveExpression, multiplyExpression, unaryExpression, atom, identPrimary]: line 1:89 mismatched token: [@32,89:92='null',<124>,1:89]; expecting type IDENTIFIER]. > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74) > {code} > Full log is in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3532) Infinispan-dsl-cache translator: Exception is thrown when order by clause is used

by Filip Elias (JIRA)

Filip Elias created TEIID-3532: ---------------------------------- Summary: Infinispan-dsl-cache translator: Exception is thrown when order by clause is used Key: TEIID-3532 URL: https://issues.jboss.org/browse/TEIID-3532 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.7.1.6_2 Reporter: Filip Elias Assignee: Steven Hawkins Attachments: server.log Infinispan-dsl-cache translator will fail if order by clause is pushed down. Sample query: {code} select intKey from smalla where intkey > 1 order by intKey {code} Exception: {code} Connector worker process failed for atomic-request=iLuNd1gO/2N0.4.0.7: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[38] returned server error (status=0x85): org.hibernate.hql.ParsingException: HQLPARSER000002: The query FROM org.jboss.qe.jdg_remote.protobuf.SmallA _gen0 WHERE _gen0.intKey > 1 ORDER BY _gen0.null ASC is not valid; Parser error messages: [[statement, statementElement, selectStatement, orderByClause, sortSpecification, sortKey, concatenation, additiveExpression, multiplyExpression, unaryExpression, atom, identPrimary]: line 1:89 mismatched token: [@32,89:92='null',<124>,1:89]; expecting type IDENTIFIER]. at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298) at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88) at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74) {code} Full log is in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3524) Database Logging not working

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3524: ------------------------------------ This should work, if no we may need check the server.log check whether JPA insert have exeception throw? Also for Reporter, can you check whether JPA batch insert be enabled, if so can you dump more log than JPA batch size, then check whether it work? > Database Logging not working > ---------------------------- > > Key: TEIID-3524 > URL: https://issues.jboss.org/browse/TEIID-3524 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Van Halbert > > When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db. > I set up the logging as follows: > Created java:/teiid-log-ds datasource. > Added these to logging subsystem: > {code:xml} > <async-handler name="TEIID_COMMAND_LOG"> > <level name="DEBUG"/> > <queue-length value="50"/> > <overflow-action value="block"/> > <subhandlers> > <handler name="TEIID_JPA_LOG"/> > </subhandlers> > </async-handler> > <async-handler name="TEIID_AUDIT_LOG"> > <level name="DEBUG"/> > <queue-length value="50"/> > <overflow-action value="block"/> > <subhandlers> > <handler name="TEIID_JPA_LOG"/> > </subhandlers> > </async-handler> > <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions"> > <level name="DEBUG"/> > </custom-handler> > <logger category="org.teiid.COMMAND_LOG"> > <level name="DEBUG"/> > <handlers> > <handler name="TEIID_COMMAND_LOG"/> > </handlers> > </logger> > <logger category="org.teiid.AUDIT_LOG"> > <level name="DEBUG"/> > <handlers> > <handler name="TEIID_AUDIT_LOG"/> > </handlers> > </logger> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3531) Better planning of bushy join trees

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3531: ------------------------------------- Summary: Better planning of bushy join trees Key: TEIID-3531 URL: https://issues.jboss.org/browse/TEIID-3531 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 The primary join planning logic considers left linear trees. We also have a hint to preserve structure and some planning that reuses existing subtrees, but nothing general around considering bushy trees. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3530) dependent join enhancements

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3530: ------------------------------------- Summary: dependent join enhancements Key: TEIID-3530 URL: https://issues.jboss.org/browse/TEIID-3530 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 We need to address several aspects of dependent joins: - allow for translators to control if bind variables will be used (oracle should not) - remove the dependentJoinPushdownThreshold option and allow the planner to fully push the join based upon the plan - have rule choose dependent make a better determination of when to use a temp table vs. in predicates. -- 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 Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3527?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3527. ----------------------------------- Fix Version/s: 8.11 Resolution: Done Updated this and a spelling mistake in another transport message. > 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 > Fix For: 8.11 > > > 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-3529) Add pushdown support for regexp_replace

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3529: ------------------------------------- Summary: Add pushdown support for regexp_replace Key: TEIID-3529 URL: https://issues.jboss.org/browse/TEIID-3529 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 At least for sources with similar regex and flags support, we should offer pushdown support. This may require additional support methods to determine if the pattern is acceptable. -- 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 Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3528?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3528. ----------------------------------- Fix Version/s: 8.11 Resolution: Done This is also related to TEIID-3437, the batch handling for sources returning a single update count value (accumulo, simpledb, loopback, and solr) will effectively return infinite results without the fix. > 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 > Fix For: 8.11 > > 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-3437) Inconsistencies with row count handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3437?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3437 at 6/15/15 8:51 AM: ---------------------------------------------------------------- Note this introduced a regressions TEIID-3523 and TEIID-3528 into 8.10.1 was (Author: shawkins): Note this introduced a regression TEIID-3523 into 8.10.1 > Inconsistencies with row count handling > --------------------------------------- > > Key: TEIID-3437 > URL: https://issues.jboss.org/browse/TEIID-3437 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors, Query Engine > Affects Versions: 8.10 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10.1, 8.11, 8.7.3 > > > With TEIID-3271 we addressed returning all of the update counts from a bulk operation such that the direct JDBC logic was correct. However this left the logic inconsistent with the projectintonode (which could result in invalid rowcount variables) and with the accumulo, solr, and simpledb translators. -- 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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3528?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3528: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1231769 > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015