[jira] [Commented] (GEODE-5074) REST dev client should not access or modify internal regions

2018-11-15 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16688794#comment-16688794
 ] 

ASF subversion and git services commented on GEODE-5074:


Commit 320b191c8286bb52be9cf93ccdbacd3e0a9981df in geode's branch 
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=320b191 ]

GEODE-5074 REST dev client should not access or modify internal regions

The Developer REST API was accessing a raw cache for all operations.
I've switched it to use a filtered InternalCacheForClientAccess cache
instead.  I added a new method to the filtered cach to allow the REST
code to get its Query Store region.


> REST dev client should not access or modify internal regions
> 
>
> Key: GEODE-5074
> URL: https://issues.apache.org/jira/browse/GEODE-5074
> Project: Geode
>  Issue Type: Sub-task
>  Components: rest (dev)
>Reporter: Darrel Schneider
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> When a request is processed from a REST dev client that contains a region 
> name, then getApplicationRegion should be used instead of getRegion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5074) REST dev client should not access or modify internal regions

2018-11-15 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16688657#comment-16688657
 ] 

ASF subversion and git services commented on GEODE-5074:


Commit 97a01fda66f5e5cdec1b793a94a088954fddde25 in geode's branch 
refs/heads/feature/GEODE-5074 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=97a01fd ]

GEODE-5074 REST dev client should not access or modify internal regions

Implementing Jinmei's idea of adding getQueryStore to InternalCache
and having only one cache access method in CacheProvider.


> REST dev client should not access or modify internal regions
> 
>
> Key: GEODE-5074
> URL: https://issues.apache.org/jira/browse/GEODE-5074
> Project: Geode
>  Issue Type: Sub-task
>  Components: rest (dev)
>Reporter: Darrel Schneider
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When a request is processed from a REST dev client that contains a region 
> name, then getApplicationRegion should be used instead of getRegion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5074) REST dev client should not access or modify internal regions

2018-11-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/GEODE-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687272#comment-16687272
 ] 

ASF subversion and git services commented on GEODE-5074:


Commit f886b63594e3cafc2757d272a8c6f597b8948ff2 in geode's branch 
refs/heads/feature/GEODE-5074 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f886b63 ]

GEODE-5074 REST dev client should not access or modify internal regions

The Developer REST API was accessing a raw cache for all operations.
I've switched it to use a filtered InternalCacheForClientAccess cache
instead for most operations.  It needed to have the unfiltered cache in
order to find the __ParameterizedQueries__ region for accessing saved
queries.


> REST dev client should not access or modify internal regions
> 
>
> Key: GEODE-5074
> URL: https://issues.apache.org/jira/browse/GEODE-5074
> Project: Geode
>  Issue Type: Sub-task
>  Components: rest (dev)
>Reporter: Darrel Schneider
>Assignee: Bruce Schuchardt
>Priority: Major
>
> When a request is processed from a REST dev client that contains a region 
> name, then getApplicationRegion should be used instead of getRegion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)