Hi,
We are trying to solve cloud replication using asyncEventListeners.However
the sample AsyncEventListener is not getting fired when I try a put. Could
you please look into this. Commands tried out are below.
I am starting to write an AsyncEventListener to store messages to
Cassandra.Howe
Hi,
I am trying to create a an asyncEventqueue thru gfsh and it gives me the
error below :
gfsh>create async-event-queue --id=sampleq7
--listener=test.gemfire.GemFireListener
Could not process command due to error. Error while processing command
Reason : No results received.
Sever throws no e
Thank you Jason.
I have one more question related to this.
I have two options / object structures for storing and retrieving objects.
First one .
Storing objects like : {key :"ConstantString_randomString", List
objects}
and then use queries with like "ConstantString_%" where function index is
Hi,
I would like to add an index to key (keyindex) and the query executed is
going to be like
"constantstring%" where constant string is going to be the constant
prefix in a lile query. In this case can we just go ahead with key index or
should we use a function index ? key indexes are not
Jason,
We are using the Map feature of GemFire and update throws CommitComflict
exceptions when the same key is updated from multiple places at the same
time, how can this be resolved ? This happens only at high contention
though. We are retrying , but still even after a couple of retries it does
thank you that clarifieded my queries.
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
is there an advantage of using one vs other
index on a field vs PDX serialization as both are used in query execution.
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
I have a question regaring the performance metrics of putAll vs storing
objects directly as List.
which would be more performant
1. store object of the form
{ key1, {sessionId, List}}
2.
store each message object in a list with unique key
{key, sessionid, data}
and then use putall for st
1.which is more performant - aggregating on client side and storing objects
as a list and retrieving the whole object as an a list or
2. storing objects using putAll and running queries to get the objects.
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
Jason,
how can we use both together, isnt it redundant as both serve the same
purpose ? making retrieval faster ?
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
10 matches
Mail list logo