March 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5685) Allow for binding non-ascii strings as varchar

by Johnathon Lee (Jira)

[ https://issues.jboss.org/browse/TEIID-5685?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5685: --------------------------------- Fix Version/s: 8.12.18.6_4 > Allow for binding non-ascii strings as varchar > ---------------------------------------------- > > Key: TEIID-5685 > URL: https://issues.jboss.org/browse/TEIID-5685 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 8.12.18.6_4 > > > Related to TEIID-5587, even newer oracle drivers that do support NVARCHAR will throw an exception when the number of bytes in an NVARCHAR string exceeds 4000. > In situations, such as insert, where the underlying native type can be detected, we can simply bind as VARCHAR if it's not a multi-byte type - and log that the string will have replacement characters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.3 Client jars

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/TEIID-5667?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5667: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1664293|https://bugzilla.redhat.com/show_bug.cgi?id=1664293] from MODIFIED to ASSIGNED > Update Infinispan Connector modules to support Infinispan 7.3 Client jars > ------------------------------------------------------------------------- > > Key: TEIID-5667 > URL: https://issues.jboss.org/browse/TEIID-5667 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.17.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The Infinispan connector needs the module updated to support the Infinispan 7.3 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.3 Client jars

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/TEIID-5667?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5667: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1664293|https://bugzilla.redhat.com/show_bug.cgi?id=1664293] from ASSIGNED to MODIFIED > Update Infinispan Connector modules to support Infinispan 7.3 Client jars > ------------------------------------------------------------------------- > > Key: TEIID-5667 > URL: https://issues.jboss.org/browse/TEIID-5667 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.17.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The Infinispan connector needs the module updated to support the Infinispan 7.3 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.3 Client jars

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/TEIID-5667?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5667: ------------------------------------------------ Andrej Smigala <asmigala(a)redhat.com> changed the Status of [bug 1664293|https://bugzilla.redhat.com/show_bug.cgi?id=1664293] from ON_QA to ASSIGNED > Update Infinispan Connector modules to support Infinispan 7.3 Client jars > ------------------------------------------------------------------------- > > Key: TEIID-5667 > URL: https://issues.jboss.org/browse/TEIID-5667 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.17.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The Infinispan connector needs the module updated to support the Infinispan 7.3 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5691) Odata cross join with sibling expand will typically error

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5691?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5691. ----------------------------------- Resolution: Done Corrected the type passed into the siblings. > Odata cross join with sibling expand will typically error > --------------------------------------------------------- > > Key: TEIID-5691 > URL: https://issues.jboss.org/browse/TEIID-5691 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > Something like: > {code} > /northwind/m/$crossjoin(x,z)?$expand=z > {code} > will typically error because the entity type for x is being set for z - and usage of that in the serializer will throw an exception that z does not extend x. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5686) NPE in MergeJoinStrategy when using joins with a particular limit value

by dalex dalex (Jira)

[ https://issues.jboss.org/browse/TEIID-5686?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5686: ------------------------------------ [~shawkins] thx a lot for the quick fix, I checked these changes locally, it worked! > NPE in MergeJoinStrategy when using joins with a particular limit value > ----------------------------------------------------------------------- > > Key: TEIID-5686 > URL: https://issues.jboss.org/browse/TEIID-5686 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 12.0 > Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > When running the following query (IMPORTANT: you shouldn't use row limit): > {code:sql} > begin > declare integer i=0; > while (i < 2) > begin > select * > from "test_tables_pg.test_a" t0 > JOIN "test_tables_pg.test_e" t1 > ON true > JOIN "test_tables_pg.test_e" t2 > ON true > JOIN views.v t3 > on true > JOIN views.v t4 > on true > limit 257 ; > i=i+1; > end > end ;; > {code} > teiid throws out the following NPE: > {code:noformat} > 2019-03-13 13:50:28,582 ERROR [org.teiid.PROCESSOR] (Worker4_QueryProcessorQueue233) InwGU8fhfbja TEIID30019 Unexpected exception for request InwGU8fhfbja.22: java.lang.NullPointerEx > ception > at org.teiid.query.processor.relational.MergeJoinStrategy.compareToPrevious(MergeJoinStrategy.java:284) > at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:238) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirectInternal(JoinNode.java:260) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:195) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:98) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) > at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:65) > at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:66) > at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:80) > at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:44) > at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:303) > at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:269) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:492) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:362) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:285) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:113) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:199) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5691) Odata cross join with sibling expand will typically error

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5691: ------------------------------------- Summary: Odata cross join with sibling expand will typically error Key: TEIID-5691 URL: https://issues.jboss.org/browse/TEIID-5691 Project: Teiid Issue Type: Bug Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 Something like: {code} /northwind/m/$crossjoin(x,z)?$expand=z {code} will typically error because the entity type for x is being set for z - and usage of that in the serializer will throw an exception that z does not extend x. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5668) Wrong results on left join + aggregation

by Johnathon Lee (Jira)

[ https://issues.jboss.org/browse/TEIID-5668?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5668: --------------------------------- Fix Version/s: 8.12.18.6_4 > Wrong results on left join + aggregation > ---------------------------------------- > > Key: TEIID-5668 > URL: https://issues.jboss.org/browse/TEIID-5668 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 12.0 > Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 12.0.1, 12.1, 11.2.3, 8.12.18.6_4 > > Attachments: wrong_count_results_1.jpg, wrong_count_results_2.jpg > > > When using a query with a left join between tables from different schemes and count it produces wrong results. The workflow for reproducing the bug contains two example queries. The only difference between these queries is the order of the counts in select clause. The first query returns wrong results (the output of the "count(b.SalesPersonID)" field). > Additional info: a) the wrong count results are the distinct values b) occurs also with other aggregations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5500) Improve OData performance

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5500?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5500: ------------------------------------- I believe ultimately the page size is a preference if there is a way if we want to limit to a high water mark that should be OK imo per spec. > Improve OData performance > ------------------------- > > Key: TEIID-5500 > URL: https://issues.jboss.org/browse/TEIID-5500 > Project: Teiid > Issue Type: Enhancement > Components: OData, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > See https://developer.jboss.org/thread/277783 > There is a significant overhead for OData vs. JDBC for a single client especially in terms of latency. > We should investigate pre-building additional batch results and entity caching in general. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5500) Improve OData performance

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5500?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5500: --------------------------------------- > But having the "chunked" response is the key thing here for managing the client side of the equation, which I did not consider before. The concern is still over the requested page size. As long as it's "small" it makes little difference whether we build an entity set 256 at a time or iteratively. The chunking is a lower level resultset/caching concern. However if someone sets or requests a larger page size, then problems could arise - which we could just limit the page size or implement this streaming style result. > Improve OData performance > ------------------------- > > Key: TEIID-5500 > URL: https://issues.jboss.org/browse/TEIID-5500 > Project: Teiid > Issue Type: Enhancement > Components: OData, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > See https://developer.jboss.org/thread/277783 > There is a significant overhead for OData vs. JDBC for a single client especially in terms of latency. > We should investigate pre-building additional batch results and entity caching in general. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2019