Hi,
By design instance of document database should be treated as lightweight
connection to database storage which adds data unmarshaling features, so
it means that open/close should be lightweight operation.
But now it is not true, we are going to change it, which means that
open/close operation
Hi,
It is very cheap.
At once we fix https://github.com/orientechnologies/orientdb/issues/2901
and https://github.com/orientechnologies/orientdb/issues/2900 and can use
document db instance as jdbc connection and this problem will gone.
On Sun, Oct 19, 2014 at 7:07 AM, odbuser odbus...@gmail.com
At once we fix https://github.com/orientechnologies/orientdb/issues/2901
and https://github.com/orientechnologies/orientdb/issues/2900 and can use
document db instance as jdbc connection and this problem will gone.
What does this mean?
On Monday, October 20, 2014 4:41:19 AM UTC-4, Andrey
I worked around this by clearing the local cache before each use on the
thread. If building the local cache is expensive, I don't like the
workaround since the majority of times, I do not want the local cache
enabled.
orientGraph.getRawGraph().getLocalCache().invalidate();
On Friday,
I spoke too soon. I am getting the OConcurrentModificationException. I
have one thread that does some work and updates a record followed by
another thread that gets the record and updates it. The second thread
fails with OConcurrentModificationException b/c it's getting the record
from the
OGlobalConfiguration.CACHE_LOCAL_ENABLED (cache.local.enabled) was removed
in 2.0-SNAPSHOT since 2.0-M2. Is there a replacement?
--
---
You received this message because you are subscribed to the Google Groups
OrientDB group.
To unsubscribe from this group and stop receiving emails from it,
Hi,
No you always should use local cache but level2 cache was removed, if you
do not use local cache you will get CME on single thread mode.
But you probably have objections.
Could you list them ?
On Thu, Oct 16, 2014 at 5:03 PM, odbuser odbus...@gmail.com wrote:
By CME I assume you mean ConcurrentModificationException. I am not sure
what you mean by single thread mode. I am using orientdb with multiple
threads. I don't remember the impact of having the cache on but so far
have not encountered any issues. I was just wondering why the option was
