ConstantObjectTable
by Mircea Markus
Hi,
I remember we had this discussion at one point, sorry if I am repeating it.
ConstantObjectTable has all the externalizer's statically defined within it. Can it just read them on the fly from the annotations existing on the object it needs to serialize? I.e. if e.g. TransientMortalCacheEntry is annotated as @Marshallable why is it needed to add it to the ConstantObjectTable again?
Cheers,
Mircea
13 years, 6 months
Next release
by Mircea Markus
Hi,
We have 29 issues fixed on 4.2.Beta - not bad at all!
I wouldn't like to release a BETA until ISPN-180 is done, as this requires some very relevant changes.
I'm thinking to release another ALPHA3 tomorrow. Would that be okay with you?
Cheers,
Mircea
13 years, 6 months
InfinispanDirectory: question about distLocksCache
by Tristan Tarrant
Hi Sanne,
I have a question regarding the distLocksCache in the new
InfinispanDirectory: can the same replicated volatile cache be shared by
different Indexes (obviously with differing indexNames) ?
Thanks
Tristan
13 years, 6 months
Problem checking in a SVN property change
by "이희승 (Trustin Lee)"
I'm getting the following error when I try to add a directory to svn:ignore:
trustin@vault ~/workspace/infinispan-4.0
$ svn commit
Adding demos\lucene-directory-demo\target
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden) in response to
CHECKOUT request for
'/repos/infinispan/!svn/ver/1551/branches/4.0.x/demos/lucene-directory-demo'
svn: Your commit message was left in a temporary file:
svn: 'C:\Users\trustin\workspace\infinispan-4.0\svn-commit.tmp'
Any clue? Should I contact JBoss.org team or is it just a configuration
problem?
Trustin
--
what we call human nature in actuality is human habit
http://gleamynode.net/
13 years, 7 months
put with SKIP_REMOTE_LOOKUP loads from the cache store
by Sanne Grinovero
Hello,
while investigating why building an index is very slow when a
CacheStore is enabled, I just discovered that if I'm using
cache.withFlags(Flag.SKIP_REMOTE_LOOKUP).put( key, value )
it will load the previous value from the CacheStore;
I really don't need the previous value, especially annoying as either
there is no data to load, making it pointless, or it will load huge
BLOBs which aren't needed.
at org.infinispan.loaders.LockSupportCacheStore.load(LockSupportCacheStore.java:100)
at org.infinispan.interceptors.CacheLoaderInterceptor.loadIfNeeded(CacheLoaderInterceptor.java:138)
at org.infinispan.interceptors.CacheLoaderInterceptor.visitPutKeyValueCommand(CacheLoaderInterceptor.java:78)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118)
at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:132)
at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:57)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118)
at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:172)
at org.infinispan.interceptors.TxInterceptor.visitPutKeyValueCommand(TxInterceptor.java:120)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118)
at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:87)
at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:58)
at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:57)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118)
at org.infinispan.interceptors.BatchingInterceptor.handleDefault(BatchingInterceptor.java:76)
at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:57)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76)
at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:273)
at org.infinispan.CacheDelegate.put(CacheDelegate.java:427)
at org.infinispan.CacheSupport.put(CacheSupport.java:28)
at org.infinispan.lucene.InfinispanIndexOutput.storeCurrentBuffer(InfinispanIndexOutput.java:167)
InfinispanIndexOutput.java:167 reads:
metadataCache.withFlags(Flag.SKIP_REMOTE_LOOKUP,
Flag.SKIP_LOCKING).put(fileKey, file);
So I'd like to add a check for SKIP_REMOTE_LOOKUP in
org.infinispan.interceptors.CacheLoaderInterceptor.loadIfNeeded:116
Other tests appear to pass, but I'm wondering if the flag name is
appropriate for this change, or if a new flag should be added
"SKIP_STORE_READ"
to make a difference between skipping a RPC call or a CacheLoader call.
What do you think?
Regards,
Sanne
13 years, 7 months
