January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator

by Vijay K (JIRA)

[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ] Vijay K updated TEIID-4717: --------------------------- Description: At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} As a user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) References: https://www.datastax.com/dev/blog/allow-filtering-explained-2 https://developer.jboss.org/thread/239011 was: At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} As as user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) References: https://www.datastax.com/dev/blog/allow-filtering-explained-2 https://developer.jboss.org/thread/239011 > Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator > --------------------------------------------------------------- > > Key: TEIID-4717 > URL: https://issues.jboss.org/browse/TEIID-4717 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Vijay K > Labels: cassandra > Fix For: 9.3 > > > At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error > {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} > As a user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) > References: > https://www.datastax.com/dev/blog/allow-filtering-explained-2 > https://developer.jboss.org/thread/239011 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4709) Enable JDG resource adapter to pass the username/password to HotRod Client

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4709?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4709: ------------------------------------ After thinking about this, the pool option won't help when someone is using the Teiid Odata endpoint. > Enable JDG resource adapter to pass the username/password to HotRod Client > -------------------------------------------------------------------------- > > Key: TEIID-4709 > URL: https://issues.jboss.org/browse/TEIID-4709 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Affects Versions: 9.3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > Enable the JDG resource adapter to pass the username/password to the JDG hot rod client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4727) Aggregation is performed incorrectly for JOIN queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4727?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4727: ---------------------------------- I still see this behavior on master. The handling of count or other cardinality dependent aggregates assumes a join predicate to relate the sides of the join. Without that in many circumstances we should not be pushing the staged grouping. > Aggregation is performed incorrectly for JOIN queries > ----------------------------------------------------- > > Key: TEIID-4727 > URL: https://issues.jboss.org/browse/TEIID-4727 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.0.3 > Environment: teiid-9.0.3 on WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > > Aggregation is performed incorrectly for JOIN queries, like this > {code:sql} > select count(v2.b) from views.v1 right join views.v2 on true group by v1.b; > select count(v2.b) from views.v1 join (call procs.pr()) v2 on true group by v1.b; > select count(v2.b) from views.v1 left join (call procs.pr()) v2 on true group by v1.b; > select count(v2.b) from views.v1 right join (call procs.pr()) v2 on true group by v1.b; > {code} > showing as a result: > {code} > 1 > 1 > 1 > {code} > though these ones work correctly: > {code:sql} > select count(v2.b) from views.v1 join views.v2 on true group by v1.b; > select count(v2.b) from views.v1 left join views.v2 on true group by v1.b; > {code} > showing > {code} > 1 > 1 > 2 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4727) Aggregation is performed incorrectly for JOIN queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4727?page=com.atlassian.jira.plugin... ] Work on TEIID-4727 started by Steven Hawkins. --------------------------------------------- > Aggregation is performed incorrectly for JOIN queries > ----------------------------------------------------- > > Key: TEIID-4727 > URL: https://issues.jboss.org/browse/TEIID-4727 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.0.3 > Environment: teiid-9.0.3 on WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > > Aggregation is performed incorrectly for JOIN queries, like this > {code:sql} > select count(v2.b) from views.v1 right join views.v2 on true group by v1.b; > select count(v2.b) from views.v1 join (call procs.pr()) v2 on true group by v1.b; > select count(v2.b) from views.v1 left join (call procs.pr()) v2 on true group by v1.b; > select count(v2.b) from views.v1 right join (call procs.pr()) v2 on true group by v1.b; > {code} > showing as a result: > {code} > 1 > 1 > 1 > {code} > though these ones work correctly: > {code:sql} > select count(v2.b) from views.v1 join views.v2 on true group by v1.b; > select count(v2.b) from views.v1 left join views.v2 on true group by v1.b; > {code} > showing > {code} > 1 > 1 > 2 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4727) Aggregation is performed incorrectly for JOIN queries

by dalex dalex (JIRA)

