The documentation for the Redis API for Geode that will currently be published
for 1.13 is not accurate and needs to be updated so potential users searching
for information about Redis API for Geode will get accurate information.
+1
From: Sarah Abbey
Sent: Wednesday, August 12, 2020 8:59 AM
To: dev@geode.apache.org
Subject: [PROPOSAL] Backport GEODE-8423 to support/1.13
The documentation for the Redis API for Geode that will currently be published
for 1.13 is not accurate and needs to be
+1
On Wed, Aug 12, 2020 at 9:10 AM Darrel Schneider wrote:
> +1
>
> From: Sarah Abbey
> Sent: Wednesday, August 12, 2020 8:59 AM
> To: dev@geode.apache.org
> Subject: [PROPOSAL] Backport GEODE-8423 to support/1.13
>
> The documentation for the Redis API for Ge
+1
-Dan
On Aug 12, 2020, at 8:59 AM, Sarah Abbey
mailto:sab...@vmware.com>> wrote:
get
+1
> On Aug 12, 2020, at 8:59 AM, Sarah Abbey wrote:
>
> The documentation for the Redis API for Geode that will currently be
> published for 1.13 is not accurate and needs to be updated so potential users
> searching for information about Redis API for Geode will get accurate
> information.
OK, Sarah, you have the requisite 3 votes -- go ahead and back-port.
Thanks for your contribution!
-Dave
On Wed, Aug 12, 2020 at 9:24 AM Dan Smith wrote:
> +1
>
> -Dan
>
> On Aug 12, 2020, at 8:59 AM, Sarah Abbey sab...@vmware.com>> wrote:
>
> get
>
>
Sounds good to me. I like the idea of using a proxy instead of the
--hostname-for-clients solution where you cannot specify the particular server
of which to connect. And it seems good to use the same approach that was used
for "off platform" clients.
Aaron
Since this is a new test, can we please prioritize fixing it?
https://issues.apache.org/jira/browse/GEODE-8379
java.lang.AssertionError:
Expecting:
<0L>
to be greater than:
<0L>
at
org.apache.geode.redis.internal.executor.server.TimeIntegrationTest.timeCommandRespondsWIthTwoValues(TimeIntegrati
Hi All,
We have found a case where tombstones were being cleared when the region was
not initialized. This was causing some test failures and potential field
failures. We would like to put this into support/1.13.
Thanks,
Mark
+1
From: Mark Hanson
Sent: Wednesday, August 12, 2020 4:40 PM
To: dev@geode.apache.org
Subject: [Proposal] Backport GEODE-8422 to support/1.13
Hi All,
We have found a case where tombstones were being cleared when the region was
not initialized. This was causing
+1
On Wed, Aug 12, 2020 at 4:41 PM Mark Hanson wrote:
> Hi All,
>
> We have found a case where tombstones were being cleared when the region
> was not initialized. This was causing some test failures and potential
> field failures. We would like to put this into support/1.13.
>
> Thanks,
> Mark
Has the version on the develop branch completed a test cycle?
On Wed, Aug 12, 2020 at 4:52 PM Jianxia Chen wrote:
> +1
>
> On Wed, Aug 12, 2020 at 4:41 PM Mark Hanson wrote:
>
> > Hi All,
> >
> > We have found a case where tombstones were being cleared when the region
> > was not initialized. T
Not yet, we will need to wait for that to finish cleanly relative to this
change. I guess I was just seeking to gain approval for priority of it once it
does pass. (Maybe I am being a little over zealous).
Thanks,
Mark
On 8/12/20, 5:52 PM, "Dave Barnes" wrote:
Has the version on the deve
13 matches
Mail list logo
