Re: [VOTE] Apache Geode 1.9.1 RC1 (new vote)

Final SD[G] Moore-RELEASE/2.2 GA is (tentatively) scheduled for Thurs, Sept 19th. Even still, any SD[G] Moore service release post GA (e.g. 2.2.1, 2.2.2, ..., 2.2.N) can pick up any patch release of Apache Geode 1.9.x (e.g. 1.9.1, 1.9.2, ..., 1.9.N). Additionally, SBDG 1.2 cannot go GA before *Sp

Re: [VOTE] Apache Geode 1.9.1 RC1

FWIW, I don't think 1.9.1 clients (or any combination of patch versions) should be incompatible with servers 1.9.patch-1 (e.g. 1.9.0). IMO, that would be very bad! major.minor client/servers, regardless of patch versions, should remain interoperable. On Thu, Aug 29, 2019 at 11:41 AM Owen Nichols

Re: [VOTE] Apache Geode 1.9.1 RC1 (new vote)

+1 On Thu, Aug 29, 2019 at 9:41 AM Kirk Lund wrote: > +1 (just in case my vote counts) > > On Thu, Aug 29, 2019 at 9:02 AM Kirk Lund wrote: > > > Hello Geode dev community, > > > > This is a release candidate for Apache Geode, version 1.9.1.RC1. > > Thanks to all the community members for their

Re: [VOTE] Apache Geode 1.9.1 RC1

+1 On Wed, Aug 28, 2019 at 2:51 PM Dan Smith wrote: > I missed this vote email as well - if we reopen the vote I'll cast one. I > don't really have much context on why we want a 1.9.1 but I'm happy to > double check the bits. > > One comment on this RC - I noticed that we bumped the ordinal in >

Re: [DISCUSS] Release Geode 1.9.1 with logging improvements

; > > -Owen > > > > > >> On Aug 18, 2019, at 7:52 AM, Anthony Baker wrote: > >> > >> Yep. Get a release manager, identify and cherry pick all the changes, > then do the release. > >> > >> Anthony > >> > >>> On Aug 1

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

FTR, I am not opposed to *Naba's* idea either. +1 I kind of like the idea of having a global, cache-wide call that can coordinate the background initialization/processing of all other Geode objects that have lifecycle processes starting in the background (e.g. Gateways, AEQs, etc). On Tue, A

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

