Build: https://builds.apache.org/job/Solr-trunk/1710/
No tests ran.
Build Log (for compile errors):
[...truncated 37347 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
[
https://issues.apache.org/jira/browse/LUCENE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173075#comment-13173075
]
Uwe Schindler commented on LUCENE-3656:
---
Any comments about my explanation to still
[
https://issues.apache.org/jira/browse/LUCENE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173123#comment-13173123
]
Michael McCandless commented on LUCENE-3656:
bq. I think we should stay with
This looks chaotic, but it was in fact a simple OOM followed by a JVM crash,
the errors below are somehow errors in the jUnit code that created corrupt xml
files (there are no such test names, LOL). I fixed the OOM in r1221197, was
caused by to expensive parameters (the test ran with a horrible
Is there a preferred time/manner for a Solr component (e.g. a SearchComponent)
to clean up resources that have been allocated during the time of its
existence, other than via a finalizer? There seems to be nothing for this in
the NamedListInitializedPlugin interface, and yet if you allocate a
Hi
Uwe mentioned on LUCENE-3653 that there are plans to remove RAMDirectory
from Trunk and move to tests only: RAMDirectory is written for tests, not
for production use. There are already plans to remove it from Lucene trunk
and move to tests only. (see full
Hi,
You misunderstood the whole thing. The idea was to maybe replace
RAMDirectory by a clone of MMapDirectory that uses large DirectByteBuffers
outside the JVM heap. The current RAMDirectory is very limited (buffersize
hardcoded to 8 KB, if you have a 50 Gigabyte Index in this RAMDirectory,
[
https://issues.apache.org/jira/browse/LUCENE-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-3598.
Resolution: Fixed
Fix Version/s: 4.0
Improve InfoStream class in
[
https://issues.apache.org/jira/browse/LUCENE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173211#comment-13173211
]
Robert Muir commented on LUCENE-3656:
-
+1, its the right data structure here.
[
https://issues.apache.org/jira/browse/LUCENE-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-3634:
--
Assignee: Michael McCandless
remove old static main methods in core
[
https://issues.apache.org/jira/browse/LUCENE-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173212#comment-13173212
]
Robert Muir commented on LUCENE-3658:
-
thanks for looking at these 2 tests, now you
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-2906:
-
Attachment: SOLR-2906.patch
Updated patch that divides by 2 and adds a unit test for aging out.
Thanks for the clarification Uwe. If the whole idea is a new RAMDirectory
implementation, that is more efficient, then it's ok. I think that the
ideas you write are interesting.
Have you tried MMapDir for read access in comparison to RAMDirectory for a
larger index
I have, and I support the
How about an issue to track this? I'd be glad to do it, but I'm not
really the reporter for it.
-- DM
On 12/20/2011 09:51 AM, Shai Erera wrote:
Thanks for the clarification Uwe. If the whole idea is a new RAMDirectory
implementation, that is more efficient, then it's ok. I think that the
Done: https://issues.apache.org/jira/browse/LUCENE-3659
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: DM Smith [mailto:dmsmith...@gmail.com]
Sent: Tuesday, December 20, 2011 4:08 PM
To:
Improve Javadocs of RAMDirectory to document its limitations
Key: LUCENE-3659
URL: https://issues.apache.org/jira/browse/LUCENE-3659
Project: Lucene - Java
Issue Type: Task
[
https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3659:
--
Description:
Spinoff from several dev@lao issues:
-
[
https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173247#comment-13173247
]
Erick Erickson commented on LUCENE-3659:
From the dev list, didn't want to lose
[
https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173252#comment-13173252
]
Uwe Schindler commented on LUCENE-3659:
---
It's even worse, it uses a buffer size of
[
https://issues.apache.org/jira/browse/LUCENE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173255#comment-13173255
]
Robert Muir commented on LUCENE-3659:
-
I actually think heap versus direct is just an
[
https://issues.apache.org/jira/browse/LUCENE-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3634:
---
Attachment: LUCENE-3634.patch
Patch. I moved IR's main to new
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173345#comment-13173345
]
Shawn Heisey commented on SOLR-2906:
bq. Could you add in the optional time decay as
[
https://issues.apache.org/jira/browse/LUCENE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3656:
--
Fix Version/s: 4.0
3.6
IndexReader's add/removeCloseListener should
[
https://issues.apache.org/jira/browse/LUCENE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-3656.
---
Resolution: Fixed
Committed trunk revision: 1221369
Merged 3.x revision: 1221371
[
https://issues.apache.org/jira/browse/LUCENE-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-3658.
Resolution: Fixed
NRTCachingDir has invalid asserts (if same file name is
[
https://issues.apache.org/jira/browse/LUCENE-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-3631.
Resolution: Fixed
Remove write access from SegmentReader and possibly move
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173378#comment-13173378
]
Erick Erickson commented on SOLR-2906:
--
Right, there's a lot of code to wrap your head
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173378#comment-13173378
]
Erick Erickson edited comment on SOLR-2906 at 12/20/11 6:25 PM:
[
https://issues.apache.org/jira/browse/LUCENE-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-3605:
--
Assignee: Michael McCandless
revisit segments.gen sleeping
[
https://issues.apache.org/jira/browse/LUCENE-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3605:
---
Attachment: LUCENE-3605.patch
Patch: I removed the sleep+retry loop in loading the
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173479#comment-13173479
]
Cody Young commented on SOLR-2242:
--
Simon, any plans for this patch?
The general
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x-java7/1309/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.SolrExampleStreamingTest.testCommitWithin
Error Message:
expected:1 but was:0
Stack Trace:
junit.framework.AssertionFailedError: expected:1 but was:0
If indexwriter hits a non-ioexception from indexExists it leaks a write.lock
Key: LUCENE-3660
URL: https://issues.apache.org/jira/browse/LUCENE-3660
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/LUCENE-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3660:
Attachment: LUCENE-3660.patch
If indexwriter hits a non-ioexception from indexExists it
[
https://issues.apache.org/jira/browse/LUCENE-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173596#comment-13173596
]
Robert Muir commented on LUCENE-3605:
-
I agree... i think we can also remove the now
[
https://issues.apache.org/jira/browse/LUCENE-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173597#comment-13173597
]
Robert Muir commented on LUCENE-3605:
-
I meant getter... you already nuked the setter
move deletes under codec
Key: LUCENE-3661
URL: https://issues.apache.org/jira/browse/LUCENE-3661
Project: Lucene - Java
Issue Type: Task
Affects Versions: 4.0
Reporter: Robert Muir
After
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/11849/
2 tests failed.
REGRESSION: org.apache.lucene.index.TestDuelingCodecs.testEquals
Error Message:
this writer hit an OutOfMemoryError; cannot complete forceMerge
Stack Trace:
java.lang.IllegalStateException: this writer hit
extend LevenshteinAutomata to support transpositions as primitive edits
---
Key: LUCENE-3662
URL: https://issues.apache.org/jira/browse/LUCENE-3662
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/LUCENE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3662:
Attachment: update-moman.patch
as a start, i thought we could try upgrading moman, passing
[
https://issues.apache.org/jira/browse/LUCENE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3662:
Attachment: lev1t.txt
lev1.rev119.txt
lev1.rev115.txt
here is the
[
https://issues.apache.org/jira/browse/LUCENE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3662:
Attachment: LUCENE-3662_upgrade_moman.patch
ok i found the bug, it was a (no longer valid)
[
https://issues.apache.org/jira/browse/LUCENE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3662:
Attachment: LUCENE-3662.patch
updated patch with hacks to the parser and generated Lev1T and
[
https://issues.apache.org/jira/browse/LUCENE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3662:
Attachment: LUCENE-3662.patch
updated patch, hooking this into LevenshteinAutomata.
I wrote a
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/11866/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.update.processor.SignatureUpdateProcessorFactoryTest
Error Message:
Cannot delete
[
https://issues.apache.org/jira/browse/LUCENE-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173843#comment-13173843
]
Shay Banon commented on LUCENE-3654:
ok, so Mr Muir is -1, if people/devs still want
[
https://issues.apache.org/jira/browse/LUCENE-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13173853#comment-13173853
]
Jason Rutherglen commented on LUCENE-3654:
--
+1 There are 3 other MAJOR Apache
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/11868/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.update.processor.SignatureUpdateProcessorFactoryTest
Error Message:
Cannot delete
48 matches
Mail list logo
