Apache Geode board report (DRAFT FOR YOUR REVIEW)

2020-05-07 Thread Dave Barnes
Please respond with changes & additions by COB Friday, May 8. See the "bragging points" at the bottom. Publish and Prevail, y'all! Thanks, Dave ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, co

Re: [DISCUSS] Geode Redis API Improvements

2020-05-07 Thread Darrel Schneider
Experimental features are subject to change or removal. No guarantees are made of backwards compatibility. On Thu, May 7, 2020 at 2:53 PM Donal Evans wrote: > Looks good to me. Fixing broken implementation and providing reliable HA > can only be a good thing. My only concern is the backwards com

Re: [DISCUSS] Geode Redis API Improvements

2020-05-07 Thread Donal Evans
Looks good to me. Fixing broken implementation and providing reliable HA can only be a good thing. My only concern is the backwards compatibility issue, but I don't know if we make any guarantees regarding that for experimental features, so it may be a non-issue. On Thu, May 7, 2020 at 8:35 AM Ray

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Ju@N
Thanks all for the replies. The fix has been back ported to support/1.12 [1] and support/1.13 [2] already. Best regards. [1]: https://github.com/apache/geode/commit/5a3a24e4724ba7278bc2f9482d25302ede964319 [2]: https://github.com/apache/geode/commit/193a98a1975a2df417e50755d7badd320c7cb8af On Th

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Dave Barnes
Looks like you have the votes, Juan. Go ahead and contribute this fix to support/1.13 and support/1.12. Thanks, Dave Geode 1.13 release manager On Thu, May 7, 2020 at 10:44 AM Eric Shu wrote: > +1 > > > On Thu, May 7, 2020 at 10:22 AM Jianxia Chen wrote: > > > +1 > > > > On Thu, May 7, 2020 at

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Eric Shu
+1 On Thu, May 7, 2020 at 10:22 AM Jianxia Chen wrote: > +1 > > On Thu, May 7, 2020 at 7:47 AM Ju@N wrote: > > > Hello devs, > > > > I'd like to propose bringing GEODE-8071 [1] to the *support/1.12* and > > *support/1.13* branches. > > The bug was introduced in Geode 1.8.0 and, long story shor

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Jianxia Chen
+1 On Thu, May 7, 2020 at 7:47 AM Ju@N wrote: > Hello devs, > > I'd like to propose bringing GEODE-8071 [1] to the *support/1.12* and > *support/1.13* branches. > The bug was introduced in Geode 1.8.0 and, long story short, prevents > locators from gracefully shutting down whenever a rebalance o

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Owen Nichols
+1 > On May 7, 2020, at 10:11 AM, Jinmei Liao wrote: > > +1 > > On Thu, May 7, 2020 at 9:26 AM Donal Evans wrote: > >> +1 >> >> From: Dick Cavender >> Sent: Thursday, May 7, 2020 8:52 AM >> To: dev@geode.apache.org >> Subject: Re: [PROPOSAL]: GEODE-8071 to s

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Jinmei Liao
+1 On Thu, May 7, 2020 at 9:26 AM Donal Evans wrote: > +1 > > From: Dick Cavender > Sent: Thursday, May 7, 2020 8:52 AM > To: dev@geode.apache.org > Subject: Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13 > > +1 > > On Thu, May 7, 2020 at 7:47 AM J

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Donal Evans
+1 From: Dick Cavender Sent: Thursday, May 7, 2020 8:52 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13 +1 On Thu, May 7, 2020 at 7:47 AM Ju@N wrote: > Hello devs, > > I'd like to propose bringing GEODE-8071 [1]

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Dick Cavender
+1 On Thu, May 7, 2020 at 7:47 AM Ju@N wrote: > Hello devs, > > I'd like to propose bringing GEODE-8071 [1] to the *support/1.12* and > *support/1.13* branches. > The bug was introduced in Geode 1.8.0 and, long story short, prevents > locators from gracefully shutting down whenever a rebalance o

Re: Update of SSLParameterExtension interface

2020-05-07 Thread Jacob Barrett
I have some concerns with using Properties in public APIs. The use of Properties is not strongly typed. I can’ tell from one property to the next what the type is. I can’t get compile time errors is the type is wrong. I don’t know what goes into a Property based on the interface or any magic and

Pull Requests

2020-05-07 Thread Jacob Barrett
Hey All, While it appears to be common practice for us to all pay attention to and burn down pull requests on the primary apache/geode repository. It would be really great if you all could take time to look at some of our other repositories and help out with PRs. The apache/geode-native reposit

Re: RFC - Logging to Standard Out

2020-05-07 Thread Jacob Barrett
Done! > On May 5, 2020, at 4:35 PM, Aaron Lindsey wrote: > > I think this could be moved to "In Development" since there is consensus. I > created a JIRA for it: https://issues.apache.org/jira/browse/GEODE-8077

Re: [DISCUSS] Geode Redis API Improvements

2020-05-07 Thread Raymond Ingles
Just a quick nudge - we set a deadline for comments for tomorrow. Anyone had a chance to look this over yet? Thanks! On Thu, Apr 30, 2020 at 2:09 PM Raymond Ingles wrote: > Hi all, > > The current Redis API support in Geode has been marked experimental for a > couple years and has several bugs a

[PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

2020-05-07 Thread Ju@N
Hello devs, I'd like to propose bringing GEODE-8071 [1] to the *support/1.12* and *support/1.13* branches. The bug was introduced in Geode 1.8.0 and, long story short, prevents locators from gracefully shutting down whenever a rebalance operation is launched from gfsh (doesn't matter whether the r

Re: About Geode rolling downgrade

2020-05-07 Thread Alberto Gomez
Hi again, Considering Geode does not support online rollback for the time being and since we have the need to rollback even a standalone system, we were thinking on a procedure to downgrade Geode cluster tolerating downtime, but without a need to: * spin another cluster to sync from, *