Re: [jira] Updated: (LUCENE-755) Payloads

2007-03-12 Thread Grant Ingersoll
I haven't looked at your latest patch yet, so this is just guesswork, but was thinking in TermScorer, around line 75 or so, we could add: score *= similarity.scorePayload(payloadBuffer); The default Similarity would just return 1. This would allow people to incorporate a score based on

[jira] Updated: (LUCENE-818) IndexWriter should detect when it's used after being closed

2007-03-12 Thread Michael McCandless (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-818: -- Attachment: LUCENE-818.take5.patch Attached patch: removed AlreadyClosedException from

[jira] Updated: (LUCENE-662) Extendable writer and reader of field data

2007-03-12 Thread JIRA
[ https://issues.apache.org/jira/browse/LUCENE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated LUCENE-662: --- Attachment: indexFormat.patch Patch updated and synchornized with the trunk r517330. I have

Re: [jira] Updated: (LUCENE-755) Payloads

2007-03-12 Thread Michael Busch
Grant Ingersoll wrote: I haven't looked at your latest patch yet, so this is just guesswork, but was thinking in TermScorer, around line 75 or so, we could add: score *= similarity.scorePayload(payloadBuffer); TermScorer currently doesn't iterate over the positions. It uses a buffer to load

Re: Flexible indexing

2007-03-12 Thread Marvin Humphrey
On Mar 10, 2007, at 3:27 PM, Michael Busch wrote: I'm going to respond to this over several mails (: and possibly days :) because there's an awful lot here, and I've already implemented a lot of it in KS. We should also make this public, so that users can store their own index metadata.

Re: Flexible indexing

2007-03-12 Thread Marvin Humphrey
On Mar 10, 2007, at 3:27 PM, Michael Busch wrote: - Introduce index format. Nicolas has already written a lot of code in this regard! I worry that going the interface route is going to be too restrictive. When I looked at Nicholas's index format spec, I immediately wanted to add an

Re: Flexible indexing

2007-03-12 Thread Marvin Humphrey
On Mar 10, 2007, at 3:27 PM, Michael Busch wrote: - Introduce index-level metadata. Preferable in XML format, so it will be human readable. Later on, we can store information about the index format in this file, like the codecs that are used to store the data. To provoke thought about

[jira] Commented: (LUCENE-791) Update the Wiki

2007-03-12 Thread Hoss Man (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480184 ] Hoss Man commented on LUCENE-791: - 1) at the moment, the old URLs are still working, these should probably be

Re: Flexible indexing

2007-03-12 Thread Michael Busch
Marvin Humphrey wrote: On Mar 10, 2007, at 3:27 PM, Michael Busch wrote: I'm going to respond to this over several mails (: and possibly days :) because there's an awful lot here, and I've already implemented a lot of it in KS. We should also make this public, so that users can store their

Re: Flexible indexing

2007-03-12 Thread Marvin Humphrey
On Mar 12, 2007, at 2:11 PM, Michael Busch wrote: I think our best option here is to have a closed XML file for the index format/configuration (something like you sent in your other mail) plus a binary file for custom index-level metadata like Grant suggested. Why the binary file? Btw,

[jira] Commented: (LUCENE-794) SpanScorer and SimpleSpanFragmenter for Contrib Highlighter

2007-03-12 Thread Mark Miller (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480207 ] Mark Miller commented on LUCENE-794: Another approach may be to modify the MemoryIndex content to suit the

Re: Flexible indexing

2007-03-12 Thread Michael Busch
Marvin Humphrey wrote: On Mar 12, 2007, at 2:11 PM, Michael Busch wrote: I think our best option here is to have a closed XML file for the index format/configuration (something like you sent in your other mail) plus a binary file for custom index-level metadata like Grant suggested. Why

[jira] Created: (LUCENE-829) StandardBenchmarker#makeDocument does not explicitly close opened files

2007-03-12 Thread Karl Wettin (JIRA)
StandardBenchmarker#makeDocument does not explicitly close opened files --- Key: LUCENE-829 URL: https://issues.apache.org/jira/browse/LUCENE-829 Project: Lucene - Java

[jira] Commented: (LUCENE-794) SpanScorer and SimpleSpanFragmenter for Contrib Highlighter

2007-03-12 Thread Mark Harwood (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480222 ] Mark Harwood commented on LUCENE-794: - How can I ignore fields in a SpanQuery. Now it hits me, rather

Re: Flexible indexing

2007-03-12 Thread Marvin Humphrey
On Mar 12, 2007, at 3:54 PM, Michael Busch wrote: Sounds interesting! I will take a closer look at it... Here's an introduction courtesy of JYaml, a YAML library for Java: http://jyaml.sourceforge.net/tutorial.html For an example of how YAML is well suited to the task of serializing

[jira] Commented: (LUCENE-794) SpanScorer and SimpleSpanFragmenter for Contrib Highlighter

2007-03-12 Thread Mark Miller (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480230 ] Mark Miller commented on LUCENE-794: Yup, we are on the same page. I was just buried in the code at the time,

Re: Flexible indexing

2007-03-12 Thread Grant Ingersoll
On Mar 12, 2007, at 6:54 PM, Michael Busch wrote: Marvin Humphrey wrote: On Mar 12, 2007, at 2:11 PM, Michael Busch wrote: I think our best option here is to have a closed XML file for the index format/configuration (something like you sent in your other mail) plus a binary file for

Re: [jira] Commented: (LUCENE-791) Update the Wiki

2007-03-12 Thread Grant Ingersoll
On Mar 12, 2007, at 4:59 PM, Hoss Man (JIRA) wrote: [ https://issues.apache.org/jira/browse/LUCENE-791? page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#action_12480184 ] Hoss Man commented on LUCENE-791: - 1) at the moment, the

[jira] Commented: (LUCENE-759) Add n-gram tokenizers to contrib/analyzers

2007-03-12 Thread Otis Gospodnetic (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480236 ] Otis Gospodnetic commented on LUCENE-759: - Oh, look at that! [EMAIL PROTECTED] contrib]$ svn st A

Re: [jira] Commented: (LUCENE-759) Add n-gram tokenizers to contrib/analyzers

2007-03-12 Thread Otis Gospodnetic
My bad - I somehow forgot to commit the meat. It's in now. Otis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simpy -- http://www.simpy.com/ - Tag - Search - Share - Original Message From: Patrick Turcotte [EMAIL PROTECTED] To: java-dev@lucene.apache.org Sent:

[jira] Updated: (LUCENE-550) InstantiatedIndex - faster but memory consuming index

2007-03-12 Thread Karl Wettin (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wettin updated LUCENE-550: --- Attachment: trunk.diff.bz2 Patched contrib/benchmark to support InstantiatedIndex. Fixed a bug with

factoring the merge policy

2007-03-12 Thread Steven Parkes
I've been thinking about merge issues for a while and going through IndexWriter to see if I could convince myself I understood it. There are areas I'm interested in exploring tweaking the merge policy. For example, it might be nice to have an optimize-like operation that could look at the number

[jira] Commented: (LUCENE-550) InstantiatedIndex - faster but memory consuming index

2007-03-12 Thread Doron Cohen (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480274 ] Doron Cohen commented on LUCENE-550: That's a good point about the task-benchmark karl! All 4 ReaderTasks are

new query

2007-03-12 Thread Gaurav Srivastava
How to search numbers using Lucene API I an using a demo application so as to search the documents but when i search the numbers or alphanumeric text it appends an empty space and no hits are returned any help would be appreciated