Thanks for your contribution, Gester
On Thu, Aug 20, 2020 at 12:37 PM Joris Melchior
wrote:
> +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:
>
>
+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.
Looks like it passes all test in the pipeline and overnight. Sounds like a
good change, +1
On 8/20/20, 9:09 AM, "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
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.
Sent: Wednesday, August 19, 2020 2:09 PM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] Backport GEODE-8432 to 1.13
+1
On 8/19/20, 10:25 AM, "Xiaojian Zhou" wrote:
This problem also exists in 1.13.
+1
From: Jinmei Liao
Sent: Wednesday, August 19, 2020 2:09 PM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] Backport GEODE-8432 to 1.13
+1
On 8/19/20, 10:25 AM, "Xiaojian Zhou" wrote:
This problem also exists in 1.13.
+1
On 8/19/20, 10:25 AM, "Xiaojian Zhou" wrote:
This problem also exists in 1.13.
This problem also exists in 1.13.
