Hi Micahel:
After removing isDelete(), the index loads in 430 ms.
Thanks
-john
On 10/21/07, Michael Busch <[EMAIL PROTECTED]> wrote:
>
> John Wang wrote:
>
> >
> > Since all three methods loads docids into an int[], the lookup time is
> the
> > same for all three methods, what's
> > differen
[
https://issues.apache.org/jira/browse/LUCENE-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536872
]
Grant Ingersoll commented on LUCENE-1001:
-
{quote}
public interface PayloadSpans extends Spans { // as above
[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536866
]
Michael McCandless commented on LUCENE-743:
---
{quote}
Oh and Mike, thanks for bearing with me :-)
{quote}
T
[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536862
]
Michael Busch commented on LUCENE-743:
--
{quote}
What about a new constructor for MultiReader/ParallelReader that
[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536848
]
Yonik Seeley commented on LUCENE-743:
-
What about a new constructor for MultiReader/ParallelReader that implement
[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536845
]
Michael Busch commented on LUCENE-743:
--
{quote}
I think this is OK?
{quote}
This was essentially the reason why
[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536827
]
Michael McCandless commented on LUCENE-743:
---
{quote}
* MultiReader/ParallelReader must not incref the s
[
https://issues.apache.org/jira/browse/LUCENE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll closed LUCENE-486.
--
Resolution: Won't Fix
> Core Test should not have dependencies on the Demo code
> -
[
https://issues.apache.org/jira/browse/LUCENE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536813
]
Mark Miller commented on LUCENE-1015:
-
Finishing up LUCENE-831 would seem like a good way to add this as well --
[
https://issues.apache.org/jira/browse/LUCENE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-1015:
Attachment: LUCENE-1015.patch
First draft at a patch to add long and double FieldCache sup
[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536805
]
Michael Busch commented on LUCENE-743:
--
{quote}
With that change, plus the change below, your example works fine
On Oct 22, 2007, at 10:09 AM, Marvin Humphrey wrote:
The conclusion I reached was that you needed to have a dedicated
TermEnum for each field, implying individual term dictionary files
(.tis, .tii).
I realized that I needed to explain this.
If KS allows users to supply Perl sort subs as c
Hoss wrote on the user list...
Terms when indexed are allways ordered lexigraphically (using
Term.compareTo which uses String.compareTo) ... regardless of what
field
or language they are in, so "Range Queries" must do their comparisons
lexigraphically as well.
because all Terms are indexed
Michael Busch wrote:
If you store unique docIds, then there are no two documents that share
the same value. That means, that each value gets its own entry in the
dictionary and to load each value it is necessary to perform two random
I/O seeks (one for term lookup + one to open the posting list).
[
https://issues.apache.org/jira/browse/LUCENE-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1020.
Resolution: Fixed
> Basic tool for checking & repairing an index
> ---
[
https://issues.apache.org/jira/browse/LUCENE-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1022.
Resolution: Fixed
> IndexWriter.setInfoStream should percolate down to mergePolicy
[
https://issues.apache.org/jira/browse/LUCENE-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-1028.
-
Resolution: Fixed
Just committed this fix.
Thanks Kyle!
> Weight is not serializable for some
[
https://issues.apache.org/jira/browse/LUCENE-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-1028:
Priority: Major (was: Critical)
Lucene Fields: [Patch Available] (was: [Patch Available,
[
https://issues.apache.org/jira/browse/LUCENE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536589
]
Marko Asplund commented on LUCENE-1029:
---
Perhaps it could be expressed more accurately using the following sen
19 matches
Mail list logo
