June 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4961) External Materialized View With State Loaded but 0 Cardinality

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4961?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4961. ----------------------------------- Resolution: Done Corrected the bug introduced by the planning change to move when the mvstatus function is checked. When a full insert with a query expression was pushed, the status check was not associated with the query. > External Materialized View With State Loaded but 0 Cardinality > -------------------------------------------------------------- > > Key: TEIID-4961 > URL: https://issues.jboss.org/browse/TEIID-4961 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.3 > Environment: * Teiid 9.3.0 > * MySQL 5.7.18 > * Wildfly 10 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.1 > > Attachments: server.log > > > *Scenario*: Having several views that depend on others (ex: V1-> V2->V3, where V3 depends on V2 and V2 depends on V1), all with external materialization. > Although all views LoadState is *LOADED *even after failures due to the dependent ones being loaded, in the end some views have zero (0) of cardinality, when there are actually records. Running the queries by hand return records. > Log attached. > Example: > {panel} > 2017-06-14 17:14:39,521 INFO [org.teiid.MATVIEWS] (Worker63_QueryProcessorQueue19799) WDpoyHmXlkvS Materialization of view VodafoneNlBaseSource.vodafone_nl_base_source completed. Rows updated = 0 Load Number = 1 > {panel} > After forcing the view update: > {panel} > 2017-06-14 17:23:38,042 INFO [org.teiid.MATVIEWS] (Worker65_QueryProcessorQueue27597) +IbRaNRtrZ1K Materialization of view VodafoneNlBaseSource.vodafone_nl_base_source completed. Rows updated = 1816 Load Number = 2 > {panel} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4961) External Materialized View With State Loaded but 0 Cardinality

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4961?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4961: ---------------------------------- Component/s: Query Engine Fix Version/s: 10.0 9.3.1 I can reproduce this behavior as well - only after subsequent reloads do the dependent mat views load correctly. I'll have a fix shortly. > External Materialized View With State Loaded but 0 Cardinality > -------------------------------------------------------------- > > Key: TEIID-4961 > URL: https://issues.jboss.org/browse/TEIID-4961 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.3 > Environment: * Teiid 9.3.0 > * MySQL 5.7.18 > * Wildfly 10 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.1 > > Attachments: server.log > > > *Scenario*: Having several views that depend on others (ex: V1-> V2->V3, where V3 depends on V2 and V2 depends on V1), all with external materialization. > Although all views LoadState is *LOADED *even after failures due to the dependent ones being loaded, in the end some views have zero (0) of cardinality, when there are actually records. Running the queries by hand return records. > Log attached. > Example: > {panel} > 2017-06-14 17:14:39,521 INFO [org.teiid.MATVIEWS] (Worker63_QueryProcessorQueue19799) WDpoyHmXlkvS Materialization of view VodafoneNlBaseSource.vodafone_nl_base_source completed. Rows updated = 0 Load Number = 1 > {panel} > After forcing the view update: > {panel} > 2017-06-14 17:23:38,042 INFO [org.teiid.MATVIEWS] (Worker65_QueryProcessorQueue27597) +IbRaNRtrZ1K Materialization of view VodafoneNlBaseSource.vodafone_nl_base_source completed. Rows updated = 1816 Load Number = 2 > {panel} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4976. ----------------------------------- Fix Version/s: 10.0 Resolution: Done Added a small update to the dependent criteria processor to dedup. This is not quite as good as a general rewrite, but that would have required further tweaks. > criteria duplicated when criteria includes the same columns as dependent join criteria > -------------------------------------------------------------------------------------- > > Key: TEIID-4976 > URL: https://issues.jboss.org/browse/TEIID-4976 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.11.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 10.0 > > > Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join. > For example: > SELECT * FROM A, B > WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B; > Results in the dependent side query looking like: > SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3'); > This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4976: ---------------------------------- Component/s: Query Engine > criteria duplicated when criteria includes the same columns as dependent join criteria > -------------------------------------------------------------------------------------- > > Key: TEIID-4976 > URL: https://issues.jboss.org/browse/TEIID-4976 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.11.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join. > For example: > SELECT * FROM A, B > WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B; > Results in the dependent side query looking like: > SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3'); > This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4976: --------------------------------------- >From what I can see this still occurs on master. This should only occur when there is a makedep hint present. > criteria duplicated when criteria includes the same columns as dependent join criteria > -------------------------------------------------------------------------------------- > > Key: TEIID-4976 > URL: https://issues.jboss.org/browse/TEIID-4976 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.11.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join. > For example: > SELECT * FROM A, B > WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B; > Results in the dependent side query looking like: > SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3'); > This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria

