lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Updated: (LUCENE-1948) Deprecating InstantiatedIndexWriter
Date Sat, 14 Nov 2009 22:16:39 GMT


Uwe Schindler updated LUCENE-1948:

    Fix Version/s:     (was: 3.0)

I move this to 3.1. The writer was already transformed to the new TokenStream API (not really
effective, but works). We can deprecate it it 3.1 if needed.

> Deprecating InstantiatedIndexWriter
> -----------------------------------
>                 Key: LUCENE-1948
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: contrib/*
>    Affects Versions: 2.9
>            Reporter: Karl Wettin
>            Assignee: Karl Wettin
>             Fix For: 3.1
>         Attachments: LUCENE-1948.patch
> I suppose that should have been suggested before 2.9 rather than  
> after...
> There are at least three reasons to why I want to do this:
> The code is based on the behaviour or the Directory IndexWriter as of  
> 2.3 and I have not been touching it since then. If there will be  
> changes in the future one will have to keep IIW in sync, something  
> that's easy to forget.
> There is no locking which will cause concurrent modification  
> exceptions when accessing the index via searcher/reader while  
> committing.
> It use the old token stream API so it has to be upgraded in case it  
> should stay.
> The java- and package level docs have since it was committed been  
> suggesting that one should consider using II as if it was immutable  
> due to the locklessness. My suggestion is that we make it immutable  
> for real.
> Since II is ment for small corpora there is very little time lost by  
> using the constructor that builts the index from an IndexReader. I.e.  
> rather than using InstantiatedIndexWriter one would have to use a  
> Directory and an IndexWriter and then pass an IndexReader to a new  
> InstantiatedIndex.
> Any objections?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message