Re: Row-Level security with key as a regex
Jens, Thanks for your reply, now i get this.
As you said, implementing the required authorization behavior in
SecurityManager.authorize() callback is way to go.
Thanks,
Nilkanth.
On Thu, Mar 1, 2018 at 7:32 PM, Jens Deppe wrote:
> Hi Nilkanth,
>
> It's basically up to the provided SecurityManager how to handle the
> ResourcePermission passed into it.
>
> So in your implementation could be as simple as:
>
> if (rp.getKey() != null && rp.getKey().contains("system") {...}
>
> Are you perhaps looking at a specific SecurityManager implementation?
>
> --Jens
>
> On Thu, Mar 1, 2018 at 3:06 AM, Nilkanth Patel
> wrote:
>
> > Hi Team,
> >
> > I am exploring row-level security with Geode and observed that exact key
> > has to be provided in security configuration (for example:
> > DATA:READ:MyRegion:*system*).
> >
> > Is there any way to provide Key as a regex (*admin*) ..? I want to
> achieve
> > row-level security on all keys containing *system* as a sub-string.
> > Providing each key in security-config is very cumbersome.
> >
> > -Nilkanth.
> >
>
Geode unit tests completed in 'release-1.5.0/IntegrationTest' with non-zero exit code
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/IntegrationTest/builds/1
[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #847 was SUCCESSFUL (with 2378 tests)
--- Spring Data GemFire > Nightly-ApacheGeode > #847 was successful. --- Scheduled 2380 tests in total. https://build.spring.io/browse/SGF-NAG-847/ -- This message is automatically generated by Atlassian Bamboo
Re: Next release: 1.5.0
Could you make the pipeline public? Anthony > On Mar 5, 2018, at 12:46 PM, Sean Goller wrote: > > 1.5.0 pipeline is up and running, please take a look at it and let the list > know if there are problems. > > https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0 > > On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker wrote: > >> LGTM >> >>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar >> wrote: >>> >>> Thanks Dave! >>> >>> All, I have created a release branch ( >>> https://github.com/apache/geode/tree/release/1.5.0) Please review. >>> >>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes wrote: >>> Status on the 3 doc issues: GEODE-4737 / GEODE-3915: JSON args in gfsh - Done GEODE-4101: redirect-output - Done GEODE-3948: client timeout - Done On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar >> wrote: > I will take up the release management task for 1.5.0 > > On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes >> wrote: > >> Status on the 3 doc issues: >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered >> GEODE-4101: redirect-output - Dave, in process, on track >> GEODE-3948: client timeout - Dave, in process. Probably on track - >> will >> keep you posted >> >> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker > wrote: >> >>> Just checking in as we’re approaching the end of February. We’ve >> finished >>> around 200 issues and enhancements with 3 documentation updates open > [1]. >>> Is this a good time for another release? >>> >>> Any takers to do the release management tasks for 1.5.0? >>> >>> Anthony >>> >>> [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395 < >>> https://issues.apache.org/jira/projects/GEODE/versions/12342395> >>> >>> On Feb 7, 2018, at 1:56 PM, Anthony Baker wrote: Hi all, Nice work on getting the 1.4.0 release out the door! Next up is > 1.5.0. >>> Any one want to volunteer for release manager? If you haven’t done > this >>> before and would like to try, please review [1]. I’ve been advocating for more frequent releases. I’d love see a > March >>> release—which means we would need to be ready to cut the release branch >> in >>> early March. Thoughts? Anthony [1] >> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src= >>> contextnavpagetreemode < >> https://cwiki.apache.org/confluence/display/GEODE/ >>> Release+Steps?src=contextnavpagetreemode> >>> >>> >> > >> >>
Re: Next release: 1.5.0
1.5.0 pipeline is up and running, please take a look at it and let the list know if there are problems. https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0 On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker wrote: > LGTM > > > On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar > wrote: > > > > Thanks Dave! > > > > All, I have created a release branch ( > > https://github.com/apache/geode/tree/release/1.5.0) Please review. > > > > On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes wrote: > > > >> Status on the 3 doc issues: > >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Done > >> GEODE-4101: redirect-output - Done > >> GEODE-3948: client timeout - Done > >> > >> > >> On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar > > >> wrote: > >> > >>> I will take up the release management task for 1.5.0 > >>> > >>> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes > wrote: > >>> > Status on the 3 doc issues: > GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered > GEODE-4101: redirect-output - Dave, in process, on track > GEODE-3948: client timeout - Dave, in process. Probably on track - > will > keep you posted > > On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker > >>> wrote: > > > Just checking in as we’re approaching the end of February. We’ve > finished > > around 200 issues and enhancements with 3 documentation updates open > >>> [1]. > > Is this a good time for another release? > > > > Any takers to do the release management tasks for 1.5.0? > > > > Anthony > > > > [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395 > >> < > > https://issues.apache.org/jira/projects/GEODE/versions/12342395> > > > > > >> On Feb 7, 2018, at 1:56 PM, Anthony Baker > >> wrote: > >> > >> Hi all, > >> > >> Nice work on getting the 1.4.0 release out the door! Next up is > >>> 1.5.0. > > Any one want to volunteer for release manager? If you haven’t done > >>> this > > before and would like to try, please review [1]. > >> > >> I’ve been advocating for more frequent releases. I’d love see a > >>> March > > release—which means we would need to be ready to cut the release > >> branch > in > > early March. > >> > >> Thoughts? > >> > >> Anthony > >> > >> [1] > https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src= > > contextnavpagetreemode < > https://cwiki.apache.org/confluence/display/GEODE/ > > Release+Steps?src=contextnavpagetreemode> > >> > > > > > > >>> > >> > >
Errored: jinmeiliao/geode#245 (cliUtil2 - ee4dddc)
Build Update for jinmeiliao/geode - Build: #245 Status: Errored Duration: 10 minutes and 32 seconds Commit: ee4dddc (cliUtil2) Author: Jinmei Liao Message: GEODE-4735: get rid of Cache.getInstance call from CliUtils and GfshCommand * all functions in CliUtils take cache as a parameter if needs one. * InternalCache is injected to the command when the command is initialized. View the changeset: https://github.com/jinmeiliao/geode/compare/be8140dadb38^...ee4dddcc569e View the full build log and details: https://travis-ci.org/jinmeiliao/geode/builds/349455118?utm_source=email&utm_medium=notification -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Re: Next release: 1.5.0
LGTM > On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar wrote: > > Thanks Dave! > > All, I have created a release branch ( > https://github.com/apache/geode/tree/release/1.5.0) Please review. > > On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes wrote: > >> Status on the 3 doc issues: >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Done >> GEODE-4101: redirect-output - Done >> GEODE-3948: client timeout - Done >> >> >> On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar >> wrote: >> >>> I will take up the release management task for 1.5.0 >>> >>> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes wrote: >>> Status on the 3 doc issues: GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered GEODE-4101: redirect-output - Dave, in process, on track GEODE-3948: client timeout - Dave, in process. Probably on track - will keep you posted On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker >>> wrote: > Just checking in as we’re approaching the end of February. We’ve finished > around 200 issues and enhancements with 3 documentation updates open >>> [1]. > Is this a good time for another release? > > Any takers to do the release management tasks for 1.5.0? > > Anthony > > [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395 >> < > https://issues.apache.org/jira/projects/GEODE/versions/12342395> > > >> On Feb 7, 2018, at 1:56 PM, Anthony Baker >> wrote: >> >> Hi all, >> >> Nice work on getting the 1.4.0 release out the door! Next up is >>> 1.5.0. > Any one want to volunteer for release manager? If you haven’t done >>> this > before and would like to try, please review [1]. >> >> I’ve been advocating for more frequent releases. I’d love see a >>> March > release—which means we would need to be ready to cut the release >> branch in > early March. >> >> Thoughts? >> >> Anthony >> >> [1] https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src= > contextnavpagetreemode < https://cwiki.apache.org/confluence/display/GEODE/ > Release+Steps?src=contextnavpagetreemode> >> > > >>> >>
Geode unit tests completed in 'develop/IntegrationTest' with non-zero exit code
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/251
EvictionDUnitTest and PRCacheListenerWithInterestPolicyAllInvocationTest
I saw these fail in a precheckin. I'll dig into these and see if I can fix them. :geode-core:distributedTest Do not allow more than 4 test workers org.apache.geode.internal.cache.eviction.EvictionDUnitTest > testDummyInlineNCentralizedEviction FAILED java.lang.AssertionError: expected:<8> but was:<6> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.apache.geode.internal.cache.eviction.EvictionTestBase.validateNoOfEvictions(EvictionTestBase.java:403) at org.apache.geode.internal.cache.eviction.EvictionDUnitTest.testDummyInlineNCentralizedEviction(EvictionDUnitTest.java:49) org.apache.geode.internal.cache.PRCacheListenerWithInterestPolicyAllInvocationTest > afterDestroyIsInvokedInEveryMember[0: redundancy=0] FAILED java.lang.AssertionError: Expected: not <172.17.0.2(1):32770> but: was <172.17.0.2(1):32770> org.apache.geode.internal.cache.PRCacheListenerWithInterestPolicyAllInvocationTest > afterInvalidateIsInvokedInEveryMember[0: redundancy=0] FAILED java.lang.AssertionError: Expected: not <172.17.0.2(1):32770> but: was <172.17.0.2(1):32770> org.apache.geode.internal.cache.PRCacheListenerWithInterestPolicyAllInvocationTest > afterDestroyIsInvokedInEveryMember[1: redundancy=3] FAILED java.lang.AssertionError: Expected: not <172.17.0.2(1):32770> but: was <172.17.0.2(1):32770> org.apache.geode.internal.cache.PRCacheListenerWithInterestPolicyAllInvocationTest > afterUpdateIsInvokedInEveryMember[1: redundancy=3] FAILED java.lang.AssertionError: Expected: <172.17.0.2(1):32770> but: was <172.17.0.2(157):32773> java.lang.AssertionError: Expected: <172.17.0.2(1):32770> but: was <172.17.0.2(157):32773> java.lang.AssertionError: Expected: <172.17.0.2(1):32770> but: was <172.17.0.2(157):32773> org.apache.geode.internal.cache.PRCacheListenerWithInterestPolicyAllInvocationTest > afterInvalidateIsInvokedInEveryMember[1: redundancy=3] FAILED java.lang.AssertionError: Expected: not <172.17.0.2(1):32770> but: was <172.17.0.2(1):32770> org.apache.geode.internal.cache.PRCacheListenerWithInterestPolicyAllInvocationTest > afterCreateIsInvokedInEveryMember[1: redundancy=3] FAILED java.lang.AssertionError: Expected: <172.17.0.2(1):32770> but: was <172.17.0.2(175):32774> java.lang.AssertionError: Expected: <172.17.0.2(1):32770> but: was <172.17.0.2(175):32774> java.lang.AssertionError: Expected: <172.17.0.2(1):32770> but: was <172.17.0.2(175):32774>