After talking with *Alexander* this morning (and taking *Mike's* concerns into consideration), and to not adversely affect users/customers today, I think... 1). AEQ's can (should) have a configuration setting to "manually" start the queue's background processor (i.e. Thread) to begin processing (e

Re: Proposal to Include GEODE-7079 in 1.10.0

+1 On Thu, Aug 15, 2019 at 5:30 AM Ju@N wrote: > Hello team, > > I'd like to propose including the *fix [1]* for *GEODE-7079 [2]* in release > 1.10.0. > Long story short: a *NullPointerException* can be continuously thrown > and flood the member's logs if a serial event processor (either > *asyn

Re: [DISCUSS] Geode dependency update process (review by 8/28/2019)

+1 to Nick's proposal! While you cannot always guarantee that a dependency for whatever version, whether a new major, an updated minor or simply a patch release won't introduce problems (regressions, performance issues, or worse, CVEs), it is extremely important to keep dependencies up-to-date, pr

Re: [DISCUSS] Release Geode 1.9.1 with logging improvements

Sorry, corrections below... On Tue, Aug 13, 2019 at 1:54 PM John Blum wrote: > Stated slightly a different way... > > If *SBDG 1.2 *were to be (re)based on *Apache Geode 1.10* directly, then > it would *defy* the dependency on Apache Geode pulled in by SDG Moore/2.2 > (which is

Re: [DISCUSS] Release Geode 1.9.1 with logging improvements

at that time (e.g. 1.10, maybe 1.11) and continue to be upgraded until 2.3 reaches RC status. Cheers, John On Tue, Aug 13, 2019 at 1:45 PM John Blum wrote: > For clarification... > > 1. SBDG 1.1 is the "*current*" development line (on > <https://github.com/spring-

Re: [DISCUSS] Release Geode 1.9.1 with logging improvements

For clarification... 1. SBDG 1.1 is the "*current*" development line (on master [1]); SBDG 1.2 is *not* yet in

Re: Fix for ClassCastException when using Logback for 1.10.0

+1 On Thu, Aug 8, 2019 at 11:31 AM Juan José Ramos wrote: > +1 > > On Thu, Aug 8, 2019 at 7:26 PM Mark Hanson wrote: > > > +1 > > > > I think it is valuable to make life easier for Spring Boot users. > > > > Thanks, > > Mark > > > > > On Aug 8, 2019, at 11:24 AM, Kirk Lund wrote: > > > > > > T

Re: Fix for NPE during forceDisconnect candidate for 1.10.0

+1 for Kirk's changes in 1.10. This will be critical for SD Neuman and SBDG 1.3. On Thu, Aug 8, 2019 at 10:57 AM Owen Nichols wrote: > Hi Kirk and Mark, thank you for bringing your concern. > > Our “critical fixes” rule allows critical fixes to be brought to the > release branch by proposal on

Re: Another change for 1.10.0 release

+1 for Dan's changes. On Thu, Aug 8, 2019 at 10:28 AM Owen Nichols wrote: > Hi Dan, thank you for bringing your concern. > > Our “critical fixes” rule allows critical fixes to be brought to the > release branch by proposal on the dev list [as you have just done]. If > there is consensus from th

Re: [DISCUSS] Time to cut Geode 1.10.0?

A couple of clarifications: 1. First, and most importantly, Pivotal GemFire, specifically (Apache Geode was never officially on *Spring Initializer*, actually) was removed from *Spring Initializer* because *Spring Boot* *1.5.x* has finally reached *End of Life*.Pivotal GemFire existed as an

[RELEASE] Spring for Apache Geode Release & Feature Update

Greetings Apache Geode community- I wanted to take this opportunity and let you all know about the recent developments in the *Spring* ecosystem as it relates to Apache Geode for all you *Spring* users out there. ~~ 1. *Spring Data for Apache Geode* (SDG) Lovelace-SR9 (2.1.9.RELEASE) a

Re: [DISCUSS] Add a test dependency to geode-core - ArchUnit

Of equal importance to uni-directional dependencies in a "modular" design is, classes in package A should not refer directly to classes in package B when A depends on B, or alternately, when module A depends on module B. All interactions are only ever through interfaces and all implementations are

Spring Boot for Apache Geode 1.1.0.M1 Released!

I am pleased to announce the release of *Spring Boot for Apache Geode* (SBDG) 1.1.0.M1. See the official release announcement here: https://spring.io/blog/2019/05/07/spring-boot-for-apache-geode-pivotal-gemfire-1-1-0-m1-released The 1.1 Milestone 1 (M1) release primarily rebases SBDG on the lates

[ANNOUNCE] Spring Boot for Apache Geode 1.0.0.RELEASE Available!

It is my pleasure to announce the first GA release of Spring Boot for Apache Geode (SBDG) 1.0.0.RELEASE. See the official release announcement on spring.io for more details: https://spring.io/blog/2019/05/07/spring-boot-for-apache-geode-pivotal-gemfire-1-0-0-release-available Feedback appreciate

[ANNOUNCE] Spring Boot for Apache Geode 1.0.0.RC2 Available!

I am pleased to announce the release of *Spring Boot for Apache Geode* (SBDG) 1.0.0.RC2. You can read more details in the official release announcement on the spring.io/blog [1]. Given feedback from the Boot team, I decided to postpone the 1.0 GA and push out 1 more release candidate. The final

[ANNOUNCE] Spring Boot for Apache Geode 1.0.0.RC1 Released!

I am pleased to announce the release of *Spring Boot for Apache Geode* (SBDG) 1.0.0.RC1. You can read more details in the official release announcement on the spring.io/blog [1]. I have tentatively scheduled the final GA release of SBDG 1.0 on Monday, April 29th, 2019. Any feedback between now a

Re: How to publish client stats on server

Or alternatively, when using Spring, you can just use @EnableStatistics [1]. [1] https://docs.spring.io/spring-data/geode/docs/current/api/org/springframework/data/gemfire/config/annotation/EnableStatistics.html On Tue, Apr 16, 2019 at 10:44 AM Darrel Schneider wrote: > setPoolStatisticInterval

Re: [Discuss] Removal of Thread Local Connection Pooling

Well articulated and a wise decision; Jake. +1 On Fri, Apr 5, 2019 at 8:24 AM Anthony Baker wrote: > One question: if I’m using thread-local connections ho does that affect > pool sizing? Are thread-local connections included in the overall pool > size or accounted for separately? > > We may w

[ANNOUNCE] Spring Boot for Apache Geode 1.0.0.M4 Available!

Greetings Apache Geode community and Spring users- I am pleased to bring you the *Spring Boot for Apache Geode* (SBDG) 1.0.0.M4 release. You can read the official announcement on the Spring Blog [1] to find out more details. Next up will be SBDG 1.0.0.RC1 followed shortly by a final 1.0.0.GA as w

Re: [DISCUSS] Changing many geode-core dependencies from compile to runtime

If users will be explicitly declaring such dependencies in their applications, then I might also suggest declaring/generating a Maven section in the POM to ensure that the user is getting and using the right version of these dependencies, especially when they don't care about the version (i.e. the

Re: [DISCUSS] Moving redis to a separate module

Definitely a reasonable change. Perhaps, for consistency sake, the same should be applied to Geode's Memcached support? (in another PR). On Tue, Mar 12, 2019 at 4:23 PM Dan Smith wrote: > I created a PR to move our redis support to a separate module. Let me know > what you think: > > https://g

Re: Dependency review for release 1.9.0

y/Java/Extensions /Library/Java/Extensions /Network/Library/Java/Extensions /System/Library/Java/Extensions /usr/lib/java . System Properties: PID = 16326 awt.toolkit = sun.lwawt.macosx.LWCToolkit ... On Thu, Feb 28, 2019 at 10:52 AM John Blum wrote: > As an example of #

Re: Dependency review for release 1.9.0

4-L61 [3] https://github.com/jxblum/spring-session-data-gemfire-serialization-example/blob/master/native-gemfire-server/src/main/java/example/app/gemfire/server/NativeGemFireServerApplication.java On Thu, Feb 28, 2019 at 10:35 AM John Blum wrote: > Dan- > > 2 things: > > 1) Users and

Re: Dependency review for release 1.9.0

vers launched > through gfsh start server unless we provide a way to configure which geode > modules are present on the server's classpath. > > -Dan > > On Thu, Feb 28, 2019 at 10:03 AM John Blum wrote: > > > Well, that just requires that you appropriately declare

Re: Dependency review for release 1.9.0

Well, that just requires that you appropriately declare dependencies with the "optionality" and "scope" (e.g. "compile", "test", "provided", etc). Additionally, Geode modules could selectively pull in the required deps as needed. For example, `geode-lucene` would only pull in the Apache Lucene de

Re: Core tenets of Geode

its fast one day but slow the next. Correctness does not take a day off. If you can only optimize for 1 thing, opt to be correct. Users will silently be thanking you, especially during the holidays when they don't have to worry about keeping the lights on at work. + $0.02 more, -John On Wed, N

Re: Core tenets of Geode

There is only 1 thing I would add to this list is, above all others... 1. Correctness Of course, this ought to go without saying, but do the right thing, always, even at the peril of all the other things combined. It is all too easy to focus on the shinny things (e.g. performance, latency, high

Re: [DISCUSS] Geode packages mustn't span Jigsaw modules

@Galen - If a method is added to a Java interface (e.g. CacheListener), then classes implementing the interface must define the method, or a compile error will occur. This is true in the case where 1) the class implements CacheListener directly rather than extending CacheListenerAdapter and 2) whe

Re: [DISCUSS] Geode packages mustn't span Jigsaw modules

*> Most of these are in internal packages, which means we can change the package of these classes without breaking users.* I don't agree with this. Some functionality in Geode required by an application, or framework, is only available in an "internal" package, unfortunately. This has to do with

Re: [DISCUSS] Geode packages mustn't span Jigsaw modules

I need more time to think about this clearly (currently juggling multiple things), but I would say this... I don't think there should be "internal" APIs, as in o.a.g.*.internal. There are only APIs/SPIs and implementations, period. If you want to maintain an API as internal, then you should prope

Re: Questions about Poms and Publishing

he native Gradle DSL > > https://docs.gradle.org/current/userguide/managing_transitive_dependencies.html > as an *eventual* replacement for the dependency-management-plugin you > reference? > > On Tue, Nov 13, 2018 at 9:09 AM John Blum wrote: > > > If you'd like Maven dep

Re: Questions about Poms and Publishing

If you'd like Maven dependencyManagement like behavior in Gradle, then you should have a look at... https://github.com/spring-gradle-plugins/dependency-management-plugin -j On Tue, Nov 13, 2018 at 8:10 AM, Bill Burcham wrote: > @Patrick Rhomberg I've never seen the > dependencyManagement elem

Re: [PROPOSAL] Add getCache and getLocator to Launchers

ache.geode.distributed.ServerLauncher.start(ServerLauncher.java:749) ... 2 more Cheers, -John On Fri, Nov 2, 2018 at 5:49 PM, John Blum wrote: > Damn it! Correction to my previous email... > > '--disable-default-port' should read '--disable-default-server' in my >

Re: [PROPOSAL] Add getCache and getLocator to Launchers

Damn it! Correction to my previous email... '--disable-default-port' should read '--disable-default-server' in my *Gfsh* `start server` command examples. Apologies, John On Fri, Nov 2, 2018 at 5:41 PM, John Blum wrote: > Bruce- > > Regarding... > > >

Re: [PROPOSAL] Add getCache and getLocator to Launchers

7;s got to be created through cache.xml or something. > > Be that as it may I think the recent talk about this convinces me that > Kirk's original proposal is sound and we should go with it. Servers can be > fished out of the cache so it's not a big deal if the launcher API doesn&

Re: Testing tip: Use IgnoredException as an AutoCloseable

With IDE highlighting things as unused, you can either @SuppressWarnings("unused") on the method or statement highlighted or adjust your IDE inspections (perhaps more advisable), which is per project. On Fri, Nov 2, 2018 at 1:27 PM, Kirk Lund wrote: > The easiest way to use IgnoredException is a

Re: [PROPOSAL] Add getCache and getLocator to Launchers

Well, ServerLauncher may or may not create a CacheServer instance when it starts a server. A server can be created without a CacheServer, for instance, when in *Gfsh* `start server --disable-default-server` option is specified. In addition, you can always find or get the list of CacheServers (if

Re: [Discuss] showcasing community work

This is a very nice idea Sai. Perhaps a page with a table containing... * Project Name * Project Description (Summary) * Project License * Project URL (to GitHub page, Website, etc, where users can find out more information) Food for thought. On Thu, Oct 11, 2018 at 12:04 PM, Sai Boorlagadda

Re: [DISCUSS] Predictable minor release cadence

+1; a time-based approach also helps to keep scope in check (i.e. smaller changes and change sets), which leads to faster feedback (either fail faster, sooner or find out you are on the right track), and shows users/customers active progress/forward momentum, which is only a good thing. Also, a hu

Re: [Discuss] Transitive dependencies and internal .pom changes

Agreed, plus many times you can declare that a dependency is either (appropriately) "test" scope (for test dependencies only), "optional", or (in certain cases) "provided", which will (should) have no impact to end users, e.g. like conflicting dependencies. However, I am in favor of reducing depen

Spring Boot for Apache Geode 1.0.0.M3 Released!

It is my pleasure to announce [1] the release of *Spring Boot for Apache Geode* 1.0.0.M3. This release builds on the latest GA version of *Spring Boot*, 2.0.5.RELEASE, and adds extensive support for using *Spring Boot Actuator* [2] (specifically, providing HealthIndicators [3]) with Apache Geode,

Re: [DISCUSS] Wrapping log calls in Conditionals like isDebugEnabled, isTraceEnabled, etc.

I think any arguments about what optimizations the (JIT enabled) compiler (HotSpot or otherwise) will perform at runtime is questionable at best. HotSpot can "inline" certain [frequent/hot] code paths both at compile/runtime thereby reducing the number of method invocations (which also depends on m

Re: [DISCUSS] Wrapping log calls in Conditionals like isDebugEnabled, isTraceEnabled, etc.

Grrr, meant... logger.debug("Logging in user {}", user); On Fri, Sep 7, 2018 at 11:37 AM, John Blum wrote: > Technically, I think that is SLF4J syntax (but maybe Log4J2 supports this > format now as well; anyway). > > Still, you should be careful with log statements lik

Re: [DISCUSS] Wrapping log calls in Conditionals like isDebugEnabled, isTraceEnabled, etc.

Technically, I think that is SLF4J syntax (but maybe Log4J2 supports this format now as well; anyway). Still, you should be careful with log statements like... logger.debug("Logging in user {}" + user); Assuming the User class itself and an "informative" and properly constructed toString() meth

Re: [Discuss] Hosting nightly Geode snapshots

> --Udo > > > > > > > > > > > > On 9/5/18 15:16, Dan Smith wrote: > > > >> Hi John, > > > >> > > > >> We are publishing nightly snapshots from the develop branch. See > > > >> https://repository.

Re: Concerning Apache Geode 1.7.0

ough > > [DISCUSS] -> [VOTE] , then implemented. > > Currently, it is out of scope for the 1.7.0 release process. > > > > Regards > > Nabarun Nag > > > > On Wed, Sep 5, 2018 at 3:10 PM John Blum wrote: > > > > > I just need nightly build

Re: [Discuss] Hosting nightly Geode snapshots

for the gradle build for the examples repo for an example of > >> build that is consuming these nightly snapshots: > >> > >> https://github.com/apache/geode-examples/blob/master/build.gradle > >> > >> -Dan > >> > >> On Wed, Sep

Re: Concerning Apache Geode 1.7.0

uent versions 1.8.0+ will continue in the > way you mentioned. For 1.7.0 there were some unforeseen circumstances, > which is causing some issues with the release process. > I apologize for the inconvenience and hopefully you will soon have a stable > branch to test. > > Regards

Re: [Discuss] Hosting nightly Geode snapshots

+1 On Wed, Sep 5, 2018 at 3:00 PM, Udo Kohlmeyer wrote: > Hi there Geode Dev-list, > > I would like to suggest that Geode starts making nightly build snapshots > available for downstream consumption. > > Would it be possible to start uploading nightly snapshots to the > http://repository.apache

Re: Concerning Apache Geode 1.7.0

ch to world > to test. > > It will be unproductive of users to run their experiments on a branch with > issues. It will be up as soon as the issues are resolved. I'm working on > resolving them at the moment. Hopefully soon we will send out the mail and > the updated release br

Re: Concerning Apache Geode 1.7.0

s ready. > > Regards > Nabarun Nag > > > On Wed, Sep 5, 2018 at 2:10 PM John Blum wrote: > > > I see that the branch for Apache Geode 1.7.0 (release/1.7.0 [1]) has been > > created in preparation for the upcoming the 1.7 release. > > > > I am trying to get

Concerning Apache Geode 1.7.0

I see that the branch for Apache Geode 1.7.0 (release/1.7.0 [1]) has been created in preparation for the upcoming the 1.7 release. I am trying to get an early sense/feel for the required changes in SDG when I rebase it on 1.7. Previously, I was able to obtain Geode snapshots from... apache-

Re: Testing code in geode-junit and geode-dunit src/main

If you haven't seen this, you should have a look at *Spring Test for Apache Geode* (STDG) [1] I have much work to do yet to round this project out: docs, more "formalized" integration test support (think JUnit Rules and custom Runners over extension, etc) and so on. However, mocking for Geode Obj

Re: Assertions in Geode

While powerful, the problem with Java assertions is that they must be explicitly enabled (e.g. with the JVM switch, -ea), as Jake already pointed out, which makes them dangerous to rely on. Additionally, in general, there is nothing about Assertions that require they only be used for testing purpo

Spring Boot for Apache Geode 1.0.0.M1 Released!

Apache Geode Community- It is my please to announce the first milestone release of Spring Boot for Apache Geode, version 1.0.0.M1. See the official Spring Blog Post [1] for more details. Documentation [2] is available as are a couple of Examples [3]. Feedback appreciated and welcomed. Much mor

Re: Quarterly report - DRAFT for your review

HI Dave- I just recently gave a Webinar to the community on using Spring Session and Apache Geode to manage (HTT) Session State. https://www.youtube.com/watch?v=KIBseFSQUuc Cheers, John On Tue, May 8, 2018 at 10:52 AM, Michael Stolz wrote: > Looks fine to me > > -- > Mike Stolz > Principal

Re: [Proposal] add isBound() to CacheServer API

Kirk- Please see your other email thread and my response [1] to that as 1 potential way to handle this situation. As I mentioned, I use this in the Spring Session client/server integration tests as a way to mitigate the NoSubscriptionsServersAvailableException. -j [1] http://markmail.org/messag

Re: NoSubscriptionServersAvailableException

Kirk- Follow this logic... [1] https://github.com/spring-projects/spring-session-data-geode/blob/master/samples/boot/gemfire/src/main/java/sample/client/IntegrationTestConfiguration.java#L70-L71 Which is based on the Registration of a ClientMembershipListener... [2] https://github.com/spring-p

Re: [Proposal]: behavior change when region doesn't exist in cluster configuration

Hi Jinmei- Regarding this... " *So the current behavior is, when a customer starts a server with cache.xmlthat has a region defined, and then later on issues a gfsh command `createindex` on that region, the command output would be something like:* *>create index .Member | Status--

Re: [Proposal]: behavior change when region doesn't exist in cluster configuration

I would also ask/remind us to carefully consider anything that might be needed, or required, in the API as well. We must thoughtfully compliment the, or a, API (i.e. programmatically) with anything you can do in/from *Gfsh*. The API is a first class citizen and how most users will consume product

Re: [Proposal] Changes to the experimental cluster configuration API.

Perhaps a reference to the "experimental" interface would be helpful. This "specification" page ( https://cwiki.apache.org/confluence/display/GEODE/Public+Interface+to+Cluster+Configuration+Service) contains no links. *Main question... again, why should the ClusterConfigurationService interface h

Re: Index on Region

Well, the way I handle this in *Spring Data for Apache Geode* is, and to *Kirk's* point, the schema (XSD) version matches the SDG version. I.e. in SDG 2.0.0 [1] there is a spring-geode-2.0.0.xsd, and in SDG 2.1.0 [2] there now exists a spring-geode-2.1.0.xsd. So, you could have a cache-1.1.xsd, o

Re: [VOTE] Apache Geode 1.5.0.RC2

Thanks Anthony and team. On Thu, Apr 5, 2018 at 9:03 AM, Anthony Baker wrote: > +1 > > - checked signatures > - checked sha’s > - checked for binaries in source release > - builds from source > - examples run cleanly > > Let’s crowd source some release notes at https://cwiki.apache.org/ > conflu

Re: [VOTE] Apache Geode 1.5.0.RC2

+0 The Apache Geode *Log4j* dependency version *2.8.2* is or will cause significant issues for apps, and in particular *Spring Boot* 2.0 apps. This Geode Log4j version is already quite dated as *Log4j 2.11.0* is now already available [1] and *Spring Boot* 2.0 pulls in *Log4j 2.10.0* [2]. *Why a

Re: [PROPOSAL] Deprecating DistributedSystem

is from the ClusterConfigurationService, since what does that have to do with clients? -j On Thu, Mar 29, 2018 at 3:33 PM, Kirk Lund wrote: > We should probably consider moving ServerLauncher and LocatorLauncher from > org.apache.geode.distributed to a different package (maybe > org.apache.geode

Re: [PROPOSAL] Deprecating DistributedSystem

@Patrick - have a look at... http://gemfire-93-javadocs.docs.pivotal.io/org/apache/geode/cache/execute/FunctionService.html#onMember-org.apache.geode.distributed.DistributedMember- On Thu, Mar 29, 2018 at 2:23 PM, Patrick Rhomberg wrote: > +1 to deprecation. > > @John, The context in which the

Re: [PROPOSAL] Deprecating DistributedSystem

Yes, framework and tooling. I see no reason why the functionality in o.a.g.distributed.DistributedSystem [1] should be hidden or internal. I would certainly remove the deprecated methods by now. A few other methods are questionable as to whether they really belong on the DistributedSystem interf

Re: [VOTE] Apache Geode 1.5.0 RC1

The same could be said of GEODE-4787. On Fri, Mar 23, 2018 at 2:58 PM, Anthony Baker wrote: > Thanks for catching this Diane. I agree; we shouldn't break something that > used to work. > > Anthony > > > On Mar 23, 2018, at 11:27 AM, Diane Hardman wrote: > > -1 > I filed GEODE-4913 based on scr

Re: [PROPOSAL] Public API for Cluster Configuration

any other open > > source projects that have solved the configuration problem. Let’s not > > reinvent the wheel here. > > > > -Jake > > > > > > > > > On Mar 13, 2018, at 1:59 PM, John Blum wrote: > > > > > > Some initial though

Re: [PROPOSAL] Public API for Cluster Configuration

Some initial thoughts after looking over the spec... 1. As a developer (application, API/framework, tool or even a module developer), I really don't care nor should I care what Apache Geode is storing the configuration as under-the-hood. It could be XML, JSON, YAML, a database or even some confi

Re: FunctionService Proposal

+1 Udo. A very clear and descriptive spec; Nice work! In short, these would be welcomed changes and would have very little impact to *Spring Data for Apache Geode*, which nicely abstracts this API even further using its POJO-based, Annotation configuration model for Function Implementations as we

Re: Next release: 1.5.0

rse. > apachegeode-ci.info/teams/main/pipelines/release-1.5.0/ > jobs/DistributedTest/builds/2> > > Anthony > > > > On Mar 6, 2018, at 8:57 AM, John Blum wrote: > > > > I don't think this should wait since it affects downstream artifacts > > (already

Re: Next release: 1.5.0

18 at 8:40 AM, Alexander Murmann wrote: > John, how much of an issue would it be if the change was added one month > from now? > > On Tue, Mar 6, 2018 at 8:36 AM, John Blum wrote: > > > I have 1 addition (planning to submit a PR for review) for the 1.5 > release > > tha

Re: Next release: 1.5.0

I have 1 addition (planning to submit a PR for review) for the 1.5 release that is imperative for *Spring Data for Apache Geode*, and specifically, client-side Cluster Configuration Push [1]. Details to follow soon; will file a ticket in JIRA. -j [1] https://docs.spring.io/spring-data/geode/doc

Spring for Apache Geode Announcements...

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

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

configuration) > can exist on both locators and servers. If it runs on servers then it > suddenly does not have access to the configuration service. > > It almost feels like we need more capabilities around > distributed/discoverable micro-services inside Geode. > > --Jens > > On

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

icult or prevent running everything in geode within one JVM. > > On Wed, Feb 21, 2018 at 10:12 AM, John Blum wrote: > > > Hi Jinmei- > > > > Plain and simple, "development purposes". I can easily debug such a > server > > when I can launch it from m

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

pulse or other jmx client for monitoring purpose > mostly? Or they would still want to connect using gfsh and execute bunch of > commands to create regions/indexes etc? We are just wondering how much > command support we should do for such jmx-managers. > > On Tue, Feb 20, 2018 at 3:0

Re: [DISCUSS] changes to registerInterest API

+1 On Tue, Feb 20, 2018 at 5:17 PM, Dan Smith wrote: > > > > unregisterInterestForKeys(Iterable keys) > > > > +1 > -- -John john.blum10101 (skype)

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

So long as we **never** remove the ability to start an "embedded" *Locator/Manager* in an [application] *CacheServer *process*, *which is highly valuable during "*development*". For instance, I may want to spin up an application peer *CacheServer* instance with an embedded *Locator/Manager*, like

Re: [PROPOSAL] creation of a public interface to the cluster configuration service

I agree that there ought to be some kind of public API for administrative operations (e.g. create Region remembered/stored by Cluster Config), but when will there actually be substance to this proposed "public interface"? It would be helpful to have some high-level interfaces and domain types to re

Re: Updating dependencies

Ever consider inheriting from *Spring Boot's* dependency BOM file [1] by applying the *Spring *Dependencies Management Gradle Plugin? The advantage of plugin over this [2] is that you are guaranteed to get a curated and harmonized list of *Spring* and 3rd party (transitive) dependencies that have

Re: ASF Quarterly report - please review by Tuesday Noon

+1 On Mon, Feb 12, 2018 at 4:38 PM, Anthony Baker wrote: > I would add info about the Geode sessions at the SpringOne conference. > > "The SpringOne Platform conference in December 2017 included 12 talks [1] > on Apache Geode. The talks were given by users and developers of Geode, > covering us

Re: [PROPOSAL]: deprecating create region using --template-region option

in gfsh. > I am sure the concept can be useful in other creation mechanism as long as > they have a way to ensure that those callback are available on the member > where they are trying to create the region. > > On Wed, Feb 7, 2018 at 10:56 AM, John Blum wrote: > >> +

Re: [PROPOSAL]: deprecating create region using --template-region option

+0 As an FYI, *Spring Data Geode/GemFire* already provides such a capability [1], which makes much more sense from an application standpoint than a tooling standpoint. Having said that, I would also add that this capability is 1 of the more popular features in SDG (particularly from customers).

Re: Naming unit tests and integration tests

+1 to Kirk's last point (and, well, the points before it). As for bug specific tests, it is common to add a comment of the nature... class SomeExistingTestClass { /** * ... ** @see http://issues.apache.org/../GEODE-123 ">Bug Title Here* */ @Test public v

Re: [ANNOUNCE] Apache Geode 1.4.0

Congrats! On Mon, Feb 5, 2018 at 2:10 AM, Swapnil Bawaskar wrote: > The Apache Geode community is pleased to announce the availability of > Apache Geode 1.4.0. > > Apache Geode is a data management platform that provides a database-like > consistency model, reliable transaction processing and a

Re: Proposal: GEODE-4367 - Return PDXInstance when Domain Object can't be found

rder for SDG to do the right thing for the user, covering 80% of the most common scenarios. -j [1] https://github.com/spring-projects/spring-data-geode/blob/2.0.3.RELEASE/src/main/java/org/springframework/data/gemfire/function/PdxFunctionArgumentResolver.java On Thu, Jan 25, 2018 at 1:1

Re: Proposal: GEODE-4367 - Return PDXInstance when Domain Object can't be found

To Swap's point about making ReflectionBasedAutoSerializer the default (which I think is a good idea), comparably, in SDG, I have made SDG's o.s.d.g.mapping.MappingPdxSerializer [1] the default when PDX is enabled (i.e. @EnablePdx). No need to explicitly declare/register it. SDG's MappingPdxSeria

Re: Proposal: GEODE-4367 - Return PDXInstance when Domain Object can't be found

I have always thought/wondered, why not just store the data in serialized form always. There are several reasons to do so... 1. Whenever data is transferred between client & server, between peers, over the WAN, overflowed to disk or persisted to disk, it must be serialized. 2. Naturally it follow

Roadmap and Upcoming Features for Spring Data for Apache Geode 2.1 (SD Lovelace)...

Hi Apache Geode Community- Now that SDG 2.0 is fairly stable (entering its 3rd service release already now) and I have resolved all known issues, particularly with the new SDG Annotation configuration, I figured I would take this opportunity to let you all know about some of the features I have pl

Spring Data for Apache Geode 2.0.3.RELEASE available!

Apache Geode Community- I am very pleased to follow-up to the announcement by Mark Paluch on the release of Spring Data Kay SR3. This includes Spring Data for Apache Geode 2.0.3.RELEASE. The 3rd service release of SDG includes several import fixes and enhancements, particular around the new Anno

Spring Session for Apache Geode 2.0.0.RELEASE Available!

Apache Geode Community- I am pleased to announce the General Availability (GA) of *Spring Session for Apache Geode* 2.0.0.RELEASE (SSDG), which is now available from Maven Central [1]. SSDG 2.0 GA builds on... * Spring Framework 5.0.2.RELEASE * Spring Data for Apache Geode 2.0.2.RELEASE * Spring

Re: [DISCUSS] changes to registerInterest API

ught I'd ask the question... > > On Thu, Nov 30, 2017 at 2:33 PM John Blum wrote: > > > For instance, this came up recently... > > > > > > https://stackoverflow.com/questions/46551278/gemfire- > composite-key-pojo-as-gemfire-key > > > > I have se

<    1   2   3   4   >