dalex dalex created TEIID-4727: ---------------------------------- Summary: Aggregation is performed incorrectly for JOIN queries Key: TEIID-4727 URL: https://issues.jboss.org/browse/TEIID-4727 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 9.0.3 Environment: teiid-9.0.3 on WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) Reporter: dalex dalex Assignee: Steven Hawkins Priority: Blocker Aggregation is performed incorrectly for JOIN queries, like this {code:sql} select count(v2.b) from views.v1 right join views.v2 on true group by v1.b; select count(v2.b) from views.v1 join (call procs.pr()) v2 on true group by v1.b; select count(v2.b) from views.v1 left join (call procs.pr()) v2 on true group by v1.b; select count(v2.b) from views.v1 right join (call procs.pr()) v2 on true group by v1.b; {code} showing as a result: {code} 1 1 1 {code} though these ones work correctly: {code:sql} select count(v2.b) from views.v1 join views.v2 on true group by v1.b; select count(v2.b) from views.v1 left join views.v2 on true group by v1.b; {code} showing {code} 1 1 2 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4726) "java.util.ConcurrentModificationException" when deploying VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4726?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4726: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1417241, https://bugzilla.redhat.com/show_bug.cgi?id=1417246 Bugzilla Update: Perform > "java.util.ConcurrentModificationException" when deploying VDB > -------------------------------------------------------------- > > Key: TEIID-4726 > URL: https://issues.jboss.org/browse/TEIID-4726 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.9.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > Customer is seeing "java.util.ConcurrentModificationException"[1] when deploying their VDB, the vdb is not active. > [1] > 06:10:47,275 ERROR [stderr] (teiid-async-threads - 3) Exception in thread "teiid-async-threads - 3" java.util.ConcurrentModificationException > 06:10:47,276 ERROR [stderr] (teiid-async-threads - 3) at java.util.ArrayList.writeObject(ArrayList.java:746) > 06:10:47,276 ERROR [stderr] (teiid-async-threads - 3) at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) > 06:10:47,276 ERROR [stderr] (teiid-async-threads - 3) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 06:10:47,276 ERROR [stderr] (teiid-async-threads - 3) at java.lang.reflect.Method.invoke(Method.java:606) > 06:10:47,276 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028) > 06:10:47,276 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1495) > 06:10:47,277 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) > 06:10:47,277 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) > 06:10:47,277 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) > 06:10:47,288 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) > 06:10:47,289 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) > 06:10:47,289 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) > 06:10:47,289 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) > 06:10:47,289 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) > 06:10:47,289 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) > 06:10:47,289 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) > 06:10:47,290 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) > 06:10:47,290 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) > 06:10:47,290 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) > 06:10:47,290 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) > 06:10:47,290 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) > 06:10:47,290 ERROR [stderr] (teiid-async-threads - 3) at java.util.ArrayList.writeObject(ArrayList.java:742) > 06:10:47,291 ERROR [stderr] (teiid-async-threads - 3) at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) > 06:10:47,291 ERROR [stderr] (teiid-async-threads - 3) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 06:10:47,291 ERROR [stderr] (teiid-async-threads - 3) at java.lang.reflect.Method.invoke(Method.java:606) > 06:10:47,291 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028) > 06:10:47,291 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1495) > 06:10:47,291 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) > 06:10:47,291 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) > 06:10:47,292 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) > 06:10:47,292 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) > 06:10:47,292 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) > 06:10:47,292 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) > 06:10:47,292 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) > 06:10:47,292 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) > 06:10:47,293 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) > 06:10:47,293 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) > 06:10:47,293 ERROR [stderr] (teiid-async-threads - 3) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) > 06:10:47,293 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.ObjectSerializer.saveAttachment(ObjectSerializer.java:77) > 06:10:47,293 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.cacheMetadataStore(VDBService.java:468) > 06:10:47,293 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.access$900(VDBService.java:85) > 06:10:47,297 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$6.run(VDBService.java:405) > 06:10:47,297 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$7.run(VDBService.java:439) > 06:10:47,297 ERROR [stderr] (teiid-async-threads - 3) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > 06:10:47,297 ERROR [stderr] (teiid-async-threads - 3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > 06:10:47,298 ERROR [stderr] (teiid-async-threads - 3) at java.lang.Thread.run(Thread.java:745) > 06:10:47,298 ERROR [stderr] (teiid-async-threads - 3) at org.jboss.threads.JBossThread.run(JBossThread.java:122) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4504) Provide an option to ignore the atomic block handling of triggers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4504?page=com.atlassian.jira.plugin... ] Work on TEIID-4504 started by Steven Hawkins. --------------------------------------------- > Provide an option to ignore the atomic block handling of triggers > ----------------------------------------------------------------- > > Key: TEIID-4504 > URL: https://issues.jboss.org/browse/TEIID-4504 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > While BEGIN ATOMIC is mandated by the spec, it may not be desirable to force a transaction block in all circumstances and instead rely on the autoCommit transaction. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4626: ---------------------------------- Fix Version/s: 9.3 (was: 9.2) > Add a full snapshot refresh strategy based upon table modifications > ------------------------------------------------------------------- > > Key: TEIID-4626 > URL: https://issues.jboss.org/browse/TEIID-4626 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 9.3 > > > using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4625) Consider consolidating/managing materialization status tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4625?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4625: ---------------------------------- Fix Version/s: 9.3 (was: 9.2) > Consider consolidating/managing materialization status tables > ------------------------------------------------------------- > > Key: TEIID-4625 > URL: https://issues.jboss.org/browse/TEIID-4625 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.3 > > > To enhance usability we should consider consolidating/managing status tables. Management would include auto creation similar (which could just leverage hibernate similar to the database log logic, regardless of whether we use hibernate to read/write). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4709) Enable JDG resource adapter to pass the username/password to HotRod Client

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4709?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4709: ------------------------------------ Yes. However for materialization, would we want to require the a special user/password or assume that the admin (or what ever user that's kicking it off) would have to have the correct permission on the JDG side? > Enable JDG resource adapter to pass the username/password to HotRod Client > -------------------------------------------------------------------------- > > Key: TEIID-4709 > URL: https://issues.jboss.org/browse/TEIID-4709 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Affects Versions: 9.3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > Enable the JDG resource adapter to pass the username/password to the JDG hot rod client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2017