Mike, The codebase for lucene.net should be almost identical to java's
3.0.3 release, and LUCENE-1044 is included in that.
Itamar, are you committing the index regularly? I only ask because I can't
reproduce it myself by forcibly terminating the process while it's
indexing. I've tried both
Christopher,
I used the IndexBuilder app from here
https://github.com/synhershko/Talks/tree/master/LuceneNeatThings with a
8.5GB wikipedia dump.
After running for 2.5 days I had to forcefully close it (infinite loop in
the wiki-markdown parser at 92%, go figure), and the 40-something GB index
I
Sami Siren created SOLR-3540:
Summary: MultiCoreExampleTest and MultiCoreEmbedded test clash
with each other
Key: SOLR-3540
URL: https://issues.apache.org/jira/browse/SOLR-3540
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren updated SOLR-3540:
-
Attachment: SOLR-3540.patch
this patch should fix the issue
MultiCoreExampleTest and
Hi,
While looking at some of the test failures it occurred to me that it
would be great to have a tiny addition to the junit output for
succesfull tests. Now if a test succeeds it only prints out something
like this:
[junit4] Suite: org.apache.solr.analysis.TestKeepFilterFactory
[junit4]
Thijs Vonk created SOLR-3541:
Summary: Not all libs are copied into solrj-lib
Key: SOLR-3541
URL: https://issues.apache.org/jira/browse/SOLR-3541
Project: Solr
Issue Type: Bug
hmm, actually the html report (and generate-test-reports) displays
this information nicely so i don't know if this is necessary.
On Wed, Jun 13, 2012 at 9:55 AM, Sami Siren ssi...@gmail.com wrote:
Hi,
While looking at some of the test failures it occurred to me that it
would be great to have
[
https://issues.apache.org/jira/browse/SOLR-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thijs Vonk updated SOLR-3541:
-
Attachment: SOLR-3541-trunk.patch
SOLR-3541-4x.patch
Patches for 4x and trunk
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/305/
1 tests failed.
REGRESSION: org.apache.solr.spelling.suggest.SuggesterTest.testRebuild
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at
[
https://issues.apache.org/jira/browse/SOLR-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren resolved SOLR-3541.
--
Resolution: Fixed
Assignee: Sami Siren
Thijs: I just committed the fix. Thanks!
[junit4] Suite: org.apache.solr.analysis.TestKeepFilterFactory
[junit4] Completed on J0 in 0.22s, 1 test
If that also had a time stamp when the test started it would be, in
some cases, helpful to see what other tests were running at the same
The event log contains this information, it's
Hi Andi,
Am 13.06.2012 02:30, schrieb Andi Vajda:
In your patch, instead of including functions.h, add this to JArray.h after
the #include macros.h line:
That worked, thank you.
fs
[
https://issues.apache.org/jira/browse/LUCENE-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294257#comment-13294257
]
Simon Willnauer commented on LUCENE-4142:
-
+1 looks good to me
On Wed, Jun 13, 2012 at 10:45 AM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
[junit4] Suite: org.apache.solr.analysis.TestKeepFilterFactory
[junit4] Completed on J0 in 0.22s, 1 test
If that also had a time stamp when the test started it would be, in
some cases, helpful to see what
On Wed, Jun 13, 2012 at 11:41 AM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
So how about if something similar was printed from different aspect:
NOTE: All tests that were running at the same time: [TestA, TestB, TestC]
I think this would be noisy -- if you have multiple jvms it's normal
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java7-64/54/
1 tests failed.
REGRESSION: org.apache.solr.search.TestSort.testRandomFieldNameSorts
Error Message:
Over 0.2% oddities in test: 12/5765 have func/query parsing semenatics gotten
broader?
Stack Trace:
This would be visible only for failed tests (no point in printing it
for anything else)
Yes, but it'd require higher-level analysis (cross-jvm). Another
element of difficulty is that I also had a plan to distribute suites
physically to different machines at some point (and the overlap
wouldn't
In my opinion, the separate JVMs should not produce test failures or affect
each other, because every JVM gets its own temporary directory for running
tests and creating indexes.
Lucene respects this completely, so running 2 test suites in parallel acts like
running them on different machines
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294293#comment-13294293
]
Mikhail Khludnev commented on SOLR-3535:
Yonik,
do you mean XMLLoader (as well as
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/63/
2 tests failed.
REGRESSION: org.apache.solr.cloud.LeaderElectionTest.testStressElection
Error Message:
Could not get leader props
Stack Trace:
java.lang.RuntimeException: Could not get leader props
at
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294313#comment-13294313
]
Ryan McKinley commented on SOLR-3535:
-
I think the suggestion is to make nestable
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/101/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestNRTThreads.testNRTThreads
Error Message:
Thread threw an uncaught exception, thread: Thread[Thread-923,5,]
Stack Trace:
java.lang.RuntimeException: Thread
[
https://issues.apache.org/jira/browse/SOLR-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294347#comment-13294347
]
Robert Muir commented on SOLR-3540:
---
Thanks for tracking this down Sami! I was hitting
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294348#comment-13294348
]
Ryan McKinley commented on SOLR-3535:
-
off hand, the big complication I see is how to
[
https://issues.apache.org/jira/browse/LUCENE-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4142.
-
Resolution: Fixed
Fix Version/s: 5.0
4.0
AnalyzerWrapper doesn't
Build: https://builds.apache.org/job/Solr-4.x/8/
1 tests failed.
FAILED: org.apache.solr.cloud.RecoveryZkTest.testDistribSearch
Error Message:
Thread threw an uncaught exception, thread: Thread[Lucene Merge Thread #2,6,]
Stack Trace:
java.lang.RuntimeException: Thread threw an uncaught
On Tue, Jun 12, 2012 at 10:24 PM, Yonik Seeley
yo...@lucidimagination.com wrote:
I just checked in a fix (hopefully) for this.
The snap puller was creating a temp directory that only used down to
seconds precision. I've changed it to milliseconds.
Can this somehow be fixed to not rely on
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/64/
1 tests failed.
REGRESSION: org.apache.solr.spelling.suggest.SuggesterTSTTest.testRebuild
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at
[
https://issues.apache.org/jira/browse/LUCENE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294423#comment-13294423
]
Michael McCandless commented on LUCENE-4120:
+1 to commit. Thanks Adrien!
[
https://issues.apache.org/jira/browse/LUCENE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294427#comment-13294427
]
Michael McCandless commented on LUCENE-4132:
I dislike chaining (return this
I don't think any tests are writing to the source tree anymore: see
https://issues.apache.org/jira/browse/SOLR-3112,
https://issues.apache.org/jira/browse/SOLR-3268
Jenkins runs 'svn status' after all tests execute and fails the build
if its not clean.
So I think the only likely possibilities for
[
https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-2878:
--
Attachment: LUCENE-2878.patch
Patch adding positions() support to SloppyPhraseScorer.
Some
[
https://issues.apache.org/jira/browse/LUCENE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-4132:
---
Attachment: LUCENE-4132.patch
Patch removes ReadOnlyConfig and the tests from TestIWC that ensure
On Wed, Jun 13, 2012 at 7:58 AM, Michael McCandless
luc...@mikemccandless.com wrote:
On Tue, Jun 12, 2012 at 10:24 PM, Yonik Seeley
yo...@lucidimagination.com wrote:
I just checked in a fix (hopefully) for this.
The snap puller was creating a temp directory that only used down to
seconds
Sebastian Lutze created SOLR-3542:
-
Summary: Highlighter: Integration of LUCENE-4133 (Part of
LUCENE-3440)
Key: SOLR-3542
URL: https://issues.apache.org/jira/browse/SOLR-3542
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Lutze updated SOLR-3542:
--
Attachment: SOLR-3542.patch
Highlighter: Integration of LUCENE-4133 (Part of LUCENE-3440)
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294461#comment-13294461
]
Sebastian Lutze commented on LUCENE-3440:
-
Hi Koji,
here's the Solr-Integration:
[
https://issues.apache.org/jira/browse/SOLR-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Lutze updated SOLR-3542:
--
Description:
This patch integrates a weight-based approach for sorting highlighted
fragments.
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294466#comment-13294466
]
Erik Hatcher commented on SOLR-3535:
bq. off hand, the big complication I see is how to
So I think the only likely possibilities for test interference across
JVMS are things like using same temp directory outside of the source
tree or under some svn-ignore'd part of the source tree, or using the
same network port numbers, etc.
Temp directories shouldn't be a problem if they're
I added to the email notification regex in all non-Maven ASF Jenkins jobs to
capture this failure:
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due
to exception hudson.remoting.RequestAbortedException:
hudson.remoting.RequestAbortedException: java.net.SocketException:
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294500#comment-13294500
]
Yonik Seeley commented on SOLR-3535:
bq. At first blush, I think we'd want a single
On Wed, Jun 13, 2012 at 10:13 AM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
So I think the only likely possibilities for test interference across
JVMS are things like using same temp directory outside of the source
tree or under some svn-ignore'd part of the source tree, or using the
[
https://issues.apache.org/jira/browse/LUCENE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-4120.
--
Resolution: Fixed
Fix Version/s: 5.0
Committed (r1349826 and r1349830 on trunk, and
foo-dependency-1.0.jar does stuff with java.io.tmpdir it could create
an issue correct? or does the test runner also set this sysprop to the
sandbox dir for slave jvms (if it doesn't already but can, that
would be very cool, more safety).
True, we could alter java.io.tmpdir. There is actually
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294504#comment-13294504
]
Jack Krupansky commented on SOLR-3535:
--
Maybe there should be a block-doc-aware
I could never repro this but I think I found the cause (just committed
the fix)...
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jun 13, 2012 at 6:45 AM, jenk...@sd-datasolutions.de wrote:
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/101/
1 tests
Was it a race condition of some sort? Why do you think it wasn't
reproducible from the same seed?
Dawid
On Wed, Jun 13, 2012 at 5:04 PM, Michael McCandless
luc...@mikemccandless.com wrote:
I could never repro this but I think I found the cause (just committed
the fix)...
Mike McCandless
[
https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-2878:
--
Attachment: LUCENE-2878.patch
This fixes the MultiPhraseQuery tests. Simplifies the
It was a thread scheduling issue.
The test opened an IndexWriter, launched indexing threads, then opened
the first NRT reader.
The failure would happen (as best I can figure out...) if a merge
completed before the NRT reader was opened.
Mike McCandless
http://blog.mikemccandless.com
On Wed,
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/104/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.lucene.queryparser.flexible.standard.TestNumericQueryParser
Error Message:
Unparseable date: 1864.08.28 9:23 44 -0500 1864
Stack Trace:
Hi Java devs,
I'm a Lucene.Net committer, and there is a chance we have a bug in our
FSDirectory implementation that causes indexes to get corrupted when
indexing is cut while the IW is still open. As it roots from some
retroactive fixes you made, I'd appreciate your feedback.
Correct me if I'm
Hi Itamar,
One quick question: does Lucene.Net include the fixes done for
LUCENE-1044 (to fsync files on commit)? Those are very important for
an index to be intact after OS/JVM crash or power loss.
More responses below:
On Tue, Jun 12, 2012 at 8:20 PM, Itamar Syn-Hershko ita...@code972.com
[
https://issues.apache.org/jira/browse/SOLR-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-3240:
-
Attachment: SOLR-3240.patch
Ok. I think I have a version here that will never compute scores, without
: In my opinion, the separate JVMs should not produce test failures or
: affect each other, because every JVM gets its own temporary directory
: for running tests and creating indexes.
I don't think anyone would disagree with that opinion -- but having a
common opinion doesn't magically make
[
https://issues.apache.org/jira/browse/LUCENE-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-4121:
-
Attachment: LUCENE-4121.patch
First version of the patch.
I first tried to replace the size
[
https://issues.apache.org/jira/browse/LUCENE-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294560#comment-13294560
]
Alex Liu commented on LUCENE-3759:
--
is there any performance concern?
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294569#comment-13294569
]
Hoss Man commented on SOLR-3535:
bq. The necessity to treat multiple docs as a single
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/81/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.MultiCoreExampleJettyTest.testMultiCore
Error Message:
IOException occured when talking to server at:
http://localhost:53802/example/corefoo
Stack Trace:
Looks like there's still something wrong, i'll look more into this
tomorrow unless someone get's there first
13381 T141 oasc.CoreContainer.reload Reloading SolrCore 'core0' using
instanceDir:
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only-4.x/checkout/solr/example/multicore/core0
[
https://issues.apache.org/jira/browse/LUCENE-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294621#comment-13294621
]
Robert Muir commented on LUCENE-4135:
-
Test blasts random numbers (in a loop) until
[
https://issues.apache.org/jira/browse/LUCENE-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4135.
-
Resolution: Fixed
Fix Version/s: 5.0
4.0
TestNumericQueryParser
On Wed, Jun 13, 2012 at 6:11 PM, Michael McCandless
luc...@mikemccandless.com wrote:
It was a thread scheduling issue.
The test opened an IndexWriter, launched indexing threads, then opened
the first NRT reader.
The failure would happen (as best I can figure out...) if a merge
completed
it could be as simple as a flaky DNS or something: e.g. on my internet
connection when this happens, my ISP (verizon) returns 404. So that
would fail this test, because the content would be different.
Ill commit a change for the test to assume(httpCode == 200).
On Tue, Jun 12, 2012 at 10:26 PM,
Ok, thanks. These will be hard to reproduce (thread races). There is
so much room for experimenting though -- with the right
instrumentation you could have thread traces and visualize these...
much like with the jvms/ tests we talked in the other thread.
Next GSoC :)
Dawid
On Wed, Jun 13, 2012
ie: tests in seperate JVMs shouldn't affect eachother, but in spite of
best intentions they might, and having timestamps would help discover
that.
They do -- look at the html report, it contains timestamps. I'll add
them to the txt report in the next version.
Dawid
I committed a fix for this. its the same as LUCENE-4135
On Wed, Jun 13, 2012 at 12:15 PM, jenk...@sd-datasolutions.de wrote:
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/104/
2 tests failed.
FAILED:
[
https://issues.apache.org/jira/browse/LUCENE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294596#comment-13294596
]
Shai Erera commented on LUCENE-4132:
If there are no objections, I'd like to commit
[
https://issues.apache.org/jira/browse/LUCENE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294626#comment-13294626
]
Robert Muir commented on LUCENE-4132:
-
I still feel the same way as before. I'm sorry
[
https://issues.apache.org/jira/browse/LUCENE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294632#comment-13294632
]
Michael McCandless commented on LUCENE-4132:
Please don't rush this Shai.
I
I would love to have a JVM impl that had random yet repeatable (with a
seed) thread scheduling
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jun 13, 2012 at 1:46 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
Ok, thanks. These will be hard to reproduce (thread races). There
This would require some kind of quantified per thread time
allocation... and would most likely be ruined by any I/O or some other
kind of external stimuli? Interesting idea but I don't think it's
possible to achieve.
There's been some talk about tools to detect data races at the hotspot
mailing
I don't think any of this is the problem.
The reproducibility problem in my eyes is clear:
...
while (System.currentTimeMillis() stopTime
...
On Wed, Jun 13, 2012 at 4:05 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
This would require some kind of quantified per thread time
On Wed, Jun 13, 2012 at 4:05 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
This would require some kind of quantified per thread time
allocation...
It would, and would probably have to have control down in the OS and CPU.
and would most likely be ruined by any I/O or some other
kind
while (System.currentTimeMillis() stopTime
Yeah... we should really avoid depending on wall time. This is a
problem even if you'd like to debug such a test because debugging runs
with an agent, this is typically slower to boot, depends on background
load, etc.
D.
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294650#comment-13294650
]
Mikhail Khludnev commented on SOLR-3535:
assuming that at the hight level of
[
https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294678#comment-13294678
]
Hoss Man commented on SOLR-3535:
bq. I don't feel that this rich model is covered with
[
https://issues.apache.org/jira/browse/LUCENE-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4137:
--
Attachment: LUCENE-4137.patch
Simplified patch (only checks for overflow). I will commit this
[
https://issues.apache.org/jira/browse/SOLR-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-2599.
Resolution: Fixed
I went ahead and committed my patch.
(one of the beauties of adding more
[
https://issues.apache.org/jira/browse/SOLR-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2599:
---
Summary: CloneFieldUpdateProcessor (copyField-equse equivilent) (was:
FieldCopy Update Processor)
[
https://issues.apache.org/jira/browse/SOLR-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-1751.
Resolution: Not A Problem
Fix Version/s: (was: 4.0)
looks like this was just a transient issue
[
https://issues.apache.org/jira/browse/SOLR-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1693:
---
Fix Version/s: (was: 4.0)
Issue Type: Improvement (was: Bug)
Removing fix version since this
[
https://issues.apache.org/jira/browse/SOLR-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-1288.
Resolution: Fixed
Fix Version/s: (was: 4.0)
no idea why this issue is still open.
all of the
[
https://issues.apache.org/jira/browse/SOLR-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-3406:
--
Assignee: Martijn van Groningen
Martijn: can you triage this for 4.0? commit if you think it's ready,
[
https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-2894:
--
Assignee: Erik Hatcher
Erik: Can you triage this for 4.0? commit if you think it's ready, otherwise
[
https://issues.apache.org/jira/browse/SOLR-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-1958:
--
Assignee: James Dyer
James: Could you please triage this for 4.0? commit if you think it's ready,
[
https://issues.apache.org/jira/browse/SOLR-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-735.
---
Resolution: Not A Problem
Fix Version/s: (was: 4.0)
I'm going to bite the bullet and resolve this
[
https://issues.apache.org/jira/browse/SOLR-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1542:
---
Fix Version/s: (was: 4.0)
Removing fix version since this issue hasn't gotten much attention and doesn't
[
https://issues.apache.org/jira/browse/SOLR-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-1014.
Resolution: Duplicate
Fix Version/s: (was: 4.0)
no activity for quite a long time, last update
[
https://issues.apache.org/jira/browse/SOLR-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-416:
--
Fix Version/s: (was: 4.0)
Removing fix version since this issue hasn't gotten much attention and doesn't
[
https://issues.apache.org/jira/browse/SOLR-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1557:
---
Fix Version/s: (was: 4.0)
Removing fix version since this issue hasn't gotten much attention and doesn't
[
https://issues.apache.org/jira/browse/SOLR-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1939:
---
Fix Version/s: (was: 4.0)
Removing fix version since this issue hasn't gotten much attention lately and
[
https://issues.apache.org/jira/browse/SOLR-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1785:
---
Fix Version/s: (was: 4.0)
Removing fix version since this issue hasn't gotten much attention lately and
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/68/
1 tests failed.
REGRESSION: org.apache.solr.spelling.suggest.SuggesterWFSTTest.testRebuild
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at
Mike,
On Wed, Jun 13, 2012 at 7:31 PM, Michael McCandless
luc...@mikemccandless.com wrote:
Hi Itamar,
One quick question: does Lucene.Net include the fixes done for
LUCENE-1044 (to fsync files on commit)? Those are very important for
an index to be intact after OS/JVM crash or power loss.
Christopher,
I used the IndexBuilder app from here
https://github.com/synhershko/Talks/tree/master/LuceneNeatThings with a
8.5GB wikipedia dump.
After running for 2.5 days I had to forcefully close it (infinite loop in
the wiki-markdown parser at 92%, go figure), and the 40-something GB index
I
[
https://issues.apache.org/jira/browse/SOLR-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294757#comment-13294757
]
Hoss Man commented on SOLR-2556:
when i read this issue, i assumed it was simply a matter
Yes, reproduced in first try. See attached program - I referenced it to
current trunk.
On Thu, Jun 14, 2012 at 3:54 AM, Itamar Syn-Hershko ita...@code972.comwrote:
Christopher,
I used the IndexBuilder app from here
https://github.com/synhershko/Talks/tree/master/LuceneNeatThings with a
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java7-64/59/
1 tests failed.
REGRESSION: org.apache.solr.search.TestSort.testRandomFieldNameSorts
Error Message:
Over 0.2% oddities in test: 14/6802 have func/query parsing semenatics gotten
broader?
Stack Trace:
[
https://issues.apache.org/jira/browse/SOLR-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2435:
---
Fix Version/s: (was: 4.0)
Summary: Duplicate Jars in (binary) release packages (was: Duplicate
1 - 100 of 112 matches
Mail list logo
