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: https://issues.apache.org/jir
want to do this as soon as possible before
3.0 comes out.
> Deprecating InstantiatedIndexWriter
> ---
>
> Key: LUCENE-1948
> URL: https://issues.apache.org/jira/browse/LUCENE-1948
> Project: Lucene - Java
On 10/05/2009 12:22 PM, Karl Wettin (JIRA) wrote:
Deprecating InstantiatedIndexWriter
---
Key: LUCENE-1948
URL: https://issues.apache.org/jira/browse/LUCENE-1948
Project: Lucene - Java
Issue Type: Task
[
https://issues.apache.org/jira/browse/LUCENE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-1948:
Attachment: LUCENE-1948.patch
> Deprecating InstantiatedIndexWri
Deprecating InstantiatedIndexWriter
---
Key: LUCENE-1948
URL: https://issues.apache.org/jira/browse/LUCENE-1948
Project: Lucene - Java
Issue Type: Task
Components: contrib/*
Affects Versions
utable 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
g 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 objec
method?
On Wed, Nov 26, 2008 at 8:44 PM, Karl Wettin <[EMAIL PROTECTED]> wrote:
> I was just about to get on with LUCENE-1462 when I noticed the new
> TokenStream API. (Yeah, I've been really busy with other stuff for a while
> now.)
>
> Rather than keeping Instantiat
Hi Karl,
I can update InstantiatedIndexWriter to work with the new TokenStream
API. What about MemoryIndex? Is it incompatible now as well?
Jason
On 11/26/08, Karl Wettin <[EMAIL PROTECTED]> wrote:
> I was just about to get on with LUCENE-1462 when I noticed the new
> TokenStrea
I was just about to get on with LUCENE-1462 when I noticed the new
TokenStream API. (Yeah, I've been really busy with other stuff for a
while now.)
Rather than keeping InstantiatedIndexWriter in sync with IndexWriter
I'm considering suggesting that we sim
binary yet. Would like to get Karl's
thoughts on supporting binary.
> Enable reader and binary fields in InstantiatedIndexWriter
> --
>
> Key: LUCENE-1332
> URL: https://issues.apache.org/jir
Enable reader and binary fields in InstantiatedIndexWriter
--
Key: LUCENE-1332
URL: https://issues.apache.org/jira/browse/LUCENE-1332
Project: Lucene - Java
Issue Type: Improvement
12 matches
Mail list logo
