@Mark, looks like we got enough eyeballs on this. Can you submit?
Thanks,
Anthony
> On Aug 9, 2018, at 4:03 PM, Dave Barnes wrote:
>
> +1 LGTM
>
> On Thu, Aug 9, 2018 at 3:57 PM, Kirk Lund wrote:
>
>> +1 looks good!
>>
>> On Thu, Aug 9, 2018 at 3:46 PM, Anthony Baker wrote:
>>
>>> This
I see those tests in the main. I’m correcting those in an upcoming pr. Looks
like they are tests for shared test classes so they will go in
geode-dunit/src/test.
I’ll update this email after I burn through them.
> On Aug 9, 2018, at 3:56 PM, Kirk Lund wrote:
>
> We now have geode-junit and ge
+1 LGTM
On Thu, Aug 9, 2018 at 3:57 PM, Kirk Lund wrote:
> +1 looks good!
>
> On Thu, Aug 9, 2018 at 3:46 PM, Anthony Baker wrote:
>
> > This is a bit late so please review asap. Thanks!
> >
> > ## Description:
> > Apache Geode provides a database-like consistency model, reliable
> > transacti
+1 looks good!
On Thu, Aug 9, 2018 at 3:46 PM, Anthony Baker wrote:
> This is a bit late so please review asap. Thanks!
>
> ## Description:
> Apache Geode provides a database-like consistency model, reliable
> transaction processing and a shared-nothing architecture to maintain
> very low laten
We now have geode-junit and geode-dunit modules which contain the testing
frameworks and rules that we've been using in Geode tests. These are also
being published to maven and have release jars. Yay!
There is some code however that was moved from src/test of various modules
into the src/main of b
+1, Looks good to me!
-Dan
On Thu, Aug 9, 2018 at 3:53 PM, Joey McAllister
wrote:
> Looks great, Anthony! Thanks for putting this together!
>
> My only note is to capitalize "YouTube" in the reference to Addison's video
> series.
>
> Best,
> Joey
>
> On Thu, Aug 9, 2018 at 3:46 PM Anthony Baker
Looks great, Anthony! Thanks for putting this together!
My only note is to capitalize "YouTube" in the reference to Addison's video
series.
Best,
Joey
On Thu, Aug 9, 2018 at 3:46 PM Anthony Baker wrote:
> This is a bit late so please review asap. Thanks!
>
> ## Description:
> Apache Geode pro
---
Spring Data GemFire > Nightly-ApacheGeode > #1004 was successful.
---
Scheduled
2425 tests in total.
https://build.spring.io/browse/SGF-NAG-1004/
--
Thi
This is a bit late so please review asap. Thanks!
## Description:
Apache Geode provides a database-like consistency model, reliable
transaction processing and a shared-nothing architecture to maintain
very low latency performance with high concurrency processing.
## Issues:
There are no issues r
let me see if my understanding is correct: if ssl-enabled-component is
none, then we would accept non-ssl connections, no ssl context will be
used. if ssl-enabled-component is something other than "none", but we don't
specify any other ssl-* configurations, then we use the default ssl context
provi
This should be fixed now.
On Thu, Aug 9, 2018 at 10:35 AM, Kirk Lund wrote:
> Looks like I introduced a bad commit. I'm working on reverting it. Sorry
> for the inconvenience!
>
Looks like I introduced a bad commit. I'm working on reverting it. Sorry
for the inconvenience!
> On Aug 9, 2018, at 10:05 AM, Jacob Barrett wrote:
>
>
>
> On Aug 9, 2018, at 9:42 AM, Anthony Baker wrote:
>
>>>
>>>
>>> I would like to also get consensus on defaulting GEODE's behavior to always
>>> use default SSL context instead of introducing a new parameter
>>> 'ssl-use-default-s
On Aug 9, 2018, at 9:42 AM, Anthony Baker wrote:
>>
>>
>> I would like to also get consensus on defaulting GEODE's behavior to always
>> use default SSL context instead of introducing a new parameter
>> 'ssl-use-default-sslcontext'. If user's have specified any existing ssl-*
>> props then t
Windows jobs are live and run in parallel to existing jobs.
On Wed, Aug 8, 2018 at 11:49 AM Dan Smith wrote:
> +1 for in parallel.
>
> -Dan
>
> On Wed, Aug 8, 2018 at 11:37 AM, Jacob Barrett
> wrote:
>
> > Parallel
> >
> > > On Aug 8, 2018, at 11:32 AM, Sai Boorlagadda <
> sai_boorlaga...@apach
>
>
> I would like to also get consensus on defaulting GEODE's behavior to always
> use default SSL context instead of introducing a new parameter
> 'ssl-use-default-sslcontext'. If user's have specified any existing ssl-*
> props then the current implementation is exercised (ie to configure the
16 matches
Mail list logo