+1 to Anthony’s suggestion.
From: Anthony Baker
Date: Wednesday, June 29, 2022 at 12:34 PM
To: dev@geode.apache.org
Subject: CODEOWNERS? (was Re: Pending PR reviews)
⚠ External Email
I realize that this is a thread hijack, but hopefully a useful one. I’ve seen
several requests for timely revie
I like this idea. I agree that changes to documentation are different from
changes to code, and documentation should be able to move in a different
cadence.
Would committers to Geode and Geode-docs be the same after this proposed change?
Joris Melchior
From: Dave Barnes
Date: Tuesday, June
+1 for Naburan’s proposed options.
From: Nabarun Nag
Date: Monday, June 28, 2021 at 4:06 PM
To: Owen Nichols , dev@geode.apache.org
Subject: Re: Fw: [DISCUSS] Rebase and Squash Options on Github develop
Just a clarification.
The options I am proposing to be kept in the PRs are:
* Squash a
Congratulations Kamilla!
Joris
From: Ernie Burghardt
Date: Monday, April 19, 2021 at 5:22 PM
To: dev@geode.apache.org
Subject: [ANNOUNCE] New Geode Committer - Kamilla Aslami
The Apache Geode Project Management Committee has invited Kamilla Aslami to
join the Geode as a Committer and we are pl
+1 On this approach. If we could somehow have side project to implement this I
think it would be really helpful.
I also think it's less intimidating to contribute to for a lot of people.
Joris
On 2021-03-29, 2:55 PM, "John Blum" wrote:
How hard is it to put the work like Protobuf in a s
Welcome Matt!
On 2021-03-23, 1:56 PM, "Ernie Burghardt" wrote:
The Apache Geode Project Management Committee has invited Matt Reddington
to join the Geode as a Committer and we are pleased to announce he has
accepted.
Please join me in welcoming Mat!
Best regards,
EB
+1
On 2021-03-19, 10:35 AM, "Jens Deppe" wrote:
This work builds on GEODE-9023 which added sharding support to the
compatible with Redis region.
This change cleans up data structures and will allow for easier, future
rolling upgrades and data migrations if necessary.
Thanks
+1
On 2021-03-17, 2:43 PM, "Hale Bales" wrote:
Hello,
I am putting forward the proposal to backport GEODE-9045 (Rename Redis
properties and error messages) to support/1.14 branch,
What does GEODE-9045 do?
* It renames the redis-port property to
com
February 18, 2021.
Thanks,
Joris Melchior
I’ll give this an informal +1 then.
Joris
From: Robert Houghton
Date: Thursday, January 14, 2021 at 4:40 PM
To: dev@geode.apache.org
Subject: [DISCUSS] CODEOWNERS and .asf.yml
Hello fellow Geode developers.
The CODEOWNERS file has been merged to Geode develop for a few days now,
and we are sta
+1
Looks good to me. Did a build and gfsh test-drive.
From: Dan Smith
Date: Monday, November 16, 2020 at 1:29 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.13.1.RC2
+1
Looks good to me! I ran the geode-release-check against it, looked for binary
artifacts, checked the pipelin
+1
From: Dick Cavender
Date: Thursday, November 12, 2020 at 2:01 PM
To: dev@geode.apache.org
Subject: Apache Geode 1.13.1 patch proposal
It's been two months since the 1.13.0 release and there have been 28 important
fixes on support/1.13 that the community would benefit from. Based on this I'd
+1
From: Donal Evans
Date: Wednesday, October 21, 2020 at 12:00 PM
To: dev@geode.apache.org
Subject: [PROPOSAL] Backport fix for GEODE-8620 to 1.13.1
Hi Geode dev,
I would like to backport the fix for
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2F
+1
On 2020-10-08, 10:51 AM, "Jinmei Liao" wrote:
I would like to include the fix for GEODE-8574 to 1.13.1, it would greatly
help the Geode on k8s experience.
Thanks!
Jinmei
+1
On 2020-09-29, 6:09 PM, "Xiaojian Zhou" wrote:
Hi,
GEODE-6008 changed “java.lang.IllegalStateException: NioSslEngine has been
closed” to IOException, which enabled DirectChannel to handle it and retry the
connection in the case that the connection is closed.
This fix is impor
+1
On 2020-09-28, 3:21 PM, "Dan Smith" wrote:
Hi,
I'd like to backport this change to support/1.13 as well
GEODE-8522: Switching exception log back to debug -
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F5566&data=02%7C01%
+1
On 2020-09-23, 7:23 PM, "Jason Huynh" wrote:
Hello,
I’d like to merge the pull request:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F5524&data=02%7C01%7Cjmelchior%40vmware.com%7Cf627e716175e47d617c408d86017a1be%7Cb39138ca3ce
+1
On 2020-08-20, 12:08 PM, "Xiaojian Zhou" wrote:
It's using region path instead of getting the region. It should be no risk.
On 8/19/20, 10:25 AM, "Xiaojian Zhou" wrote:
This problem also exists in 1.13.
+1
On 2020-07-28, 7:34 PM, "Alexander Murmann" wrote:
Hi all,
As mentioned on the previous discuss thread, I propose to hold off cutting
1.14 until we have shipped 1.13.
Once we have shipped 1.13, we should discuss when we want to cut the 1.14
release. The actual ship date
+1
On 2020-07-10, 12:39 AM, "Owen Nichols" wrote:
A fresh checkout of geode and all but one geode- repos
checks out develop as the Default branch.
The lone exception is geode-examples. Please vote +1 if you are in favor
of changing its Default branch to develop for consistency with
You might also want to look at docker compose so that locator and server can
run in separate containers.
On 2020-07-08, 12:18 AM, "Mark Hanson" wrote:
Here is a command that actually runs..
You need to be in the Geode directory, the run the command below to start
everything.
d
+1
On 2020-07-03, 9:06 AM, "Ju@N" wrote:
Hello devs,
I'd like to propose bringing GEODE-8029 [1] to the support/1.12 and
support/1.13 branches.
No, you're not having deja vú (neither this is an error within the Matrix):
a couple of weeks ago I've backported another fix for
Pulse communicates to the locator over jmx/rmi as well.
From: Kirk Lund
Sent: June 19, 2020 14:24
To: dev@geode.apache.org
Subject: Re: Client Usage of RMI
The only use of RMI in Geode that I'm aware of is:
1) GFSH to Locator communication over jmx/rmi
2) Commun
Yes, +1 on this change.
Joris
From: Mark Hanson
Sent: June 15, 2020 16:30
To: dev@geode.apache.org
Subject: Re: Refactor to Restore Redundancy Command for 1.13?
To be clear the code for 1.13 using the Restore Redundancy Command in GFSH is
fine as it stands. We
+1
From: Ju@N
Sent: June 10, 2020 6:18
To: dev@geode.apache.org
Subject: [PROPOSAL]: BackPort GEODE-8029 to support/1.12 and support/1.13
Hello devs,
I'd like to propose bringing GEODE-8029 [1] to the *support/1.12* and
*support/1.13* branches.
The fix has been
I lean towards forks as well. I understand Naba's concerns but for most of the
work we do, forks are a straightforward way to work on contributions to Geode.
It's easy to give people rights on your fork if you work with multiple
contributors.
Joris
From: Ernie B
+1
From: Bruce Schuchardt
Sent: May 27, 2020 16:35
To: dev@geode.apache.org
Subject: [PROPOASAL] backport GEODE-8144
This ticket has two PRs. One passed all normal CI runs but then we hit a
faulty test that failed on a Windows machine. There’s a new PR that fi
More documentation is good!
+1
From: Jinmei Liao
Sent: May 19, 2020 14:26
To: geode
Subject: [PROPOSAL] Bring GEODE-8100 to support branches
This is to update documentation to better explain the Cluster management
service and various geode/system properties that
+1
From: Bruce Schuchardt
Sent: May 19, 2020 11:53
To: dev@geode.apache.org
Subject: [PROPOSAL] bring GEODE-8131 PR to support branches
While investigating a distributed hang we discovered that the alerting system
was blocking the logging of critical information
This seems like a good thing to have.
+1
From: Robert Houghton
Sent: May 13, 2020 17:32
To: dev@geode.apache.org ; Mario Ivanac
Subject: [DISCUSS] enable GitHub PR blocking on API breaking changes
We have enabled this job on the develop and support 1.13 branche
+1
From: Robert Houghton
Sent: May 12, 2020 18:57
To: dev@geode.apache.org ; Dave Barnes (Pivotal)
Subject: [PROPOSAL] Merge PR 5103 (GEODE-8083) to support/1.13
This is a squash of GEODE-8083 and 8087, to bring the Java API comparison
jobs from Gradle and Conc
+1
From: Patrick Johnson
Sent: May 8, 2020 17:40
To: dev@geode.apache.org
Subject: Proposal to bring GEODE-8068 to support/1.13
I’d like to bring GEODE-8068 to support/1.13. This commit reverts two prior
commits (GEODE-8033 and GEODE-8044). GEODE-8033 and GEODE-
+1
From: Jacob Barrett
Sent: May 8, 2020 21:26
To: dev@geode.apache.org
Subject: Discussion - Change Public API Before Initial Release
Hey Ya’ll,
We have a new API going into 1.13 that has an inconsistency I want to address
before we are stuck with it. The clas
Recent experience makes me lean towards quick revert as well. Takes the
pressure off when trying to produce a fix and if done soon enough it is usually
quite straightforward.
From: Owen Nichols
Sent: April 29, 2020 7:06 PM
To: dev@geode.apache.org
Subject: [DISC
+1
From: Anthony Baker
Sent: April 21, 2020 11:54 AM
To: dev@geode.apache.org
Subject: Reconfiguring our notifications and more
I’d like a quick round of feedback so we can stop the dev@ spamming [1].
ASF has implemented a cool way to give projects control of lo
> [2]:
>
> https://github.com/apache/geode/commit/bfbb398891c5d96fa3a5975365b29d71bd849ad6
>
> --
> Ju@N
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*
<https://en.wikipedia.org/wiki/Hal_Abelson>
velop since February via GEODE-7798.
>
> This fix is critical to avoid false positives in automated vulnerability
> scans.
>
> -Owen
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to e
evised from an earlier draft
> version that some of you may have seen, so the content may have changed.
>
> Thanks,
> Donal
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to exe
This hopefully addresses some of the concerns with the previous RFC for
> this feature. The new proposal is for a more general SocketFactory property
> that users can implement, along the lines of what Jake and Owen suggested.
>
> -Dan
>
--
*Joris Melchior *
CF Engineering
Pivotal
gt;* {@code
> >* Bar bar = Bar();
> >* bar.doSomethingBetter();
> >* bar.doSomethingElse();
> >* }
> >*/
> > @Deprecated
> > public void doSomethingAndSomethingElse() {}
> > }
> >
> > class Bar {
> > public void doSomethingBetter() {}
> > public void doSomethingElse() {}
> > }
> >
> > -Jake
> >
> >
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*
<https://en.wikipedia.org/wiki/Hal_Abelson>
r bar = Bar();
>* bar.doSomethingBetter();
>* bar.doSomethingElse();
>* }
>*/
> @Deprecated
> public void doSomethingAndSomethingElse() {}
> }
>
> class Bar {
> public void doSomethingBetter() {}
> public void doSomethingElse() {}
> }
>
>
o
>
> On 3/6/20 11:04 AM, Bill Burcham wrote:
> > Please review the RFC for *Client side configuration for a SNI proxy*:
> >
> >
> https://cwiki.apache.org/confluence/display/GEODE/Client+side+configuration+for+a+SNI+proxy
> >
> > Please comment by Monday, March
it in this release, where
> most users are just starting to experiment with CMS rest service would be
> great.
>
> [1]: https://issues.apache.org/jira/browse/GEODE-7717
>
> https://github.com/apache/geode/commit/bda6bdf50c0a6a3e7cc39fb3ff654a0c26c86d94
>
> --
> Cheers
Since the feedback has been to proceed with this proposal I will open a
JIRA ticket and start the work on this.
Thanks for the feedback on this.
Joris.
On Fri, Jan 3, 2020 at 1:11 PM Kirk Lund wrote:
> I'm for un-deprecating it.
>
> On Fri, Jan 3, 2020 at 7:01 AM Joris Mel
tring-java.lang.String-java.lang.String-
> [4]
>
> https://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/query/QueryService.html#createIndex-java.lang.String-org.apache.geode.cache.query.IndexType-java.lang.String-java.lang.String-java.lang.String-
> [5]
>
> https://geode.apache.org/release
ear
> to me why it was originally deprecated or what the intended new direction
> (instead of IndexType) was ever going to be. Do you know more about why it
> was deprecated or what the devs were going to replace it with?
>
> On Thu, Jan 2, 2020 at 6:31 AM Joris Melchior
> wrot
his proposal seems reasonable to me
>
> On 12/3/19 10:19 AM, Joris Melchior wrote:
> > Ah, that makes sense. I will update!
> >
> >
> > On Tue, Dec 3, 2019 at 12:41 PM Alexander Murmann
> > wrote:
> >
> >> Joris, the "to be reviewed by" fi
Spring Data Geode and friends
> had trying to mock Pools and remove the need for those projects to try to
> inject mock Pools into a Geode singleton.
>
>
> https://cwiki.apache.org/confluence/display/GEODE/Replace+singleton+PoolManager+with+ClientCache+scoped+service
>
> T
eframe you envision?
>
> Thanks!
>
> On Mon, Dec 2, 2019 at 1:41 PM Joris Melchior
> wrote:
>
> > Hi All,
> >
> > Looking for feedback on the proposal to [un/de]deprecate the IndexType
> ENUM
> > on Geode.
> >
> >
> https://cwiki.apa
Hi All,
Looking for feedback on the proposal to [un/de]deprecate the IndexType ENUM
on Geode.
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=135863477
Thanks, Joris.
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to
we just take the certificate subject DN instead and provide
> it
> >> to the security manager for authorization.
> >>
> >>
> >>
> >> This wouldn’t lower the level of security (we can have TLS enabled
> without
> >> access control already), but would provide authentication without the
> >> hassle of username and password handling.
> >>
> >>
> >>
> >> This is the basic description of the idea. There would be more things to
> >> consider, like multi user authentication, but for now we would just
> like to
> >> get some initial feedback. If it is considered useful, we could get into
> >> the details.
> >>
> >>
> >> BR,
> >>
> >> Mario
> >>
> >>
>
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*
<https://en.wikipedia.org/wiki/Hal_Abelson>
lementations for the Functional type. Under the covers we create a
> > memory-optimized version based on the indexed expression.
> >
> > Things have changed since deprecation, so maybe it should be
> > un/de-deprecated or an alternative solution can probably be
and the functional index.
>
> I am not sure if there is an alternative in gfsh... it might still be using
> the IndexType enum or something similar.
>
>
>
>
> On Fri, Nov 29, 2019 at 12:18 PM Joris Melchior
> wrote:
>
> > Thanks John.
> >
> > I'm t
re/IndexType.html
> [2]
>
> https://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/query/IndexType.html
>
>
> On Fri, Nov 29, 2019 at 8:17 AM Joris Melchior
> wrote:
>
> > Hi All,
> >
> > I notice that the ENUM
> >
> > org.apach
) are still valid and I believe we
should be able to use them without using deprecated code.
Can anyone tell me how this is accomplished?
Thanks, Joris.
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machin
> > WAN/AEQ such as AEQ-pause are increasing user interaction with
> > WAN-related
> > > gfsh commands.
> > > >
> > > > The fix is simple, low risk, tested, and has been on develop for 5
> > days:
> > > >
> > >
> >
> https://github.com/apache/geode/commit/e148cef9cb63eba283cf86bc490eb280023567ce
> > >
> >
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*
<https://en.wikipedia.org/wiki/Hal_Abelson>
on this group of types, which in
> >> turn
> >>> are (were) highly-dependent on geode-core. We have been systematically
> >>> eliminating dependencies from these types to geode-core as part of
> >>> https://issues.apache.org/jira/browse/GEODE-7343 _TcpServer should not
> &
icy/updates/jboss_notes
> >>>>> [4] - https://en.wikipedia.org/wiki/IBM_WebSphere_Application_Server
> >>>>> [5] -
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://www.solstice.com/fwd/survival-gu
Thanks Dan!
On Fri, Nov 1, 2019 at 3:01 PM Dan Smith wrote:
> Hi Joris,
>
> You now also have access.
>
> Thanks!
> -Dan
>
> On Fri, Nov 1, 2019 at 8:12 AM Joris Melchior
> wrote:
>
> > Hi Dan,
> >
> > Can you provide me with the ability to as
e one.
> > >
> > > -Dan
> > >
> > > On Thu, Oct 31, 2019 at 10:09 AM Szu-Yu Lo
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > I am new to geode and would love to contributed to geode. I am not
> > able
> &
ple to reapprove minor changes (Fixing merge
> > > > > conflicts, spotless, etc.)
> > > > >
> > > > > If you all agree I'll ask infra to uncheck "Dismiss stale pull
> > request
> > > > > approvals when new commits are pushed." in our branch protection
> > rules.
> > > > >
> > > > > -Dan
> > > >
> > > >
> > >
> >
>
>
> --
> Ju@N
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*
<https://en.wikipedia.org/wiki/Hal_Abelson>
s and beginning
> > elimination of usage of it within Geode?
> >
> > Regards,
> > Bill
> >
> > [1]
> > https://docs.oracle.com/javase/specs/jvms/se7/html/jvms-6.html#jvms-6.3
> > [2] oh and here's a ticket
> > https://issues.apache.org/jira/browse/GEODE-7369
> >
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*
<https://en.wikipedia.org/wiki/Hal_Abelson>
to
> wait at least until all CIs are done)*. *I also agree in that that we
> should require *at least one* official approval.
> Cheers.
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
mach
t; > > > 1. start your locator with this property:
> > > > *security-auth-token-enabled-components = all (or management)*
> > > > 2. implement your SecurityManager to authenticate the jwt token
> passed
> > > in.
> > > > The jwt token
ut in review comments today. We're shooting
> for
> > >> > closing this RFC this week.
> > >> >
> > >> >
> > >> > On 8/30/19 3:50 PM, Dan Smith wrote:
> > >> > > Hi all,
> > >> > >
> > >> > > We added the following RFC to the wiki about moving Geode's
> > membership
> > >> > > system to a separate gradle sub-project. Please review and comment
> > by
> > >> > > 9/6/2019.
> > >> > >
> > >> > > https://cwiki.apache.org/confluence/x/WRB4Bw
> > >> > >
> > >> > > Thanks!
> > >> > > -Dan
> > >> > >
> > >> >
> > >>
> > >
> >
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*
<https://en.wikipedia.org/wiki/Hal_Abelson>
gt; The geode-unsafe module compiles with API warnings suppressed. Have fun
> compiling without all these warnings filling your screen.
>
> https://issues.apache.org/jira/browse/GEODE-130 <
> https://issues.apache.org/jira/browse/GEODE-130>
>
> -Jake
>
>
>
--
*
Thanks, all good now!
On Fri, Aug 2, 2019 at 4:32 PM Kirk Lund wrote:
> Oops. Try now.
>
> On Fri, Aug 2, 2019 at 12:52 PM Joris Melchior
> wrote:
>
> > Don't seem to have edit permissions yet though ...
> >
> > On Fri, Aug 2, 2019 at 3:48 PM Joris Melc
Don't seem to have edit permissions yet though ...
On Fri, Aug 2, 2019 at 3:48 PM Joris Melchior wrote:
> Thanks Kirk!
>
> On Fri, Aug 2, 2019 at 12:16 PM Kirk Lund wrote:
>
>> You should have permission now. Thanks!
>>
>> On Fri, Aug 2, 2019 at 7:32 AM J
Thanks Kirk!
On Fri, Aug 2, 2019 at 12:16 PM Kirk Lund wrote:
> You should have permission now. Thanks!
>
> On Fri, Aug 2, 2019 at 7:32 AM Joris Melchior
> wrote:
>
> > Hi,
> >
> > Can someone provide me with edit permissions on the wiki? Specifically
>
Hi,
Can someone provide me with edit permissions on the wiki? Specifically the
tree starting with this link
https://cwiki.apache.org/confluence/display/GEODE/Cluster+Management+Service
My user name is 'joris.melchior'.
Thanks,
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
41
; >>> I have just spent a bit of time reviewing PRs that have been open for a
> >>> while and sent some emails to reviewers of the ones that are open the
> >>> longest. In my humble opinion, it would be very nice if we could close
> >> out
> >>> s
if we could close out
> some of the older PRs where the requester has made changes to, but
> reviewers have not re-reviewed. An ideal norm would seem to be 7 days. One
> might notice that I have a PR that I requested a change on, that I have not
> provided feedback on, so I am in the same b
udhary <
aashish.choudha...@gmail.com> wrote:
> Hi Team,
>
> I am interested to work on Geode development, bug fixes etc. Let me know
> the process for same.
>
>
> With Best Regards,
> Ashish
>
--
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427
“Prog
he "reviewers" field - if
> > someone can figure out how to do this with the github IU, we can at least
> > try filing an ticket with apache infrastructure.
> >
> > In the meantime, you can also just add a comment mentioning the people
> > you'd like t
tter(s)
> > of
> > > >>> that PR to ensure that the code and the PR follows the project's
> > > criteria
> > > >>> for code quality and test coverage. It also becomes easier to
> measure
> > > the
> > > >>> PRs of a non-committ
75 matches
Mail list logo
