September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2584: --------------------------------------- Can you refresh me, what do you envision the start/stop hooks for? > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- Changed above check to {code:lang=SQL} SELECT * FROM MAT_VIEW WHERE 1 = ALL(SELECT MVSTATUS(Valid, LoadState, OnErrorAction) FROM {statusTbl} WHERE VDBName=? AND VDBVersion=? AND SchemaName=? AND viewName = ?) {code} As I observed from previous check that EXISTS will be true for either valid or invalid situations as along there is a result, even if it is null. So, I choose the above kind of check, that seems work as expected. Also implemented the "wait" action, when matview is not valid or not in "LOADED" state, the user query will wait until the "status" table is shows that the matview is in "LOADED" state with valid set to true. During the wait, the query submits polling commands to check the status of "status" table every 30 seconds. We could make this time-slot configurable if needed. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2648) Add the login username to the source query comment along with the session and requests IDs

by Colin Mondesir (JIRA)

[ https://issues.jboss.org/browse/TEIID-2648?page=com.atlassian.jira.plugin... ] Colin Mondesir deleted TEIID-2648: ---------------------------------- > Add the login username to the source query comment along with the session and requests IDs > ------------------------------------------------------------------------------------------ > > Key: TEIID-2648 > URL: https://issues.jboss.org/browse/TEIID-2648 > Project: Teiid > Issue Type: Feature Request > Reporter: Colin Mondesir > Assignee: Steven Hawkins > -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2648) Add the login username to the source query comment along with the session and requests IDs

by Colin Mondesir (JIRA)

Colin Mondesir created TEIID-2648: ------------------------------------- Summary: Add the login username to the source query comment along with the session and requests IDs Key: TEIID-2648 URL: https://issues.jboss.org/browse/TEIID-2648 Project: Teiid Issue Type: Feature Request Reporter: Colin Mondesir Assignee: Steven Hawkins -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2035: ------------------------------------------------ Stefano Maestri <smaestri(a)redhat.com> changed the Status of [bug 985576|https://bugzilla.redhat.com/show_bug.cgi?id=985576] from NEW to CLOSED > DeleteDataSource method on Admin API does not completely delete the Connection Factory > -------------------------------------------------------------------------------------- > > Key: TEIID-2035 > URL: https://issues.jboss.org/browse/TEIID-2035 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.4.1, 8.5 > > > ConnectionFactory requires a two step creation process > 1) create the resource-adaptor section > 2) connection factory section > The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2035: ------------------------------------------------ Stefano Maestri <smaestri(a)redhat.com> made a comment on [bug 985576|https://bugzilla.redhat.com/show_bug.cgi?id=985576] Closing based on comment 13 and 14 > DeleteDataSource method on Admin API does not completely delete the Connection Factory > -------------------------------------------------------------------------------------- > > Key: TEIID-2035 > URL: https://issues.jboss.org/browse/TEIID-2035 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.4.1, 8.5 > > > ConnectionFactory requires a two step creation process > 1) create the resource-adaptor section > 2) connection factory section > The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- My thinking there was, if user changed their mind and would like to change the outcome, and also when reporting the status of the materialization it would be in single place for use to access, but you are correct it does not required to be there. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- Per SteveH suggestion, added a "status" check such that when a materialization view is being accessed, it will issue a query like below to fetch the results of the materialized view {code} SELECT * FROM MAT_VIEW WHERE EXISTS (SELECT MVSTATUS(Valid, LoadState, OnErrorAction) FROM {statusTbl} WHERE VDBName=? AND VDBVersion=? AND SchemaName=? AND viewName = ?) {code} Where "MVSTATUS" is a system function, which based on the validity and LoadStatus carries out the "action" defined by OnErrorAction. Currently it code allows THROW_EXCEPTION, IGNORE actions. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2584: --------------------------------------- Does onErrorAction need to be on the status table? If it's already a metadata property we don't need to also place it on the status table. Also if it's set to ignore then we can omit adding the subquery to the planned form of the view. You can also implement a "wait" behavior by allowing blocked exceptions to bubble up from the FunctionDescriptor invocation. Then we either need a waiting queue/notification when finished, or just have the function logic get the workitem and schedule more work at some polling interval. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2647) Add an impala translator

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2647: ------------------------------------- Summary: Add an impala translator Key: TEIID-2647 URL: https://issues.jboss.org/browse/TEIID-2647 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: Open To Community Impala offers an alternative to Hive SQL access: http://blog.cloudera.com/blog/2012/10/cloudera-impala-real-time-queries-i... -- 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

12 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013