Build failed in Jenkins: Geode-nightly #945

2017-09-05 Thread Apache Jenkins Server
See -- [...truncated 218.29 KB...] --- * What went wrong: Execution failed for task ':geode-assembly:integrationTest'. > There were failing tests. See the report at: >

Build failed in Jenkins: Geode-nightly-flaky #113

2017-09-05 Thread Apache Jenkins Server
See -- Started by upstream project "Geode-nightly" build number 945 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on H14

Re: [VOTE] Apache Geode release - v1.2.1 RC2

2017-09-05 Thread Galen O'Sullivan
Looks like the repos have moved to gitbox. It should be as simple as changing the three git-wip-us.apache.org links to gitbox.apache.org . On Tue, Sep 5, 2017 at 5:01 PM, Karen Miller wrote: > A guarded +1 based on limited testing of the RC: > > Built the Geode RC from

Re: Review Request 62088: GEODE-3249 Validate internal client/server messages

2017-09-05 Thread Galen O'Sullivan
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/62088/#review184608 --- I prefer config option names to be as unambiguous as possible. I

Re: [VOTE] Apache Geode release - v1.2.1 RC2

2017-09-05 Thread Karen Miller
A guarded +1 based on limited testing of the RC: Built the Geode RC from source. Built and ran the RC (partitioned) geode-example against the Geode RC, which means I ran gfsh, started a locator and some servers with gfsh, did some puts and gets via the API, and ran a query and other commands via

Recording of Geode Clubhouse - Lucene Text Search in Geode 1.2

2017-09-05 Thread Jagdish Mirani
Hi All: If you missed our Geode Clubhouse webinar at which Diane Hardman of Pivotal Product Management covers the Lucene Text Search feature in Geode 1.2, then you can still access a recording of this webinar: https://www.youtube.com/watch?v=9JWX_S8yWQA=14=PL62pIycqXx-R6IxZBlFyD_gq1EwT5CGE- As

Re: Review Request 62088: GEODE-3249 Validate internal client/server messages

2017-09-05 Thread Udo Kohlmeyer
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/62088/#review184602 --- Ship it! Ship It! - Udo Kohlmeyer On Sept. 5, 2017, 5:57

Re: [VOTE] Apache Geode release - v1.2.1 RC1

2017-09-05 Thread Jacob Barrett
If this change is for security reasons I think it should be introduced in whatever way is necessary mitigate any security issues by default. > On Sep 5, 2017, at 3:31 PM, Anthony Baker wrote: > > Ok, I understand and agree this approach, even though it means spinning >

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

2017-09-05 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #669 was successful. --- Scheduled 2029 tests in total. https://build.spring.io/browse/SGF-NAG-669/ -- This

Re: [VOTE] Apache Geode release - v1.2.1 RC1

2017-09-05 Thread Anthony Baker
Ok, I understand and agree this approach, even though it means spinning another RC. Other thoughts? Anthony > On Sep 5, 2017, at 11:04 AM, Michael Stolz wrote: > > GEODE-3249 is a breaking change to the client/server protocol, but it has a > property that can override

Re: Review Request 62088: GEODE-3249 Validate internal client/server messages

2017-09-05 Thread Alexander Murmann
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/62088/#review184591 --- Ship it! I am rather disappointed that this required no test

Re: Review Request 61895: GEDOE-3516: TXManagerImpl.tryResume call may add itself again into the waiting thread queue

2017-09-05 Thread Eric Shu
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61895/#review184582 ---

Re: [VOTE] Apache Geode release - v1.2.1 RC1

2017-09-05 Thread Michael Stolz
GEODE-3249 is a breaking change to the client/server protocol, but it has a property that can override whether or not to turn the breaking change on. The plan was to release Geode 1.2.1 with the breaking change turned on, but I spent a lot of time thinking about this over the weekend, and I came

Re: Review Request 62088: GEODE-3249 Validate internal client/server messages

2017-09-05 Thread Hitesh Khamesra
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/62088/#review184565 --- Ship it! Ship It! - Hitesh Khamesra On Sept. 5, 2017, 5:57

Review Request 62088: GEODE-3249 Validate internal client/server messages

2017-09-05 Thread Bruce Schuchardt
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/62088/ --- Review request for geode, Alexander Murmann, Galen O'Sullivan, Hitesh Khamesra,

Re: Indxes and hints

2017-09-05 Thread Jason Huynh
Not exactly sure the reasoning to use only one index only, other than it was a performance choice at the time. Are you sure you are seeing both indexes being used? In Geode, with the following query,select * from /region p where p.ID > 0 AND p.status = 'on' ORDER BY ID, I only see one of the

Re: git repo is gone

2017-09-05 Thread Bruce Schuchardt
That worked - thank you! On 9/1/17 4:18 PM, Jacob Barrett wrote: Have you registered your github account with Apache’s directory? Log into the Apache ID portal and add your github. You’ll have access after the next sync. On Sep 1, 2017, at 4:16 PM, Bruce Schuchardt

RE: continuous query internal mechanism questions

2017-09-05 Thread Roi Apelker
Hi, After quite some time, I was getting back to this issue where something seems wrong with the registration of CQ. In the java client I see that the code goes to a method called " executeCqOnRedundantsAndPrimary " which seems indeed to go to all the relevant servers and register the CQ.