Yes, it looks like the Redis server is only labeled an Experimental
Feature in the Pivotal docs for GemFire. Geode docs don't label it
experimental and no-one added @Experimental when that annotation was
introduced.
Le 2/27/2017 à 1:40 PM, Dan Smith a écrit :
Given that the feature is still
>
> Given that the feature is still labeled experimental, do our backwards
> compatibility constraints apply?
>
Actually, it doesn't look like it is marked with @Experimental or is
described as experimental in the docs.
That said, I think maybe it *should* have been marked as experimental
because
icity of Redis API making this problem (delta update)most
>>>> apparent. But, I would imagine many Geode apps has a similar use case.
>>>>
>>>> -Hitesh
>>>>
>>>>From: Michael Stolz
>>>> To: dev@geode.apache.org
>&g
ot of work to
>> propagate Redis commands through those paths.
>>>>
>>>>> Le 2/27/2017 à 10:35 AM, Hitesh Khamesra a écrit :
>>>>> The simplicity of Redis API making this problem (delta update)most
>> apparent. But, I would imagine many Geode ap
gh those paths.
> >>
> >>> Le 2/27/2017 à 10:35 AM, Hitesh Khamesra a écrit :
> >>> The simplicity of Redis API making this problem (delta update)most
> apparent. But, I would imagine many Geode apps has a similar use case.
> >>>
> >>> -Hit
licity of Redis API making this problem (delta update)most apparent.
But, I would imagine many Geode apps has a similar use case.
-Hitesh
From: Michael Stolz
To: dev@geode.apache.org
Sent: Monday, February 27, 2017 9:06 AM
Subject: Re: [DISCUSS] changes to Redis implementation
ase.
>>
>> -Hitesh
>>
>> From: Michael Stolz
>> To: dev@geode.apache.org
>> Sent: Monday, February 27, 2017 9:06 AM
>> Subject: Re: [DISCUSS] changes to Redis implementation
>>It does seem like the operations will often be much smaller than the
blem (delta update)most apparent.
But, I would imagine many Geode apps has a similar use case.
-Hitesh
From: Michael Stolz
To: dev@geode.apache.org
Sent: Monday, February 27, 2017 9:06 AM
Subject: Re: [DISCUSS] changes to Redis implementation
It does seem like the operations will o
The simplicity of Redis API making this problem (delta update)most apparent.
But, I would imagine many Geode apps has a similar use case.
-Hitesh
From: Michael Stolz
To: dev@geode.apache.org
Sent: Monday, February 27, 2017 9:06 AM
Subject: Re: [DISCUSS] changes to Redis
It does seem like the operations will often be much smaller than the data
they are operating on.
It is almost the classic "move the code to the data" pattern.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Mon, Feb 27, 2017 at 10:51 AM, Udo Kohlmeyer
wrote:
Delta could provide us a mechanism to replicate only what is required.
I wonder if we could not create a simple operation replication
framework. Rather than writing a potential large amounts of code for
delta, we replicate only the operation.
On 2/27/17 07:18, Wes Williams wrote:
Replicatin
>>Replicating a whole collection because of 1 change does not really make
too much sense.<<
I agree but won't delta replication prevent sending the entire collection
across the wire?
*Wes Williams | Pivotal Advisory **Data Engineer*
781.606.0325
http://pivotal.io/big-data/pivotal-gemfire
On Mon,
I've quickly gone through the changes for the pull request.
The most significant change of this pull request is that the collections
that initially were regions are single collections (not distributed).
That said, this is something that we've been discussing. The one thing
that I wonder about
Hello,
I just push the changes to remove the @author tags and updated the
RegionProviderTest.
On Fri, Feb 24, 2017 at 7:36 PM, Jason Huynh wrote:
> It looks like travis ci failed on that pr? Also there are some @author
> tags that should probably be scrubbed out
>
> On Fri, Feb 24, 2017 at 4:3
It looks like travis ci failed on that pr? Also there are some @author
tags that should probably be scrubbed out
On Fri, Feb 24, 2017 at 4:33 PM Michael Stolz wrote:
> +1 experimental means changing. Go for it.
>
> --
> Mike Stolz
> Principal Engineer - Gemfire Product Manager
> Mobile: 631-835
+1 experimental means changing. Go for it.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Feb 24, 2017 7:30 PM, "Kirk Lund" wrote:
> +1 for merging in these changes even though they break rolling upgrade for
> redis storage format -- it should be ok to break
+1 for merging in these changes even though they break rolling upgrade for
redis storage format -- it should be ok to break API or data format if it
was "experimental" in all releases so far
On Fri, Feb 24, 2017 at 3:25 PM, Bruce Schuchardt
wrote:
> Gregory Green has posted a pull request that w
17 matches
Mail list logo
