[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463483
]
Doron Cohen commented on LUCENE-140:
Jed, is it possible that when re-creating the index, while IndexWriter is
c
[
https://issues.apache.org/jira/browse/LUCENE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463471
]
jianwu chen commented on LUCENE-542:
Hi, Erik
I can't find more information on this issue. Could you provide more
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463470
]
Jed Wesley-Smith commented on LUCENE-140:
-
BTW. We have looked at all the open files referenced by the VM whe
(Sorry for the cross-posting)
This is a full-time position with an exciting New Venture (now in
stealth mode) and will be based out of Sunnyvale, CA.
We are looking for Java Developer with search, social networks and/or
payment processing related experience.
Required Skills:
2+ yrs of industri
I synched the XML with the HTML and committed, changes should show up
tonight. The regeneration process is now (almost) the same as Solrs
and is covered at http://wiki.apache.org/jakarta-lucene/
HowToUpdateTheWebsite
-Grant
On 1/9/07, Doron Cohen <[EMAIL PROTECTED]> wrote:
Otis Gospodnetic
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463440
]
Jed Wesley-Smith commented on LUCENE-140:
-
Hi Michael,
Thanks for the patch, applied and recreated. Attached
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jed Wesley-Smith updated LUCENE-140:
Attachment: indexing-failure.log
> docs out of order
> -
>
>
I'm not sure we fully understand one another, but I'll try to explain
what I am thinking.
Yes, it has use after sorting. It is used at query time for document
scoring in place of the TF and length norm components (new scorers
would need to be created).
Using an impact based index moves most o
Doron -- you have the idea.
And yes, it would be a substantial change to Lucene scoring. Ideally,
Lucene / doc format would be changed in such a way to support both docId
sorted indexes (and doc-at-a-time processing) and frequency/impact
sorted indexes with term-at-a-time or even score-at-a-tim
[
https://issues.apache.org/jira/browse/LUCENE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Vasiliev updated LUCENE-769:
--
Attachment: DocCachingSorting.patch
> [PATCH] Performance improvement for some cases of sorted
Scoring today goes doc-at-a-time - all scorers and term-posting-readers
advance together; once a new doc is processed, scoring of previous docs is
known and final. This allows maintaining a finite size queue for collecting
best hits. Then, for huge collections, having to exhaustively scan all
posti
[PATCH] Performance improvement for some cases of sorted search
---
Key: LUCENE-769
URL: https://issues.apache.org/jira/browse/LUCENE-769
Project: Lucene - Java
Issue Type: Improvem
[
https://issues.apache.org/jira/browse/LUCENE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463414
]
Nicolas Lalevée commented on LUCENE-755:
The patch I have just upload (payload.patch) is Michael's one (paylo
[
https://issues.apache.org/jira/browse/LUCENE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated LUCENE-755:
---
Attachment: payload.patch
> Payloads
>
>
> Key: LUCENE-755
>
robert engels wrote:
It would appear that NFS Version 2 is not suitable for Lucene. NFS
Version 3 looks like it should work. See
http://nfs.sourceforge.net/#section_a
I will take this opportunity to state again what I've always been told,
and it seems to hold up, using NFS for shared interact
On Jan 9, 2007, at 6:25 AM, Dalton, Jeffery wrote:
e.
f. ],...[docN, freq
,])
Does the impact have any use after it's used to sort the postings?
Can we leave it out of the index format and recalculate at merge-time?
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
---
[
https://issues.apache.org/jira/browse/LUCENE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463377
]
Marcelo F. Ochoa commented on LUCENE-724:
-
Latest code includes:
- The Data Cartridge API is used without co
[
https://issues.apache.org/jira/browse/LUCENE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo F. Ochoa updated LUCENE-724:
Attachment: ojvm-01-09-07.tar.gz
> Oracle JVM implementation for Lucene DataStore also a pr
"Michael McCandless (JIRA)" <[EMAIL PROTECTED]> wrote on 09/01/2007 03:32:27:
> > I think however that the test Mike added does not expose the docs
> > out of order bug - I tried this test without the fix and it only
> > fail on the "gotException assert" - if you comment this assert the
> > test p
I think this is the relevant section:
A8. What is close-to-open cache consistency?
A. Perfect cache coherency among disparate NFS clients is very
expensive to achieve, so NFS settles for something weaker that
satisfies the requirements of most everyday types of file sharing.
Everyday
It would appear that NFS Version 2 is not suitable for Lucene. NFS
Version 3 looks like it should work. See http://nfs.sourceforge.net/
#section_a
I will take this opportunity to state again what I've always been
told, and it seems to hold up, using NFS for shared interactively
updated fil
[
https://issues.apache.org/jira/browse/LUCENE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463358
]
Michael McCandless commented on LUCENE-767:
---
Carrying over from the java-dev list:
Grant Ingersoll wrote
[
https://issues.apache.org/jira/browse/LUCENE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-768.
---
Resolution: Fixed
> Exception in deleteDocument, undeleteAll or setNorm in IndexReade
Hi Michael,
Can you explain in more detail on this bug why this makes you nervous?
Thanks,
Grant
On Jan 9, 2007, at 6:41 AM, Michael McCandless (JIRA) wrote:
maxDoc should be explicitly stored in the index, not derived from
file length
Exception in deleteDocument, undeleteAll or setNorm in IndexReader can fail to
release write lock on close
--
Key: LUCENE-768
URL: https://issues.apache.org/ji
[
https://issues.apache.org/jira/browse/LUCENE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463335
]
Michael McCandless commented on LUCENE-767:
---
Ooh that's great! I think your logic is correct.
But I do se
[
https://issues.apache.org/jira/browse/LUCENE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463322
]
Chuck Williams commented on LUCENE-767:
---
Isn't maxDoc always the same as the docCount of the segment, which is
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463294
]
Michael McCandless commented on LUCENE-140:
---
Jed, one question: when you tested the fix, you fully rebuilt
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-140:
--
Attachment: LUCENE-140-2007-01-09-instrumentation.patch
> docs out of order
> -
Hi,
I wanted to start some discussion about possible future Lucene file /
index formats. This is an extension to the discussion on Flexible
Lucene Indexing discussed on the wiki:
http://wiki.apache.org/jakarta-lucene/FlexibleIndexing
Note: Related sources are listed at the end.
I would like
Term Vectors with positions are written to the "tvf" file like other
term vector information too. There is no extra file containing term
vectors position information. The "tvp" extension seems to be an relict
from earlier days where lucene file extensions where spreaded over
several class files
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463249
]
Michael McCandless commented on LUCENE-140:
---
OK, I created LUCENE-767 for the "maxDoc should be explicitly
maxDoc should be explicitly stored in the index, not derived from file length
-
Key: LUCENE-767
URL: https://issues.apache.org/jira/browse/LUCENE-767
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463247
]
Michael McCandless commented on LUCENE-140:
---
Doron,
> (1) the sequence of ops brought by Jason is wrong:
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463243
]
Michael McCandless commented on LUCENE-140:
---
Jed, thanks for testing the fix!
> Alas, this doesn't appear
35 matches
Mail list logo
