On Jun 12, 2008, at 06:00, Sanne Grinovero wrote:
>> Does it somehow involve not having cluster changes (ie intra VM
policy rather than inter VM?)
I don't really understand what you're asking; I hope previous
example contains an answer; it just means you don't need
to lock the index to m
>
>
>> >> Does it somehow involve not having cluster changes (ie intra VM policy
>> rather than inter VM?)
>> I don't really understand what you're asking; I hope previous example
>> contains an answer; it just means you don't need
>> to lock the index to make a "hotcopy" to anywhere.
>>
>
>
> My q
On Jun 10, 2008, at 07:17, Sanne Grinovero wrote:
Hello Emmanuel,
as you asked how to use the SnapshotDeletionPolicy:
when you create the IndexWriter do:
IndexDeletionPolicy policy = new KeepOnlyLastCommitDeletionPolicy();
SnapshotDeletionPolicy snapshotter = new
SnapshotDeletionPolicy(
Hello Emmanuel,
as you asked how to use the SnapshotDeletionPolicy:
when you create the IndexWriter do:
IndexDeletionPolicy policy = new KeepOnlyLastCommitDeletionPolicy();
SnapshotDeletionPolicy snapshotter = new SnapshotDeletionPolicy(policy);
IndexWriter writer = new IndexWriter(dir, auto
On Jun 7, 2008, at 11:32, Sanne Grinovero wrote:
Hi all,
I've been thinking on some more design changes for Hibernate Search,
I hope to start a creative discussion.
A)FSMasterDirectoryProvider and Index Snapshots.
is currently making copies of it's changing index; Using Lucene's
SnapshotDele
