February 2017 - teiid-issues - Jboss List Archives

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4626: ------------------------------------- Since we are just collecting # of source updates without correlation to view, it is unknown #rows or #columns on the view that are affected. Thus my comment about a possible callback procedure that user defined to make decision when to run the reload. > 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 > Assignee: Ramesh Reddy > 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)

9 years, 1 month

1
0
0 / 0

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

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4727?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4727: --------------------------------- Fix Version/s: 8.12.10.6_3 > 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 > Fix For: 9.0.6, 9.2, 9.1.3, 8.7.12.6_2, 8.12.10.6_3 > > > 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)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4770) The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4770?page=com.atlassian.jira.plugin... ] Work on TEIID-4770 started by Steven Hawkins. --------------------------------------------- > The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema. > -------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4770 > URL: https://issues.jboss.org/browse/TEIID-4770 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 9.2 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1 > > > The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema. > E.g. GRANT ON SCHEMA glims TO mica; > When you try to deploy the script, the server complains that it expects a permission type (like select or alter) here. > These lines should probably be removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4726?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4726: --------------------------------- Fix Version/s: 8.12.10.6_3 > "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 > Fix For: 9.2, 8.7.12.6_2, 8.12.10.6_3 > > > 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)

9 years, 1 month

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 commented on TEIID-4626: --------------------------------------- > I think when to reload based on stale record count is thorny issue, this must be driven by the user. That's not being proposed - I'm saying that is how result set caching works. The description of this issue is to trigger a reload when the materialization is some percent dirty - that could be # of transitive column modifications / (# of rows * # of columns) - or simplified to just rows. So we're trying to allow the user to say something like trigger a refresh when the materialization is approximately 1% dirty. > 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 > Assignee: Ramesh Reddy > 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)

9 years, 1 month

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4626: ------------------------------------- I think when to reload based on stale record count is thorny issue, this must be driven by the user. Whatever we do will not be sufficient for other user. How about user providing a procedure, which we can call with given statistics that tells us to start a reload or not? > 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 > Assignee: Ramesh Reddy > 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)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4720) changes in requiresLeftLinearJoin and useParensForJoins needed for Hive

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4720?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4720: --------------------------------- Fix Version/s: 8.12.10.6_3 > changes in requiresLeftLinearJoin and useParensForJoins needed for Hive > ----------------------------------------------------------------------- > > Key: TEIID-4720 > URL: https://issues.jboss.org/browse/TEIID-4720 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.2, 8.12.10.6_3 > > > 4 table join in Hive requires settings: > requiresLeftLinearJoin true, useParensForJoins false -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4666) Google translator throws SpreadsheetOperationException for query DELETE FROM table

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4666?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4666: --------------------------------- Fix Version/s: 8.12.10.6_3 > Google translator throws SpreadsheetOperationException for query DELETE FROM table > ---------------------------------------------------------------------------------- > > Key: TEIID-4666 > URL: https://issues.jboss.org/browse/TEIID-4666 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.2, 8.12.10.6_3 > > Attachments: googlespreadsheetcrud-vdb.xml, server.log, standalone.xml, teiid-4666.png > > > Query "DELETE FROM smalla" where smalla is table throws exception: > 07:06:52,219 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue20) Connector worker process failed for atomic-request=IlMZP21M8Gwr.8.0.2: org.teiid.resource.adapter.google.common.SpreadsheetOperationException: Error getting spreadsheet feed. Possibly bad authentication or connection problems. com.google.gdata.util.InvalidEntryException: Bad Request > Invalid query parameter value for sq. > Please see server.log, standalone.xml and vdb for other information. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4787) Add Netzza datasource configuration example

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4787?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4787: ----------------------------------- Assignee: (was: Steven Hawkins) > Add Netzza datasource configuration example > -------------------------------------------- > > Key: TEIID-4787 > URL: https://issues.jboss.org/browse/TEIID-4787 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Ramesh Reddy > Fix For: 9.3 > > > In "docs" directory there is no example for Netezza datasource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4787) Add Netzza datasource configuration example

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4787: ----------------------------------- Summary: Add Netzza datasource configuration example Key: TEIID-4787 URL: https://issues.jboss.org/browse/TEIID-4787 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 9.3 In "docs" directory there is no example for Netezza datasource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017