January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2796) An importing vdb does not properly handle imported multi-source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2796?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2796. ----------------------------------- Resolution: Done Correct the composite vdb logic so that it looks at the merged vdb state and not the original importing vdb to determine the multisource models. > An importing vdb does not properly handle imported multi-source > --------------------------------------------------------------- > > Key: TEIID-2796 > URL: https://issues.jboss.org/browse/TEIID-2796 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > When importing a vdb the imported multi-source models are not properly treated as multi-source. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2796) An importing vdb does not properly handle imported multi-source

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2796?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2796: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1050335|https://bugzilla.redhat.com/show_bug.cgi?id=1050335] from NEW to ASSIGNED > An importing vdb does not properly handle imported multi-source > --------------------------------------------------------------- > > Key: TEIID-2796 > URL: https://issues.jboss.org/browse/TEIID-2796 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > When importing a vdb the imported multi-source models are not properly treated as multi-source. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2796) An importing vdb does not properly handle imported multi-source

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2796?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2796: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1050335 > An importing vdb does not properly handle imported multi-source > --------------------------------------------------------------- > > Key: TEIID-2796 > URL: https://issues.jboss.org/browse/TEIID-2796 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > When importing a vdb the imported multi-source models are not properly treated as multi-source. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2796) An importing vdb does not properly handle imported multi-source

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2796: ------------------------------------- Summary: An importing vdb does not properly handle imported multi-source Key: TEIID-2796 URL: https://issues.jboss.org/browse/TEIID-2796 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.7 When importing a vdb the imported multi-source models are not properly treated as multi-source. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2795) TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2795: --------------------------------------- What I can infer from the sequence of events is that this highlights a design issue with the implicit refresh that is in 7.7. The refresh task is kicked of asynchly (since the data has not been invalidated the current request is allowed to continue) and also runs as a child of the current request. So that early termination of the calling session will effectively kill the refresh task. Only blocking refreshes will not suffer from this problem in 7.7, such as issuing a refreshMatView procedure call. This was addressed as part of TEIID-2467 such that the refresh runs in it's own session/request. A more targeted change would be needed for 7.7.x, although I'm not sure about the level of effort. > TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT > -------------------------------------------------------------------------------------- > > Key: TEIID-2795 > URL: https://issues.jboss.org/browse/TEIID-2795 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > using the cache hint to automatically trigger a full snapshot refresh after a specified time to live (TTL)[1]. The TTL works but if the user query that is run contains a LIMIT clause the refresh load uses the LIMIT and doesn't completely load the internal MV and fails load. > Sequence of events > 1) Execute the query to initiate the internal MV load > 2) After caching, issue the same query but with limit of 10,000 to test it is hitting the cache > 3) Wait for 5 minutes for TTL to expire > 4) Re-issue the same query with limit of 10,000 and i can see the state change to reloading but once the query has finished fetching 10,000 from data source it terminates and the MV state changed to failed_load. I would have expected the MV to continue to load to rehydrate the cache and the query should be fetching the data from the stale cache. But this is not the case ... > [1]https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Dat... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2795) TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2795: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1050059|https://bugzilla.redhat.com/show_bug.cgi?id=1050059] from NEW to ASSIGNED > TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT > -------------------------------------------------------------------------------------- > > Key: TEIID-2795 > URL: https://issues.jboss.org/browse/TEIID-2795 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > using the cache hint to automatically trigger a full snapshot refresh after a specified time to live (TTL)[1]. The TTL works but if the user query that is run contains a LIMIT clause the refresh load uses the LIMIT and doesn't completely load the internal MV and fails load. > Sequence of events > 1) Execute the query to initiate the internal MV load > 2) After caching, issue the same query but with limit of 10,000 to test it is hitting the cache > 3) Wait for 5 minutes for TTL to expire > 4) Re-issue the same query with limit of 10,000 and i can see the state change to reloading but once the query has finished fetching 10,000 from data source it terminates and the MV state changed to failed_load. I would have expected the MV to continue to load to rehydrate the cache and the query should be fetching the data from the stale cache. But this is not the case ... > [1]https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Dat... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2795) TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2795: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1050059 > TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT > -------------------------------------------------------------------------------------- > > Key: TEIID-2795 > URL: https://issues.jboss.org/browse/TEIID-2795 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > using the cache hint to automatically trigger a full snapshot refresh after a specified time to live (TTL)[1]. The TTL works but if the user query that is run contains a LIMIT clause the refresh load uses the LIMIT and doesn't completely load the internal MV and fails load. > Sequence of events > 1) Execute the query to initiate the internal MV load > 2) After caching, issue the same query but with limit of 10,000 to test it is hitting the cache > 3) Wait for 5 minutes for TTL to expire > 4) Re-issue the same query with limit of 10,000 and i can see the state change to reloading but once the query has finished fetching 10,000 from data source it terminates and the MV state changed to failed_load. I would have expected the MV to continue to load to rehydrate the cache and the query should be fetching the data from the stale cache. But this is not the case ... > [1]https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Dat... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2795) TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-2795: -------------------------------------- Summary: TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT Key: TEIID-2795 URL: https://issues.jboss.org/browse/TEIID-2795 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7.8 Reporter: Debbie Steigner Assignee: Steven Hawkins using the cache hint to automatically trigger a full snapshot refresh after a specified time to live (TTL)[1]. The TTL works but if the user query that is run contains a LIMIT clause the refresh load uses the LIMIT and doesn't completely load the internal MV and fails load. Sequence of events 1) Execute the query to initiate the internal MV load 2) After caching, issue the same query but with limit of 10,000 to test it is hitting the cache 3) Wait for 5 minutes for TTL to expire 4) Re-issue the same query with limit of 10,000 and i can see the state change to reloading but once the query has finished fetching 10,000 from data source it terminates and the MV state changed to failed_load. I would have expected the MV to continue to load to rehydrate the cache and the query should be fetching the data from the stale cache. But this is not the case ... [1]https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Dat... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2785: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1045206|https://bugzilla.redhat.com/show_bug.cgi?id=1045206] from ASSIGNED to NEW > Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call > ---------------------------------------------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > > The ModeShapeExecutionFactory should expose the JCR procedures in the metadata when the getMetadata(..) is called. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2783) ModeShape query isn't retaining quotes defined for column in NIS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2783?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2783: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1045206|https://bugzilla.redhat.com/show_bug.cgi?id=1045206] from ASSIGNED to NEW > ModeShape query isn't retaining quotes defined for column in NIS > ---------------------------------------------------------------- > > Key: TEIID-2783 > URL: https://issues.jboss.org/browse/TEIID-2783 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Attachments: ModeShape.vdb > > > Issuing query: > SELECT jcr_name FROM nt_base AS children WHERE JCR_ISCHILDNODE(children.jcr_path, '/pathtoparent') > produces exception: > Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_0.jcr:name FROM "nt:base" AS g_0 WHERE ISCHILDNODE(g_0.jcr:path, '/pathtoparent')" is not well-formed: Expecting "FROM" but found ":" at line 1, column 15: SELECT g_0.jcr ===>> :name FROM "nt:base" > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146) > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014