Amazing!!! Thank you Charlie!
On Feb 15, 2017 9:11 PM, "Charlie Black" wrote:
> Hello fellow Apache Geode users.
>
> I thought I would share a project with the community where I showcase how
> to add Geospatial indexing to Geode. In this project I simulate vehicle
> sensors reporting thier geo
Hello fellow Apache Geode users.
I thought I would share a project with the community where I showcase how to
add Geospatial indexing to Geode. In this project I simulate vehicle sensors
reporting thier geo location as they travel the California roadways. Geode
will be indexing the data
The Apache Geode team is proud to announce Apache Geode release version 1.1.0
Apache *Geode* is a data management platform that provides a
database-like consistency model, reliable transaction processing and a
shared-nothing architecture to maintain very low latency performance with
high concurren
Does delta propagation make worrying about frequently updated fat collections
moot?
On Feb 15, 2017, at 4:29 PM, Dan Smith
mailto:dsm...@pivotal.io>> wrote:
Doing the spill/unspill option could be pretty tricky to implement, so you have
to do a lot of fancy logic in the transition period. I th
Doing the spill/unspill option could be pretty tricky to implement, so you
have to do a lot of fancy logic in the transition period. I think Jason's
suggestion of configuring things might make more sense.
-Dan
On Wed, Feb 15, 2017 at 1:12 PM, Jason Huynh wrote:
> With the suggestion from Wes, t
With the suggestion from Wes, the constraint on the names would have to
apply 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 wi
Thinking about this, I think that the “spill”/ “unspill” option may actually be
the best solution. If the criteria waffles back and forth along the threshold,
well, that’s the acceptable worst case.
How’s this?:
1) Create a separate region for the collection key
- for fat collections that
We should be careful here on a decision. If we start replicating fat
lists/sets/hash maps synchronously every update, the Geode user will complain
how slow the API is compared with Redis. Note: Redis replicates asynchronously.
For fat collections we’re better off creating a region and suffer
>>>The Redis adapter was designed so that we can scale all the Redis data
structures horizontally. If you bring the data structures to region entry
level, there is no reason for anyone to use our implementation over Redis.
hmm, here we need to understand when we need to create partition-region for
