February 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3279) SOLR: Error when date, time or timestamp literal is in where clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3279?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3279: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1180107|https://bugzilla.redhat.com/show_bug.cgi?id=1180107] from VERIFIED to CLOSED > SOLR: Error when date,time or timestamp literal is in where clause > ------------------------------------------------------------------ > > Key: TEIID-3279 > URL: https://issues.jboss.org/browse/TEIID-3279 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Fix For: 8.7.1.6_2, 8.11 > > > Query fails when time,date or timestamp literal is used in where clause. > Examples: > Query: > {code}select intkey from smalla where timevalue = '11:30:20'{code} > Error: > {code} > '11:30:20'org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20' > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491) > {code} > Query: > {code}select intkey from smalla where datevalue = '2002-02-02'{code} > Error: > {code} > org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20' > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491) > {code} > Query: > {code}select intkey from smalla where timestampvalue = '2000-01-01 00:00:04'{code} > Error: > {code} org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'2000-01-01T00-00-04' > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491) > {code} > SOLR supports only timestamps (YYYY-mm-ddThh:mm:ssZ) so date and time types should be converted into timestamp before a query is send to SOLR. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3274) Change archetypes to create independent projects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3274?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3274: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1178658|https://bugzilla.redhat.com/show_bug.cgi?id=1178658] from VERIFIED to CLOSED > Change archetypes to create independent projects > ------------------------------------------------ > > Key: TEIID-3274 > URL: https://issues.jboss.org/browse/TEIID-3274 > Project: Teiid > Issue Type: Enhancement > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > > The current archetypes were developed with the mindset of generating projects that are part of the Teiid build. However, they need to be changed so that they are generating projects that are independent, that can stand on their own without requiring Teiid jar's. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2736) MongoDB: failed to translate to mongo query with boolean value expression

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2736?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2736: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1033077|https://bugzilla.redhat.com/show_bug.cgi?id=1033077] from VERIFIED to CLOSED > MongoDB: failed to translate to mongo query with boolean value expression > -------------------------------------------------------------------------- > > Key: TEIID-2736 > URL: https://issues.jboss.org/browse/TEIID-2736 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: Teiid 8.6 beta with mongoDB > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Beta2, teiid > Fix For: 8.4.1, 8.6 > > > Fail to translate the following SQL to mongo query: > select "grade", > "name", > "score", > "state", > "grade" as "test", > ("name" = "state") as "name2" > from "mongoDBDS"."grades" > where "grade" = 'B' > However, it works with the query contains group by and boolean value expression: > elect "grade" as "test", > "grade", > ("name" = "state") as "name2", > sum("score") as "sum_score" > from "mongoDBDS"."grades" > where "grade" = 'B' > group by "grade", "grade", ("name" = "state") > order by "grade", "test", "name2" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2992) MongoDB: Offset clause causes MongoDB to crash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2992?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2992: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1105473|https://bugzilla.redhat.com/show_bug.cgi?id=1105473] from VERIFIED to CLOSED > MongoDB: Offset clause causes MongoDB to crash > ---------------------------------------------- > > Key: TEIID-2992 > URL: https://issues.jboss.org/browse/TEIID-2992 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Environment: MongoDB < 2.5.2 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.8, 8.7.1 > > > MongoDB(version < 2.5.2) will crash when offset clause is used in SQL query. > Althought the bug[1] is in MongoDB (Adding big number into $limit causes Mongodb to shutdown), it is also caused by teiid because it adds max integer into $limit which seems to be unnecessary. > Sample query: > {code} > SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS > {code} > Generated mongo command: > {code} > { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY" } }, { $sort: { c_0: 1 } }, { $skip: 45 }, { $limit: 2147483647 } ] } > {code} > [1] https://jira.mongodb.org/browse/SERVER-10136 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3592: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1247651|https://bugzilla.redhat.com/show_bug.cgi?id=1247651] from VERIFIED to CLOSED > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2, 8.7.2.6_2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3240) Tranlator archetype creation: -Dversion option sets the version of parent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3240?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3240: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1170588|https://bugzilla.redhat.com/show_bug.cgi?id=1170588] from VERIFIED to CLOSED > Tranlator archetype creation: -Dversion option sets the version of parent > ------------------------------------------------------------------------- > > Key: TEIID-3240 > URL: https://issues.jboss.org/browse/TEIID-3240 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Van Halbert > > If new translator is created using command line, -Dversion option is set as version of parent project instead of version of actual translator. > pom file: > <parent> > <groupId>org.jboss.teiid</groupId> > <artifactId>connectors</artifactId> > <version>0.0.1</version> > </parent> > ... > <groupId>org.jboss.teiid.test.translator</groupId> > <artifactId>test-translator</artifactId> >  > <packaging>jar</packaging> > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2936) Combining multiple 'in' criteria can prevent pushing criteria to database

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2936?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2936: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1243875|https://bugzilla.redhat.com/show_bug.cgi?id=1243875] from VERIFIED to CLOSED > Combining multiple 'in' criteria can prevent pushing criteria to database > ------------------------------------------------------------------------- > > Key: TEIID-2936 > URL: https://issues.jboss.org/browse/TEIID-2936 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.7 > Reporter: Mike Higgins > Assignee: Steven Hawkins > Fix For: 8.8, 8.7.2.6_2 > > > When two 'in' criteria containing constant values on the same field are combined with an 'or', Teiid will combine the two into a single 'in' operation. > Since Oracle (for example) has a 1000 item limit on the 'in' values, if the resulting combined list contains more than 1000 values, it can no longer be pushed down into Oracle for execution. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2976: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1154655|https://bugzilla.redhat.com/show_bug.cgi?id=1154655] from VERIFIED to CLOSED > Using new database logging extension, getting error that indicates column isn't long enough > ------------------------------------------------------------------------------------------- > > Key: TEIID-2976 > URL: https://issues.jboss.org/browse/TEIID-2976 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1 > > > Getting the following sporadically: > 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement: > insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3219) Excel Translator Wrong Result From Columns With Interleaved Null Values

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3219: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1164281|https://bugzilla.redhat.com/show_bug.cgi?id=1164281] from VERIFIED to CLOSED > Excel Translator Wrong Result From Columns With Interleaved Null Values > ----------------------------------------------------------------------- > > Key: TEIID-3219 > URL: https://issues.jboss.org/browse/TEIID-3219 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Kylin Soong > Fix For: 8.7.1, 8.10 > > Attachments: artifacts.zip > > > When querying a column which has a null value somewhere in it, the result set is missing all the rows under the null value in the xlsx file. When querying more columns, the result set is missing some values only if there is a row, where both columns contains null value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2890) IndexOutOfBoundsException when using GROUP BY

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2890?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2890: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1167875|https://bugzilla.redhat.com/show_bug.cgi?id=1167875] from VERIFIED to CLOSED > IndexOutOfBoundsException when using GROUP BY > --------------------------------------------- > > Key: TEIID-2890 > URL: https://issues.jboss.org/browse/TEIID-2890 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: 8.7, grouping, translator > Fix For: 8.7 > > > I have a translator that does not support aggregates or grouping. I am using a view to try to normalize data from several sources. I am duplicating some of the fields as an approximation. I have existing software that is querying with GROUP BY, and sometimes this happens. > This query works fine in 8.6: > {code:sql} > select identifier > from foo.items > group by identifier, identifier; > {code} > In 8.7 this happens: > {code} > 10:15:24,280 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue39) njknuxobPkVY TEIID30019 Unexpected exception for request njknuxobPkVY.3: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) [rt.jar:1.7.0_02] > at java.util.ArrayList.get(ArrayList.java:382) [rt.jar:1.7.0_02] > at org.teiid.query.processor.relational.MergeJoinStrategy.compareTuples(MergeJoinStrategy.java:313) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.sameGroup(GroupingNode.java:488) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:414) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:336) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:273) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 February 2016