[jira] Commented: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

[ https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999884#comment-12999884 ] Mark Miller commented on LUCENE-2939: - Fair enough (this setting is well before my ti

[jira] Commented: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

[ https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999883#comment-12999883 ] Robert Muir commented on LUCENE-2939: - Maybe the setting is already there, but I thin

[jira] Commented: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

[ https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999882#comment-12999882 ] Mark Miller commented on LUCENE-2939: - Because this is already a setting on the Highl

[jira] Commented: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

[ https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999880#comment-12999880 ] Robert Muir commented on LUCENE-2939: - i don't know why you get this null pointer exc

[jira] Commented: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

[ https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999866#comment-12999866 ] Mark Miller commented on LUCENE-2939: - only seems to happen when maxDocCharsToAnalyze

[jira] Commented: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

[ https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999863#comment-12999863 ] Mark Miller commented on LUCENE-2939: - hmmm...didn't quite get it right yet I think..

[jira] Updated: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

[ https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated LUCENE-2939: Attachment: LUCENE-2939.patch I'm a little rusty on the new tokenstream api, but here is a little

[jira] Created: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex

Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex --- Key: LUCENE-2939 URL: h

[jira] Updated: (SOLR-2385) Backport latest /browse improvements to branch_3x

[ https://issues.apache.org/jira/browse/SOLR-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-2385: -- Attachment: SOLR-2385.patch This new patch is in svn format. I think this makes a really good improveme

[jira] Updated: (SOLR-2385) Backport latest /browse improvements to branch_3x

[ https://issues.apache.org/jira/browse/SOLR-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-2385: -- Affects Version/s: 3.1 > Backport latest /browse improvements to branch_3x > ---

[jira] Updated: (SOLR-2387) UIMA tests are unstable

[ https://issues.apache.org/jira/browse/SOLR-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SOLR-2387: -- Attachment: SOLR2387.patch Hello Robert, this is due to an issue on the alchemy remote service f

[HUDSON] Lucene-Solr-tests-only-3.x - Build # 5347 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/5347/ 1 tests failed. FAILED: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExceptio

[jira] Updated: (SOLR-1656) XInclude's are resolved relative CWD, not instance dir

[ https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-1656: Attachment: (was: SOLR-1656.patch) > XInclude's are resolved relative CWD, not instance dir > --

[jira] Updated: (SOLR-1656) XInclude's are resolved relative CWD, not instance dir

[ https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-1656: Attachment: SOLR-1656.patch > XInclude's are resolved relative CWD, not instance dir > -

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 5360 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/5360/ 1 tests failed. FAILED: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExcept

[HUDSON] Lucene-Solr-tests-only-3.x - Build # 5346 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/5346/ 1 tests failed. REGRESSION: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExce

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 5359 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/5359/ 1 tests failed. FAILED: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExcept

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

Well, after LUCENE-2881 assigning the same fieldNumber to the same fieldName across segments is best effort - not guaranteed anymore. It looks like in most cases it works fine, just very rarely we get different field numbers. I don't see how we can improve the best effort, because I don't thi

[jira] Commented: (LUCENE-2881) Track FieldInfo per segment instead of per-IW-session

[ https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999848#comment-12999848 ] Michael Busch commented on LUCENE-2881: --- bq. One question: we seem to have lost Doc

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 5358 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/5358/ 1 tests failed. FAILED: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExcept

[jira] Created: (SOLR-2387) UIMA tests are unstable

UIMA tests are unstable --- Key: SOLR-2387 URL: https://issues.apache.org/jira/browse/SOLR-2387 Project: Solr Issue Type: Bug Reporter: Robert Muir Fix For: 3.1 The UIMA tests fail frequently in

[HUDSON] Lucene-Solr-tests-only-3.x - Build # 5344 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/5344/ 1 tests failed. FAILED: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExceptio

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 5357 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/5357/ 1 tests failed. FAILED: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExcept

Index File Format Change - heads up (late)

hey there, a couple of days ago the trunk index format changed with LUCENE-2881 you should re-index any trunk indexes. its likely if you open up old trunk indexes, you will get an exception related to Read Past EOF. Sorry for the delay! simon ---

[jira] Updated: (SOLR-1656) XInclude's are resolved relative CWD, not instance dir

[ https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-1656: Attachment: (was: SOLR-1656.patch) > XInclude's are resolved relative CWD, not instance dir > --

[jira] Updated: (SOLR-1656) XInclude's are resolved relative CWD, not instance dir

[ https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-1656: Attachment: SOLR-1656.patch Sorry, last patch was outdated. > XInclude's are resolved relative CWD,

[jira] Updated: (SOLR-1656) XInclude's are resolved relative CWD, not instance dir

[ https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-1656: Attachment: SOLR-1656.patch Here is a new patch, redesigned: - The resolver was moved into a util c

[jira] Updated: (SOLR-1656) XInclude's are resolved relative CWD, not instance dir

[ https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-1656: Fix Version/s: 4.0 3.1 > XInclude's are resolved relative CWD, not instance dir >

[jira] Assigned: (SOLR-1656) XInclude's are resolved relative CWD, not instance dir

[ https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler reassigned SOLR-1656: --- Assignee: Uwe Schindler > XInclude's are resolved relative CWD, not instance dir > ---

[jira] Updated: (SOLR-2386) Filter Query Cache Improvement

[ https://issues.apache.org/jira/browse/SOLR-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Kraus updated SOLR-2386: - Description: Currently logically identical filter queries are not reduced to one query, but

[jira] Created: (SOLR-2386) Filter Query Cache Improvement

Filter Query Cache Improvement -- Key: SOLR-2386 URL: https://issues.apache.org/jira/browse/SOLR-2386 Project: Solr Issue Type: Improvement Affects Versions: 1.4.1, 3.1, 4.0 Reporter: Frederik Krau

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

WTF - you got that running that test with while(true)? hmm... weird. Not sure if it is related to 2881 though On Sat, Feb 26, 2011 at 6:30 PM, Michael McCandless wrote: > Hmmm beast hit a failure, but, a different one from the build: > > *** Thread: Lucene Merge Thread #1 *** > org.apache.lucene

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 5355 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/5355/ 1 tests failed. FAILED: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExcept

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 5354 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/5354/ 1 tests failed. REGRESSION: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeEx

[jira] Commented: (SOLR-1223) Query Filter fq with OR operator

[ https://issues.apache.org/jira/browse/SOLR-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999820#comment-12999820 ] Frederik Kraus commented on SOLR-1223: -- I'd rather see a new filterQuery type like ofq

[jira] Updated: (SOLR-2385) Backport latest /browse improvements to branch_3x

[ https://issues.apache.org/jira/browse/SOLR-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-2385: -- Attachment: SOLR-2385.patch Attaching a working patch which is upgrading conf/velocity to equal as 4.0 w

[HUDSON] Lucene-Solr-tests-only-3.x - Build # 5340 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/5340/ 1 tests failed. REGRESSION: org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing Error Message: org.apache.uima.analysis_engine.AnalysisEngineProcessException Stack Trace: java.lang.RuntimeExce

[jira] Created: (SOLR-2385) Backport latest /browse improvements to branch_3x

Backport latest /browse improvements to branch_3x - Key: SOLR-2385 URL: https://issues.apache.org/jira/browse/SOLR-2385 Project: Solr Issue Type: Improvement Components: Response Writ

[jira] Updated: (SOLR-2383) Velocity: Generalize range and date facet display

[ https://issues.apache.org/jira/browse/SOLR-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-2383: -- Description: Velocity (/browse) GUI has hardcoded price range facet and a hardcoded manufacturedate_dt d

[jira] Updated: (SOLR-2383) Velocity: Generalize range facet display

[ https://issues.apache.org/jira/browse/SOLR-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-2383: -- Attachment: SOLR-2383.patch This last patch adds the following: * Same generic treatment of facet.dates

[jira] Commented: (SOLR-1942) Ability to select codec per field

[ https://issues.apache.org/jira/browse/SOLR-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999811#comment-12999811 ] Yonik Seeley commented on SOLR-1942: Finally got around to reviewing this again - looks

[jira] Commented: (LUCENE-2881) Track FieldInfo per segment instead of per-IW-session

[ https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999809#comment-12999809 ] Michael McCandless commented on LUCENE-2881: One question: we seem to have lo

[jira] Commented: (LUCENE-2932) clean up obselete information on the website

[ https://issues.apache.org/jira/browse/LUCENE-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999808#comment-12999808 ] Michael McCandless commented on LUCENE-2932: Patch looks good! > clean up ob

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

On Sat, Feb 26, 2011 at 12:30 PM, Michael McCandless wrote: > Hmmm beast hit a failure, but, a different one from the build: Maybe we should back this change out, until it can be stabilized on an issue? I don't like an unstable trunk. -

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

Hmmm beast hit a failure, but, a different one from the build: *** Thread: Lucene Merge Thread #1 *** org.apache.lucene.index.MergePolicy$MergeException: java.lang.NullPointerException at org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:5

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

Alas no I cannot repro so far :( I tried the seed that failed, and I'm running while(1) on beast but no failure so far gonna be a tricky one!! Mike On Sat, Feb 26, 2011 at 8:43 AM, Simon Willnauer wrote: > I am running this now for a while with no failure :( > > mike can your reproduce? > >

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

On Sat, Feb 26, 2011 at 8:43 AM, Simon Willnauer wrote: > I am running this now for a while with no failure :( I haven't been able to reproduce this either. -Yonik http://lucidimagination.com - To unsubscribe, e-mail: dev-unsub

[jira] Commented: (SOLR-2379) Improve documentation of Analyzers and Tokenizers

[ https://issues.apache.org/jira/browse/SOLR-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999803#comment-12999803 ] Yonik Seeley commented on SOLR-2379: Re-reading the link, I think you're right - it's o

[jira] Commented: (SOLR-2379) Improve documentation of Analyzers and Tokenizers

[ https://issues.apache.org/jira/browse/SOLR-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999801#comment-12999801 ] Mark Miller commented on SOLR-2379: --- That almost looks like it could be going away for pr

[jira] Commented: (SOLR-2379) Improve documentation of Analyzers and Tokenizers

[ https://issues.apache.org/jira/browse/SOLR-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999800#comment-12999800 ] Yonik Seeley commented on SOLR-2379: bq. ASIDE: And what about finally making the move

[jira] Updated: (SOLR-2375) Store & Load functionality for Suggester Lookup implementations

[ https://issues.apache.org/jira/browse/SOLR-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-2375: -- Attachment: SOLR-2375.patch Couple small changes: close DataOutputStream and DataInputStream in Jaspell

[jira] Updated: (SOLR-2375) Store & Load functionality for Suggester Lookup implementations

[ https://issues.apache.org/jira/browse/SOLR-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-2375: -- Affects Version/s: (was: 3.2) (was: 4.0) Fix Version/s: 4.0

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

I am running this now for a while with no failure :( mike can your reproduce? On Sat, Feb 26, 2011 at 2:30 PM, Michael McCandless wrote: > Uh-oh!  I suspect this failure is from LUCENE-2881 -- the assert that > tripped was verifying all merges were done w/ bulk copy.  So, somehow, > in this test

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

Uh-oh! I suspect this failure is from LUCENE-2881 -- the assert that tripped was verifying all merges were done w/ bulk copy. So, somehow, in this test we are failing to consistently assign the same field number to the same field name... Mike On Sat, Feb 26, 2011 at 4:46 AM, Apache Hudson Serve

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 5336 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/5336/ 1 tests failed. REGRESSION: org.apache.lucene.index.TestNRTThreads.testNRTThreads Error Message: null Stack Trace: junit.framework.AssertionFailedError: at org.apache.lucene.util.LuceneTestCase$LuceneTestCa

[jira] Commented: (SOLR-2379) Improve documentation of Analyzers and Tokenizers

[ https://issues.apache.org/jira/browse/SOLR-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999744#comment-12999744 ] Dawid Weiss commented on SOLR-2379: --- I realize such things are a revolutionary refactorin