[
https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin....
]
Vojtech Juranek commented on ISPN-4751:
---------------------------------------
Hi George, unfortunately the documentation wasn't updated yet. Probably the best way
is to check [XSD
schema|https://github.com/infinispan/infinispan-cachestore-cloud/blob/mas...]
or you can take a look on a [simple
example|https://github.com/vjuranek/ispn-playground-stores/blob/master/sr...],
how to use it with AWS S3. Hopefully all configuration options are clear enough, the only
thing which could be confusing is that the data are stored in AWS buckets named
{{$containerName-$cacheName}} (separated by hyphen, not by underscore as stated in XSD -
it's typo I just noticed). If you have any issue, please let me know.
Hibernate search, infinispan and Amazon S3 -
IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
------------------------------------------------------------------------------------------------------------------
Key: ISPN-4751
URL:
https://issues.jboss.org/browse/ISPN-4751
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Reporter: Lance Ess
Assignee: Vojtech Juranek
I'm trying to use hibernate-search to host a Lucene index on Amazon S3 but I'm
getting the following exception:
{code}
Exception in thread "LuceneIndexesData-CloudCacheStore-0"
java.lang.IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
at org.infinispan.loaders.bucket.Bucket.setBucketId(Bucket.java:84)
at
org.infinispan.loaders.cloud.CloudCacheStore.readFromBlob(CloudCacheStore.java:450)
at
org.infinispan.loaders.cloud.CloudCacheStore.scanBlobForExpiredEntries(CloudCacheStore.java:292)
at org.infinispan.loaders.cloud.CloudCacheStore.purge(CloudCacheStore.java:284)
at
org.infinispan.loaders.cloud.CloudCacheStore.purgeInternal(CloudCacheStore.java:336)
at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:111)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
{code}
The documentation for persisting Lucene indexes on Amazon-S3 is a little sparse but I
think I'm on the right track. I'm trying to start infinispan embedded within my
application so I've specified a path to the infinispan XML as follows in my
hibernate.cfg.xml
{code:xml}
<property
name="hibernate.search.default.directory_provider">infinispan</property>
<property
name="hibernate.search.infinispan.configuration_resourcename">infinispan-amazons3.xml</property>
<property
name="hibernate.search.infinispan.chunk_size">300000000</property>
{code}
And my infinispan-amazons3.xml is:
{code:xml}
<infinispan>
<default>
<loaders>
<cloudStore xmlns="urn:infinispan:config:cloud:5.3"
cloudService="aws-s3"
identity="user"
password="password"
bucketPrefix="bucket">
</cloudStore>
</loaders>
</default>
</infinispan>
{code}
I'm using the following versions (maven pom.xml)
{code}
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-search</artifactId>
<version>4.4.4.Final</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-search-infinispan</artifactId>
<version>4.4.4.Final</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-cachestore-cloud</artifactId>
<version>5.3.0.Final</version>
</dependency>
<dependency>
<groupId>org.jclouds.provider</groupId>
<artifactId>aws-s3</artifactId>
<version>1.4.1</version>
</dependency>
{code}
I initially thought this was related to ISPN-1909 but my version is after the fix for
that issue (5.1.3.CR1, 5.1.3.FINAL)
FYI here's my maven dependency tree (grepped for infinispan)
{code}
$ mvn dependency:tree | grep infinispan
[INFO] +- org.hibernate:hibernate-search-infinispan:jar:4.4.4.Final:compile
[INFO] | \- org.infinispan:infinispan-lucene-directory:jar:5.3.0.Final:compile
[INFO] +- org.infinispan:infinispan-cachestore-cloud:jar:5.3.0.Final:compile
[INFO] | \- org.infinispan:infinispan-core:jar:5.3.0.Final:compile
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)