Ugh, good point. I thought the unit tests would have trapped a dumb-ass mistake like
this.
The reason for transforming the name of the bucket is that we usually use hashcodes as the
bucket name, which can take Integer.MIN_VALUE to Integer.MAX_VALUE. These are then
translated into Strings, and this becomes the name of the storage unit, e.g., 12345.bucket
in the FileCacheStore. Now filesystems are happy to accept a -12345.bucket but certain
cloud storage providers barf when encountering the '-' character. Hence the
transformation to A12345.bucket in some cases.
Cheers
Manik
PS: pushing up a new snapshot as I type, containing this fix + lower verbosity on
eviction-related lock timeouts.
On 3 Feb 2010, at 17:16, Philippe Van Dyck wrote:
And BTW, why do it ?
p
---------- Forwarded message ----------
From: Philippe Van Dyck <pvdyck(a)gmail.com>
Date: Wed, Feb 3, 2010 at 6:15 PM
Subject: CloudCacheStore Bug
To: infinispan -Dev List <infinispan-dev(a)lists.jboss.org>
Hi all,
there is a bug in CloudCacheStore that makes me feel like I am the only one using it ;-)
in CR4 : if you change the "-" sign to "A" in getBucketName ... you
need to do the opposite somewhere (or call it every time) ;-)
WDYT ?
p
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org