by Marc Shirley (JIRA)

[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ] Marc Shirley commented on TEIID-4976: ------------------------------------- This is to look into pulling back a fix to 6.2.12. So, to an effect both. My comments towards not being able to find an original previous report for this were towards indicating that this is resolved in 8.12 versions, but still present in 8.7 versions. So, the intention is to identify the original issue if it exists, or explore what change fixed the issue if a previous report for this scenario does not exist. > criteria duplicated when criteria includes the same columns as dependent join criteria > -------------------------------------------------------------------------------------- > > Key: TEIID-4976 > URL: https://issues.jboss.org/browse/TEIID-4976 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.11.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join. > For example: > SELECT * FROM A, B > WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B; > Results in the dependent side query looking like: > SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3'); > This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4978) Document issue with SQLAlchemy/Superset and table names containing .

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4978: ------------------------------------- Summary: Document issue with SQLAlchemy/Superset and table names containing . Key: TEIID-4978 URL: https://issues.jboss.org/browse/TEIID-4978 Project: Teiid Issue Type: Quality Risk Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 Superset/SQLAlchemy cannot find column metadata for tables that contain . in their name - this occurs directly against Postgresql, so this isn't specifically a Teiid issue. However Teiid is likely to create foreign tables that contain . in their names unless the importer is told to not schema qualify. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4977) Support materialization as the 8.12.x version did

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4977?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4977: ------------------------------------ Can the 8.12.x logic, that Steve implemented, be used in this case, where 3 caches are used to accomplish this scenario? > Support materialization as the 8.12.x version did > ------------------------------------------------- > > Key: TEIID-4977 > URL: https://issues.jboss.org/browse/TEIID-4977 > Project: Teiid > Issue Type: Feature Request > Components: Infinispan > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > > Need to enable the materialization process to load the cache "offline" and not impact access to current cache and data. This would be similar to how the 8.12.x version was implemented and similar to how RDBMS materialization is done. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4977) Support materialization as the 8.12.x version did

by Van Halbert (JIRA)

Van Halbert created TEIID-4977: ---------------------------------- Summary: Support materialization as the 8.12.x version did Key: TEIID-4977 URL: https://issues.jboss.org/browse/TEIID-4977 Project: Teiid Issue Type: Feature Request Components: Infinispan Affects Versions: 8.12.x-6.4 Reporter: Van Halbert Assignee: Ramesh Reddy Priority: Critical Need to enable the materialization process to load the cache "offline" and not impact access to current cache and data. This would be similar to how the 8.12.x version was implemented and similar to how RDBMS materialization is done. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4903) Create a new server quickstart for the new infinispan hotrod connector/translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4903?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4903: ------------------------------- Fix Version/s: 8.12.x-6.4 > Create a new server quickstart for the new infinispan hotrod connector/translator > --------------------------------------------------------------------------------- > > Key: TEIID-4903 > URL: https://issues.jboss.org/browse/TEIID-4903 > Project: Teiid > Issue Type: Task > Components: Infinispan, Quick Starts > Affects Versions: 9.3.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.12.x-6.4 > > > Create a new server quickstart for the new infinispan hotrod connector/translator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2017