January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2761: --------------------------------------- I didn't communicate well. What I saying is that if a vdb with a security-domain property specifies security domain x and the transport is configured to have security domains y,z - do we allow the vdb security domain to be the one that is used (the behavior I would expect) or would we require the vdb's security domain to be one of the one's configured on the transport. > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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-2761) Enable/disable transport per model/view/virtual procedure

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2761: ------------------------------------- Right now we do not mix configuration with runtime deployments, so if we need to add to the transport that means deployment/undeployment of the VDB will necessitate a configuration update albeit auto-magically. I do not think I like that fact. We could just fail/in-active deployment of the VDB if the configured transport is not in configuration. > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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-2761) Enable/disable transport per model/view/virtual procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2761: --------------------------------------- > So in that case we could raise this above the data role level to VDB property if that makes sense. That's what I'm thinking. If left unspecified, then things will act as they do today. If specified, then we'll require authentication into that security domain. As a vdb property then it won't require invasive tooling changes. The only question would be whether the security domain specified by the vdb has to also be specified in the transport configuration. > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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-2761) Enable/disable transport per model/view/virtual procedure

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2761: ------------------------------------- Right now VDB and security-domain are not related. So, if we restrict VDB to single security-domain, that will restrict to the transport(s) that is configured with. [thinking out loud] >Isn't more typical that each vdb will be in a single security domain? Yes, especially if they want to use data roles. It seems silly to have two sets of users that authenticate differently for a given resource. >Generally wasn't the purpose of allowing multiple security domains per transport so that different vdbs could >effectively be in different security domains? This was not the original intention, but I agree that fits the model. I believe before we made a switch to JAAS, the requirement was to use different security domains so that user could be authenticated with different security stores. In the JBoss security-domain configuration, it gives that ability to configure multiple stores inside single security-domain so that is satisfied. So in that case we could raise this above the data role level to VDB property if that makes sense. > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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-2761) Enable/disable transport per model/view/virtual procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2761: --------------------------------------- Except that it requires \@ to be escaped, which is a potentially breaking change, and greatly changes our logic. It also seems like we should re-examine our assumptions about having multiple security domains available for each vdb/role. Isn't more typical that each vdb will be in a single security domain? Generally wasn't the purpose of allowing multiple security domains per transport so that different vdbs could effectively be in different security domains? > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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-2761) Enable/disable transport per model/view/virtual procedure

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2761: ------------------------------------- OK, cross domain aside, mapping qualification seems to be more intuitive and will work without any tooling changes. > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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-2761) Enable/disable transport per model/view/virtual procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2761: --------------------------------------- > Right now Teiid defaulting that value to given transport's security-domain, this makes it explicit and allows more cross security-domain entries. I'm not sure cross security domain makes sense at least comparing to similar JEE concepts and does require the use of mapping qualification, which complicates the logic considerably. > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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-2761) Enable/disable transport per model/view/virtual procedure

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2761: ------------------------------------- IMO, using the "mapped-role@security-domain" is better way of defining it. Right now Teiid defaulting that value to given transport's security-domain, this makes it explicit and allows more cross security-domain entries. > Enable/disable transport per model/view/virtual procedure > --------------------------------------------------------- > > Key: TEIID-2761 > URL: https://issues.jboss.org/browse/TEIID-2761 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.5 > Reporter: Patrick Deenen > Assignee: Steven Hawkins > Fix For: 8.7 > > > It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services). > One may want to have access to virtual procedures only by Odata for example. -- 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 Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ] Johnathon Lee resolved TEIID-2795. ---------------------------------- Resolution: Done Committed r4625 to https://svn.jboss.org/repos/teiid/branches/7.7.x > 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: Johnathon Lee > Fix For: 7.7.9 > > Attachments: TEIID-2795.patch > > > 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 Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2795: --------------------------------- Fix Version/s: 7.7.9 > 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: Johnathon Lee > Fix For: 7.7.9 > > Attachments: TEIID-2795.patch > > > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014