[jira] Updated: (LUCENE-1057) indexing doesn't reset token state

[ https://issues.apache.org/jira/browse/LUCENE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated LUCENE-1057: - Attachment: DocumentsWriter.patch test + patch attached. > indexing doesn't reset token state >

[jira] Created: (LUCENE-1057) indexing doesn't reset token state

indexing doesn't reset token state -- Key: LUCENE-1057 URL: https://issues.apache.org/jira/browse/LUCENE-1057 Project: Lucene - Java Issue Type: Bug Reporter: Yonik Seeley IndexWriter (DocumentsW

Re: Payload API

Thanks for the reminder Mike, that should be in there too I think. -Yonik On Nov 17, 2007 9:07 PM, Mike Klaas <[EMAIL PROTECTED]> wrote: > At some point there was support for my suggestion of changing the > deserialization api in Similarity from > > public float scorePayload(byte [] payload, int o

new Token API

Regarding the recent changes in Token (reusability and use char[] instead of Token) 1) If we are deprecating some methods like String termText(), how about at the same time deprecating "String type"? If we want lightweight per-token metadata for communication between filters, an int or a long use

Re: Payload API

On 17-Nov-07, at 5:49 PM, Yonik Seeley wrote: So I think we should change + finalize the payload API before Lucene 2.3 comes out. Single biggest drawback about current payloads is that there isn't any explicit support for adding different types of payloads to the same token. I don't really see

Payload API

So I think we should change + finalize the payload API before Lucene 2.3 comes out. Single biggest drawback about current payloads is that there isn't any explicit support for adding different types of payloads to the same token. I don't really see a good fix to that though, so I'm OK with leaving

[jira] Resolved: (LUCENE-743) IndexReader.reopen()

[ https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch resolved LUCENE-743. -- Resolution: Fixed Committed! Phew!!! > IndexReader.reopen() > > >

[jira] Updated: (LUCENE-743) IndexReader.reopen()

[ https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch updated LUCENE-743: - Attachment: lucene-743-take10.patch Changes: - Updated to current trunk. - Removed println in Se

[jira] Resolved: (LUCENE-1049) Simple toString() for BooleanFilter

[ https://issues.apache.org/jira/browse/LUCENE-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Harwood resolved LUCENE-1049. -- Resolution: Fixed Fix Version/s: 2.3 Lucene Fields: [New, Patch Available] (was: [P

[jira] Commented: (LUCENE-1055) Remove GData from trunk

[ https://issues.apache.org/jira/browse/LUCENE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543309 ] Michael Busch commented on LUCENE-1055: --- So far one user said on java-user that they would like to use gdata.

[jira] Commented: (LUCENE-1052) Add an "termInfosIndexDivisor" to IndexReader

[ https://issues.apache.org/jira/browse/LUCENE-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543306 ] Chuck Williams commented on LUCENE-1052: Michael, thanks for creating an excellent production version of thi

lucene on hadoop

Hi: I am not sure if this list is the right one for this. HBase sits on top of HDFS and MapReduce for structured data. Any thoughts or opinions about doing the same for a text search engine, e.g. Lucene? It'd be nice to have Lucene sitting on top of a distributed file system and a dist