Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/172

Geode unit tests 'develop/DistributedTest' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/171

Spring for Apache Geode Announcements...

[John Blum]

Greetings Apache Geode Community-

It is my pleasure to follow-up with several announcements and releases
concerning the Apache Geode ecosystem from the Spring portfolio.


1. First, we moved 2 versions since my last announcement [1] to *Spring
Data for Apache Geode* *2.0.5.RELEASE* (*Kay-SR5*).

1.1. The official release announcement is here [2].

1.2. See the changelog [3] for additional details.  Specifically look at
the changes in versions 2.0.4.RELEASE and 2.0.5.RELEASE.

1.3. One of the more interesting changes to SDG is the ability to register
QueryPostProcessors to process (OQL) queries generated from *Repository*
query methods when using the convention. See SDG's Reference Documentation
for more information [4].


2. Second, we have already released our first milestone for *Spring Data*
*Lovelace* [5], which, of course, includes *Spring Data for Apache Geode*
*2.1.0.M1*.  You may remember [6], I have many things planned this year for
the next few versions of *Spring Data for Apache Geode*.


3. Third, *Spring Session for Apache Geode* has also jumped to versions
since my last announcement [7] to *2.0.2.RELEASE*.  This release primarily
consist of version updates and is based on *Spring Session core*
2.0.2.RELEASE.


4. Lastly, it was just announced [8] that *Spring Boot 2.0* went GA, so is
now at version *2.0.0.RELEASE*.  \o/  .oO(Yay!)

It's been a long haul but the timing is perfect since I am only a few weeks
away from releasing the first milestone of *Spring Boot for Apache Geode*.
I have been making good progress on this project [9] and I essentially have
only testing, documentation and examples left to complete.

* Of course, it will be based on the newly minted *Spring Boot*
2.0.0.RELEASE, and will cover many things, such as, but not limited to,
providing an auto-configured ClientCache instance OOTB that will
automatically authenticate when you push your *Spring Boot*, ClientCache
apps to PCF when interfacing to PCC.

* Using Apache Geode as a caching provider in *Spring's Cache Abstraction*
will be enabled by default as will SDG *Repositories*.

* PDX is the default serialization format and there will be NO need to
explicitly register a PdxSerializer to identify and serialize your
application domain object types; it will just work as it should!

* Annotated Continuous Query Listener, POJO-based method callbacks will be
enabled by default; so just start by declaring your CQs and you will
receive events. Remember this wicked cool feature [10].  Example here [11].

* Interface-based Function Executions are also enabled by default.  Just
declare your Apache Geode Functions using an interface and SDG combined
with the new *Spring Boot* support will handle the rest.  You just invoke
your Function like any other POJO method, in a clean and Object-Oriented
way!


So many exciting things planned in *Spring Boot for Apache Geode*, I look
forward to rolling this out soon and getting your feedback.  Stay tuned!

Well, that is all for now folks.


Regards,
-- 
-John

[1] http://markmail.org/message/mhdsrml6ixhggecj
[2] https://spring.io/blog/2018/02/28/spring-data-kay-sr5-released
[3]
https://docs.spring.io/spring-data/geode/docs/2.0.5.RELEASE/changelog.txt
[4]
https://docs.spring.io/spring-data/geode/docs/current/reference/html/#gemfire-repositories.queries.post-processing
[5] https://spring.io/blog/2018/02/06/spring-data-lovelace-m1-released
[6] http://markmail.org/message/cneo6dhl6tvu2ib5
[7]
http://markmail.org/message/ssk5jgoh344cyf54?q=list:org%2Eapache%2Egeode%2Euser+order:date-backward+from:%22John+Blum%22=1
[8] https://spring.io/blog/2018/03/01/spring-boot-2-0-goes-ga
[9] https://github.com/spring-projects/spring-boot-data-geode
[10]
https://docs.spring.io/spring-data/geode/docs/current/reference/html/#bootstrap-annotation-config-continuous-queries
[11]
https://github.com/jxblum/contacts-application/tree/master/continuous-query-example

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #843 was SUCCESSFUL (with 2378 tests)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #843 was successful.
---
Scheduled
2380 tests in total.

https://build.spring.io/browse/SGF-NAG-843/





--
This message is automatically generated by Atlassian Bamboo

Geode unit tests completed in 'develop/IntegrationTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/244

Re: Next release: 1.5.0

[Swapnil Bawaskar]

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: Row-Level security with key as a regex

[Jens Deppe]

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.
>

Row-Level security with key as a regex

[Nilkanth Patel]

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.