October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4533) Change the default max-staleness for the resultset cache to 0

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4533?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4533. ----------------------------------- Resolution: Done Updated the code, release-notes, and documentation. > Change the default max-staleness for the resultset cache to 0 > ------------------------------------------------------------- > > Key: TEIID-4533 > URL: https://issues.jboss.org/browse/TEIID-4533 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > We have inherited the property setting for years and have to call it out in several places in the docs. It would be best to default to 0, and instead call out in the docs that cache can be made more tolerant to stale entries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4533) Change the default max-staleness for the resultset cache to 0

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4533?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4533: ---------------------------------- Forum Reference: https://developer.jboss.org/thread/272745 > Change the default max-staleness for the resultset cache to 0 > ------------------------------------------------------------- > > Key: TEIID-4533 > URL: https://issues.jboss.org/browse/TEIID-4533 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > We have inherited the property setting for years and have to call it out in several places in the docs. It would be best to default to 0, and instead call out in the docs that cache can be made more tolerant to stale entries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4526: ------------------------------------ To create bullet points related to the challenges to making this work: * Since we allow for hand editing and only capture a simple quoted name in source, we first have a matching problem from any event source to our source metadata. * There can be type issues or even the consideration for masking or other effects. Inferring values directly from the change event can be an issue as the CDC layer is broadcasting raw values, not what you would fetch over jdbc. * Aggregates may need to be recomputed, multiple rows removed, etc. Thoughts on implementation: * Keeping some notion of how "dirty" a particular materialized view is (number of updates that affect the view vs. number of view rows) and trigger a full refresh above a given threshold. * Need to determine if there are differing expectations for internal vs. external materialization. > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4534) Querying 1-to-many relationship in JDG data source may return the wrong results

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4534?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4534: ------------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Querying 1-to-many relationship in JDG data source may return the wrong results > ------------------------------------------------------------------------------- > > Key: TEIID-4534 > URL: https://issues.jboss.org/browse/TEIID-4534 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x, 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > When there is a 1-to-many relationship defined in a JDG schema, the results from querying the "many" relationship may return the wrong results. > Example: > Person --> Phone Numbers > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567'); > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568'); > SELECT p.name, p.id, pn.number FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 and number = '001234568' > or > Select * from PhoneNumber where number = '001234568' > return 2 rows, 1 for each phonenumber. > Why? Because JDG returns the Person object that meets those conditions. It doesn't filter the internal data to the Person object. Therefore, all phonenumbers are returned for the same person, generating a row for each. > This doesn't happen with 1-to-1 relationships because there's only ever 1 child object. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4535) Issues with EventDistributor

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4535?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4535. ----------------------------------- Resolution: Done added a check to see if the method is remote only and moved the initialization in the embedded case. Added a test to ensure that setTableStats is distributed as expected. > Issues with EventDistributor > ---------------------------- > > Key: TEIID-4535 > URL: https://issues.jboss.org/browse/TEIID-4535 > Project: Teiid > Issue Type: Bug > Components: Embedded, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2, 9.0.5, 9.1.1 > > > Non remote methods called twice in clustered mode and with the EventListener methods (add/remove listener). The proxy will call the local and the remoting handling, which again will call the local. > Also the Embedded logic is not properly initializing the eventdistributor as it is starting before the objectreplicator may have been created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4536) Support create schema with multiple statements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4536?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4536: --------------------------------------- See a previous comment on TEIID-4536, that behavior was removed - it is not expected by the spec. > Support create schema with multiple statements > ---------------------------------------------- > > Key: TEIID-4536 > URL: https://issues.jboss.org/browse/TEIID-4536 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.2 > > > Create schema can support following create statements being directly associated rather than requiring an intermediate use schema > create schema x > create view ...; > ... > ; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4536) Support create schema with multiple statements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4536?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4536: ------------------------------------- CREATE SCHEMA establishes the context already, it should not require the "SET SCHEMA ..." command. > Support create schema with multiple statements > ---------------------------------------------- > > Key: TEIID-4536 > URL: https://issues.jboss.org/browse/TEIID-4536 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.2 > > > Create schema can support following create statements being directly associated rather than requiring an intermediate use schema > create schema x > create view ...; > ... > ; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4537) Store ddl as fully qualified

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4537: ------------------------------------- Summary: Store ddl as fully qualified Key: TEIID-4537 URL: https://issues.jboss.org/browse/TEIID-4537 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins To prevent later statements (in particular create) from causing issues with existing objects, the original sql will need to be stored fully qualified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4536) Support create schema with multiple statements

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4536: ------------------------------------- Summary: Support create schema with multiple statements Key: TEIID-4536 URL: https://issues.jboss.org/browse/TEIID-4536 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Create schema can support following create statements being directly associated rather than requiring an intermediate use schema create schema x create view ...; ... ; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4535) Issues with EventDistributor

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4535?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4535: ---------------------------------- Component/s: Embedded Description: Non remote methods called twice in clustered mode and with the EventListener methods (add/remove listener). The proxy will call the local and the remoting handling, which again will call the local. Also the Embedded logic is not properly initializing the eventdistributor as it is starting before the objectreplicator may have been created. was:This is specifically an issue in clustered mode and with the EventListener methods. The proxy will call the local and the remoting handling, which again will call the local. Fix Version/s: 9.0.5 9.1.1 Summary: Issues with EventDistributor (was: Non remote methods called twice on the EventDistributor) Priority: Critical (was: Major) > Issues with EventDistributor > ---------------------------- > > Key: TEIID-4535 > URL: https://issues.jboss.org/browse/TEIID-4535 > Project: Teiid > Issue Type: Bug > Components: Embedded, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2, 9.0.5, 9.1.1 > > > Non remote methods called twice in clustered mode and with the EventListener methods (add/remove listener). The proxy will call the local and the remoting handling, which again will call the local. > Also the Embedded logic is not properly initializing the eventdistributor as it is starting before the objectreplicator may have been created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 October 2016