[
https://issues.apache.org/jira/browse/LUCENE-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Helleringer updated LUCENE-2366:
Attachment: LUCENE-2366.patch
Corrected a path problem in the patch file
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853803#action_12853803
]
Nicolas Helleringer commented on LUCENE-1777:
-
In TestCartesian there is code
[
https://issues.apache.org/jira/browse/LUCENE-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853811#action_12853811
]
Michael McCandless commented on LUCENE-2361:
Hmm are you sure you're setting
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853815#action_12853815
]
Michael McCandless commented on LUCENE-2329:
bq. We could move the if
[
https://issues.apache.org/jira/browse/LUCENE-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2265:
---
Attachment: LUCENE-2265.patch
bq. The problem is it does not handle at least the
The current subject and description of
https://issues.apache.org/jira/browse/LUCENE-2335
is obsolete due to new knowledge.
Is it possible to change it? If not, what is the policy here? To open a
new issue and close the old one?
Cc: To Michael McCandless as he is the reporter of the issue.
If
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2329:
---
Attachment: LUCENE-2329.patch
New patch, init'ing the postings arrays in THPF.start
Locale-based sort by field with low memory overhead
---
Key: LUCENE-2369
URL: https://issues.apache.org/jira/browse/LUCENE-2369
Project: Lucene - Java
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LUCENE-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853838#action_12853838
]
Robert Muir commented on LUCENE-2369:
-
Toke, I still think it would be better to use
[
https://issues.apache.org/jira/browse/LUCENE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853847#action_12853847
]
Toke Eskildsen commented on LUCENE-2335:
I've mis-read Michael McCandless
I am trying to reintegrate the flex branch into current trunk. After this has
done, no more commits to flex! (after a reintegrate, the svn book says, that
you should not touch the branch anymore) - Flex development can then proceed in
trunk. It may happen that solr compilation/tests fail
[
https://issues.apache.org/jira/browse/LUCENE-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853884#action_12853884
]
Toke Eskildsen commented on LUCENE-2369:
The current implementation accepts
[
https://issues.apache.org/jira/browse/LUCENE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toke Eskildsen updated LUCENE-2335:
---
Comment: was deleted
(was: Lotsa devils in the details when you're poking around in the
[
https://issues.apache.org/jira/browse/LUCENE-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853885#action_12853885
]
Toke Eskildsen commented on LUCENE-2369:
Moved from LUCENE-2335 as it really
[
https://issues.apache.org/jira/browse/LUCENE-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853883#action_12853883
]
Earwin Burrfoot commented on LUCENE-2369:
-
I would like to note that new types of
[
https://issues.apache.org/jira/browse/LUCENE-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853886#action_12853886
]
Toke Eskildsen commented on LUCENE-2369:
Earwin, it would be great if this can be
[
https://issues.apache.org/jira/browse/LUCENE-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853887#action_12853887
]
Nicolas Helleringer commented on LUCENE-2366:
-
I reviewed the code as it still
Reintegrate flex branch into trunk
--
Key: LUCENE-2370
URL: https://issues.apache.org/jira/browse/LUCENE-2370
Project: Lucene - Java
Issue Type: Task
Affects Versions: Flex Branch
Reporter:
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2370:
--
Attachment: LUCENE-2370.patch
Here the patch just for review!
You cannot really apply it as
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2370:
--
Attachment: (was: LUCENE-2370.patch)
Reintegrate flex branch into trunk
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2370:
--
Attachment: LUCENE-2370.patch
sorry, new patch.
The flex branch still contains some
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Helleringer updated LUCENE-2359:
Attachment: TEST-2359.patch
Worked again around the code in
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853918#action_12853918
]
Robert Muir commented on LUCENE-2370:
-
bq. we did not miss a change to trunk in flex
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2370:
--
Attachment: LUCENE-2370.patch
Here a new patch with lots of cleanups, thanks rmuir. Also
So, I want to pump my IndexWriter hard and fast with documents.
Removing fsync from FSDirectory helps. But for that I pay with possibility of
index corruption, not only if my node suddenly loses
power/kernelpanics, but also if it
runs out of disk space (which happens more frequently).
I invented
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2370:
--
Attachment: LUCENE-2370-solrfixes.patch
Here some fixes for Solr:
- makes it compile after
On Tue, Apr 06, 2010 at 11:26:23AM +0200, Toke Eskildsen wrote:
The current subject and description of
https://issues.apache.org/jira/browse/LUCENE-2335
is obsolete due to new knowledge.
Is it possible to change it? If not, what is the policy here? To open a
new issue and close the old one?
How often is fsync called? If it's just during calls to commit, then is that
that expensive? I mean, how often do you call commit?
If that's that expensive (do you have some numbers to share) then I think
that's be a neat idea. Though losing a few minutes worth of updates may
sometimes be
Update fileformats spec to match how flex's standard codec writes terms
---
Key: LUCENE-2371
URL: https://issues.apache.org/jira/browse/LUCENE-2371
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2370:
--
Attachment: LUCENE-2370.patch
New patch, reverted all files with whitespace-only changes.
[
https://issues.apache.org/jira/browse/LUCENE-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854069#action_12854069
]
Toke Eskildsen commented on LUCENE-2369:
A few experiments with the current
[
https://issues.apache.org/jira/browse/LUCENE-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854091#action_12854091
]
Shivender Devarakonda commented on LUCENE-2361:
---
Yes I set infostream on all
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2370:
--
Attachment: LUCENE-2370.patch
Here the final patch after cooperative reviewing in IRC. I will
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854112#action_12854112
]
Michael McCandless commented on LUCENE-2370:
The bug is LUCENE-1976 -- after
[
https://issues.apache.org/jira/browse/LUCENE-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reopened LUCENE-1976:
Reopening to fix on 3.1 after flex lands...
isCurrent() and getVersion() on an NRT
[
https://issues.apache.org/jira/browse/LUCENE-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1976:
---
Fix Version/s: 3.1
isCurrent() and getVersion() on an NRT reader are broken
[
https://issues.apache.org/jira/browse/LUCENE-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854120#action_12854120
]
Michael McCandless commented on LUCENE-2361:
Hmm but the above infoStream
On Tue, Apr 6, 2010 at 10:11 AM, Earwin Burrfoot ear...@gmail.com wrote:
So, I want to pump my IndexWriter hard and fast with documents.
Nice.
Removing fsync from FSDirectory helps. But for that I pay with possibility of
index corruption, not only if my node suddenly loses
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854134#action_12854134
]
Uwe Schindler commented on LUCENE-2370:
---
Committed revision: 931278
I leave the
The freeze is over, we merged successfully.
If you had a flex branch checked out:
svn switch https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From:
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2329.
Resolution: Fixed
Third time's a charm?
Use parallel arrays instead of
[
https://issues.apache.org/jira/browse/LUCENE-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854149#action_12854149
]
Shivender Devarakonda commented on LUCENE-2361:
---
I did not see any
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854151#action_12854151
]
Toke Eskildsen commented on LUCENE-1990:
I did a checkout with
{code}
svn co
[
https://issues.apache.org/jira/browse/LUCENE-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1976.
Resolution: Fixed
OK fixed on 3.1.
isCurrent() and getVersion() on an NRT
[
https://issues.apache.org/jira/browse/LUCENE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-2370.
---
Resolution: Fixed
Mike fixed the missing merges! Thanks.
Reintegrate flex branch into
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854174#action_12854174
]
Michael McCandless commented on LUCENE-1990:
OK indeed now I can see the
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1990.
Resolution: Fixed
Fix Version/s: (was: Flex Branch)
[
https://issues.apache.org/jira/browse/LUCENE-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed LUCENE-2332.
-
Resolution: Invalid
Flex was merged, so this is no longer needed.
Mrge CharTermAttribute and
Replace deprecated TermAttribute by new CharTermAttribute
-
Key: LUCENE-2372
URL: https://issues.apache.org/jira/browse/LUCENE-2372
Project: Lucene - Java
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854199#action_12854199
]
Uwe Schindler commented on LUCENE-2302:
---
I will create a patch with option #2 and
[
https://issues.apache.org/jira/browse/LUCENE-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854209#action_12854209
]
Robert Muir commented on LUCENE-2302:
-
bq. I will create a patch with option #2 and
Change StandardTermsDictWriter to work with streaming and append-only
filesystems
-
Key: LUCENE-2373
URL: https://issues.apache.org/jira/browse/LUCENE-2373
Project:
[
https://issues.apache.org/jira/browse/LUCENE-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854240#action_12854240
]
Andrzej Bialecki commented on LUCENE-2373:
---
Just noticed that the same problem
Add introspection API to AttributeSource/AttributeImpl
--
Key: LUCENE-2374
URL: https://issues.apache.org/jira/browse/LUCENE-2374
Project: Lucene - Java
Issue Type: Improvement
Add introspection API to AttributeSource/AttributeImpl
--
Key: LUCENE-2375
URL: https://issues.apache.org/jira/browse/LUCENE-2375
Project: Lucene - Java
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler deleted LUCENE-2375:
--
Add introspection API to AttributeSource/AttributeImpl
Running out of disk space with fsync disabled won't lead to corruption.
Even kill -9 the JRE process with fsync disabled won't corrupt.
In these cases index just falls back to last successful commit.
It's only power loss / OS / machine crash where you need fsync to
avoid possible corruption
[
https://issues.apache.org/jira/browse/LUCENE-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854254#action_12854254
]
Earwin Burrfoot commented on LUCENE-2373:
-
And then IndexOutput.seek() can be
java.lang.OutOfMemoryError:Java heap space
--
Key: LUCENE-2376
URL: https://issues.apache.org/jira/browse/LUCENE-2376
Project: Lucene - Java
Issue Type: Bug
Components: Index
Affects
[
https://issues.apache.org/jira/browse/LUCENE-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shivender Devarakonda updated LUCENE-2376:
--
Attachment: InfoStreamOutput.txt
I attached the info stream output from the
Earwin - do you have some numbers to share on the running time of the
indexing application? You've mentioned that if you take out fsync into a BG
thread, the running time improves, but I'm curious to know by how much.
Shai
On Wed, Apr 7, 2010 at 2:26 AM, Earwin Burrfoot ear...@gmail.com wrote:
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12854348#action_12854348
]
Shai Erera commented on LUCENE-1709:
One more thing - change benchmark tests to run
Enable the use of NoMergePolicy and NoMergeScheduler by Benchmark
-
Key: LUCENE-2377
URL: https://issues.apache.org/jira/browse/LUCENE-2377
Project: Lucene - Java
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2377:
---
Attachment: LUCENE-2377.patch
Patch includes both fix to CreateIndexTask as well as relevant tests
64 matches
Mail list logo