Re: Flexible indexing

Le Lundi 12 Mars 2007 21:34, Marvin Humphrey a écrit : 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

[jira] Resolved: (LUCENE-710) Implement point in time searching without relying on filesystem semantics

[ https://issues.apache.org/jira/browse/LUCENE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-710. --- Resolution: Fixed Implement point in time searching without relying on filesystem

Re: Flexible indexing

Marvin Humphrey wrote: It uses global field semantics, which Hoss won't be happy about. ;) However, I'm grateful to Hoss for past critiques, as they've helped me to refine and improve how Schema works. For instance, as of KS 0.20_02 you can introduce new field_name = FieldSpec

Re: Flexible indexing

Le Dimanche 11 Mars 2007 22:41, Michael Busch a écrit : Hi Grant, I certainly agree that it would be great if we could make some progress and commit the payloads patch soon. I think it is quite independent from FI. FI will introduce different posting formats (see Wiki:

[jira] Created: (LUCENE-830) norms file can become unexpectedly enormous

norms file can become unexpectedly enormous --- Key: LUCENE-830 URL: https://issues.apache.org/jira/browse/LUCENE-830 Project: Lucene - Java Issue Type: Bug Components: Index Affects

[jira] Commented: (LUCENE-252) [PATCH] Problem with Sort logic on tokenized fields

[ https://issues.apache.org/jira/browse/LUCENE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480476 ] Enis Soztutar commented on LUCENE-252: -- I should admit that, considering the case Yonik has mentioned. throwing

[jira] Commented: (LUCENE-830) norms file can become unexpectedly enormous

[ https://issues.apache.org/jira/browse/LUCENE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480520 ] Doron Cohen commented on LUCENE-830: One simple workaround is to disable norms. You mean for some of the

[jira] Commented: (LUCENE-830) norms file can become unexpectedly enormous

[ https://issues.apache.org/jira/browse/LUCENE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480522 ] Doron Cohen commented on LUCENE-830: You mean for some of the fields, using Fieldable's setOmitNorms(). Oops,

[jira] Resolved: (LUCENE-814) javacc on Win32 (cygwin) creates wrong line endings - fix them with 'ant replace'

[ https://issues.apache.org/jira/browse/LUCENE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doron Cohen resolved LUCENE-814. Resolution: Fixed Lucene Fields: [Patch Available] (was: [Patch Available, New])

[jira] Updated: (LUCENE-755) Payloads

[ https://issues.apache.org/jira/browse/LUCENE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch updated LUCENE-755: - Attachment: payloads.patch Attaching a new patch. The previous one didn't apply cleanly anymore

Build failed in Hudson: Lucene-Nightly #22

See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/22/ -- started Checking out http://svn.apache.org/repos/asf/lucene/java/trunk FATAL: null java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkBounds(Buffer.java:454)

Re: Flexible indexing

On Mar 13, 2007, at 2:38 AM, Michael Busch wrote: Global field semantics make our life with FI much easier in a single index. But even with global field semantics we would have the same problem with the IndexWriter.addIndexes() method, no? I'm curious about how you solved that conflict in

Re: Flexible indexing

On Mar 13, 2007, at 2:03 AM, Nicolas Lalevée wrote: At present KS allows you to attach both a Similarity and an Analyzer to a field name via a FieldSpec subclass. I haven't quite figured out how to attach a posting format. Should it return an object, like FieldSpec's similarity() method