Here is a simple Java client _for enterprise use_ that I developed for Geode
and distributed to several enterprises. It has similarities and differences for
your goal. This project creates both server and client regions dynamically. It
lists regions, alters regions… really anything that GFSH
Would there be a negative impact in moving PDXType’s to the region level
instead of the cache level? On the positive side, when there is an object with
a variable number of fields being stored in a partitioned region, we would get
rid of the distributed lock. As it is now at the cache level,
“So the default pattern would match all class names?”
This is the most usual case and I believe should therefore be the default.
Placing limitations is the exceptional case. It’s rather frequent during
development that I’ll change my package names and the serializer will blow up
because I
This works in Geode 1.1.0 where GemFire 8 failed:
gfsh> create region --name=Testxxx --type=PARTITION_REDUNDANT_HEAP_LRU
--badProperty=badValue
Is ignoring bad properties by design? Or a bug?
Thanks,
Wes Williams
I'm not following what a "simple operation replication framework" is and how it
applies to the Redis API. If you replicate operations, you still need to update
the data at some point, causing a synchronous replication event so as to
provide HA. What is, in more detail, a "simple operation
for both small and large. We wouldn't want the thing to explode when
it gets converted...
Is there a way to just make it configurable? If they know they want a
"large" set, somehow let them specify it. Otherwise go with the "small"
set?
On Wed, Feb 15, 2017 at 1:01 PM Real
in
> old implementation and new implementation?
>
> 2,3,4) The new implementation would mean all the data for a specific data
> structure is contained in a single bucket. So the individual data
> structures are not quite scalable. How would you allow scaling of a single
>
ementation and new implementation?
>
> 2,3,4) The new implementation would mean all the data for a specific data
> structure is contained in a single bucket. So the individual data
> structures are not quite scalable. How would you allow scaling of a single
> data structure?
&g
In what format do you want the feedback Hitesh? For now I’ll just comment:
1. Redis Type String
No comments except that a future Geode value-add would be to extend the Jedis
client so that the K/V’s are not compressed. In this way OQL and CQ will work.
The tradeoff of this is that the data
Here’s a use-case I’m dealing with right now: A single cluster supporting
multiple applications (i.e. a multi-tenant cluster). One new application wants
to do Spring http session replication. This requires placing 3 Spring jars onto
the start server —classpath=$SPRING_JARS:… It requires a
10 matches
Mail list logo
