Build: https://hudson.apache.org/hudson/job/Solr-3.x/301/
No tests ran.
Build Log (for compile errors):
[...truncated 17991 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
Build: https://hudson.apache.org/hudson/job/Lucene-trunk/1504/
All tests passed
Build Log (for compile errors):
[...truncated 16607 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
(replying to the dev list, see context below)
: Unfortunately, you can't easily recover from this (except by
: reindexing your docs again).
:
: Failing to call IW.commit() or IW.close() means no segments file was
written...
I know there were good reasons for eliminating the "autoCommit"
func
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009522#comment-13009522
]
Adriano Crestani commented on LUCENE-1768:
--
I think this is also a good candidat
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Crestani updated LUCENE-1768:
-
Labels: contrib gsoc lucene-gsoc-11 (was: )
> NumericRange support for new query parser
[
https://issues.apache.org/jira/browse/SOLR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2396:
--
Attachment: SOLR-2396.patch
now that the lucene issues are resolved, I think this patch is really close.
[
https://issues.apache.org/jira/browse/SOLR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2396:
--
Description:
In LUCENE-2551 collation support was changed to use byte[] keys.
Previously it encoded sor
[
https://issues.apache.org/jira/browse/SOLR-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009504#comment-13009504
]
Robert Muir commented on SOLR-2387:
---
Tommaso, thanks again!
> UIMA tests are unstable
>
[
https://issues.apache.org/jira/browse/SOLR-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved SOLR-2387.
---
Resolution: Fixed
Fix Version/s: 4.0
Committed revision 1084045. (trunk)
Committed revision 108
[
https://issues.apache.org/jira/browse/SOLR-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-2437:
-
Attachment: SOLR-2437.patch
> Use IndexWriter.deleteAll() in DUH2.deleteAll() instead of closing
Use IndexWriter.deleteAll() in DUH2.deleteAll() instead of closing and
reopening writer w/ create=true
---
Key: SOLR-2437
URL: https://issues.apache.org/jira/brow
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6194/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6210/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6193/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6209/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
[
https://issues.apache.org/jira/browse/SOLR-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2061:
--
Attachment: SOLR-2061.patch
attached is a patch that makes a test-framework like lucene's.
The solr con
[
https://issues.apache.org/jira/browse/SOLR-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2061:
--
Fix Version/s: 4.0
3.2
> Generate jar containing test classes.
>
[
https://issues.apache.org/jira/browse/SOLR-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir reassigned SOLR-2061:
-
Assignee: Robert Muir
> Generate jar containing test classes.
> --
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6192/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6208/
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestIndexWriterMergePolicy.testMaxBufferedDocsChange
Error Message:
null
Stack Trace:
junit.framework.AssertionFailedError:
at
org.apache.lucene.util.Luc
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6191/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-3.x/321/
All tests passed
Build Log (for compile errors):
[...truncated 18976 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6207/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6190/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6206/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6189/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6205/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
[
https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009422#comment-13009422
]
Digy commented on LUCENENET-399:
There are only a few minor remaining issues for Lucene
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6188/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6204/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6187/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
[
https://issues.apache.org/jira/browse/LUCENENET-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009390#comment-13009390
]
Digy commented on LUCENENET-405:
No. I just forgot to commit :)
DIGY
> Port: contrib/A
That's a good point. There are a lot of scenarios where exceptions
could still occur, even with parameter validation.
The difference is, in some situations, MaxInt/2 is a valid value.
However, Int32.MaxValue is never a valid value due to the internal
sorting logic requiring an additional array slo
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6203/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
[
https://issues.apache.org/jira/browse/LUCENENET-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009375#comment-13009375
]
Prescott Nasser commented on LUCENENET-405:
---
Any objections to committing thi
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6186/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
[
https://issues.apache.org/jira/browse/LUCENE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe resolved LUCENE-2973.
-
Resolution: Fixed
bq. The subversion {{export}} command has a {{--native-eol}} parameter
S
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6202/
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestIndexWriterMergePolicy.testMaxBufferedDocsChange
Error Message:
null
Stack Trace:
junit.framework.AssertionFailedError:
at
org.apache.lucene.util.Luc
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6185/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExceptio
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6201/
2 tests failed.
FAILED:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExcept
[
https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009340#comment-13009340
]
Michael McCandless commented on LUCENE-2881:
OK beast chewed on this for a fe
Is -for ex- MaxInt/2 a valid value? You can get easily an OOM exception( and
the worst case would be getting sporadic OOM when search fequency increases).
DIGY
-Original Message-
From: Troy Howard [mailto:thowar...@gmail.com]
Sent: Monday, March 21, 2011 9:43 PM
To: lucene-net-...@luce
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6184/
2 tests failed.
REGRESSION:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeExce
Hi,
2011/3/21 soheila dehghanzadeh :
> Hi All,
> I have created Index folder, and i tried to open .CFS,.CFX,.GEN, segments
> file with notpad . but they are unreadable. i want to see their structure
> for my sample directory which i have passed to Indexfiles . ihave red this
> http://lucene.apache
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6200/
2 tests failed.
REGRESSION:
org.apache.solr.uima.processor.UIMAUpdateRequestProcessorTest.testProcessing
Error Message:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
Stack Trace:
java.lang.RuntimeEx
[
https://issues.apache.org/jira/browse/LUCENE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009321#comment-13009321
]
Doron Cohen commented on LUCENE-2978:
-
bq. Consolidate all of them in one place will
This is an expected behaviour. You get arithmetic overflow since an
array[MaxInt] is created in PriorityQueue to store the results.
(Lucene doesn't know the result-count before iterating over the results).
If you want to collect all results( say,not the top 10 or 100), you can use
HitCollector.
DI
[
https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009268#comment-13009268
]
Troy Howard commented on LUCENENET-391:
---
Amanuel: +1 Agreed
> Luke.Net for Lucen
[
https://issues.apache.org/jira/browse/LUCENE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009263#comment-13009263
]
Shai Erera commented on LUCENE-2978:
I remember seeing a compress-1.1 jar under Solr
[
https://issues.apache.org/jira/browse/LUCENE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe reopened LUCENE-2973:
-
The subversion {{export}} command has a {{--native-eol}} parameter:
{noformat}
--native-eol ARG
[
https://issues.apache.org/jira/browse/LUCENE-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009240#comment-13009240
]
Yonik Seeley commented on LUCENE-2894:
--
bq. Do you mean Solr javadocs see the pretti
Hi All,
I have created Index folder, and i tried to open .CFS,.CFX,.GEN, segments
file with notpad . but they are unreadable. i want to see their structure
for my sample directory which i have passed to Indexfiles . ihave red this
http://lucene.apache.org/java/3_0_3/fileformats.html and i know wha
I'm not sure how to report this or if this is working as intended, however
using the recommended Search overload of IndexSearcher and passing
Int32.MaxValue, results in an arithmetic overflow exception in
PriorityQueue.Initialize(int maxSize).
I tested this out on several platforms, including
[
https://issues.apache.org/jira/browse/LUCENE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-2978:
Attachment: LUCENE-2978.patch
Trivial patch for trunk.
> Upgrade benchmark from commons-compress-
Hi,
In 3x 'ant test' runs nicely from lucene/contrib/benchmark.
But not so in trunk/modules/benchmark, where it fails with this:
[javac]
D:\dev\lucene\LuceneTrunk\lucene\src\test\org\apache\lucene\index\TestIndexWriterOnDiskFull.java:467:
cannot find symbol
[javac] symbol : method
keepFullyDelet
[
https://issues.apache.org/jira/browse/LUCENE-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-2958.
-
Resolution: Fixed
Committed:
- r1083789 - 3x
- r1083812 - 3x undo added unused imports
- r108381
[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009173#comment-13009173
]
Uwe Schindler commented on LUCENE-2952:
---
Unfortunately as analyzers moved to module
2011/3/21 Shai Erera :
>> So the proper behaviour is to return false & IOE (on proper occasion)?
>
> I don't object to it, as I think it's reasonable (as today we may be hiding
> some info from the app). However, given that today we never throw IOE, and
> that if we start doing so, we'll change run
[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009169#comment-13009169
]
Grant Ingersoll commented on LUCENE-2952:
-
Third time is the charm. I don't real
[
https://issues.apache.org/jira/browse/LUCENE-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-2979:
-
Fix Version/s: (was: 3.1)
3.2
moving out of 3.1 - this is not a release b
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009163#comment-13009163
]
Mark Harwood commented on LUCENE-2454:
--
Lucene does not dictate a schema and so usin
2011/3/21 Shai Erera :
>> So the proper behaviour is to return false & IOE (on proper occasion)?
>
> I don't object to it, as I think it's reasonable (as today we may be hiding
> some info from the app). However, given that today we never throw IOE, and
> that if we start doing so, we'll change run
> So the proper behaviour is to return false & IOE (on proper occasion)?
I don't object to it, as I think it's reasonable (as today we may be hiding
some info from the app). However, given that today we never throw IOE, and
that if we start doing so, we'll change runtime behavior, I lean towards
k
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009141#comment-13009141
]
Jamal Natour commented on LUCENE-2454:
--
Mark,
For my project this is a must have fe
2011/3/21 Earwin Burrfoot :
> Technically, there's a big difference between "I checked, and there
> was no index", and "I was unable to check the disk because file system
> went BANG!".
> So the proper behaviour is to return false & IOE (on proper occasion)?
+1 to throw the exception when proper t
Technically, there's a big difference between "I checked, and there
was no index", and "I was unable to check the disk because file system
went BANG!".
So the proper behaviour is to return false & IOE (on proper occasion)?
On Mon, Mar 21, 2011 at 13:53, Michael McCandless
wrote:
> On Mon, Mar 21,
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6189/
No tests ran.
Build Log (for compile errors):
[...truncated 49 lines...]
clean:
clean:
[delete] Deleting directory
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only-trunk/checkout/lucene/build
clean
[
https://issues.apache.org/jira/browse/LUCENE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-2944.
-
Resolution: Fixed
Committed revision 1083784.
> BytesRef reuse bugs in QueryParser and analysis
[
https://issues.apache.org/jira/browse/LUCENE-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-2958:
Attachment: LUCENE-2958.patch
Hmmm, while reviewing again before committing I noticed that the
He
[
https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2881:
Attachment: LUCENE-2881.patch
next iteration, I think we are ready to commit here. I added
[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-2952:
---
The nightly builds now fail because clover breaks because the checker classes
are in test-frame
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009111#comment-13009111
]
Mark Harwood commented on LUCENE-2454:
--
bq. Mark, do you have any plans for includin
[
https://issues.apache.org/jira/browse/LUCENE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-2964.
-
Resolution: Fixed
Committed:
- r1083726 - 3x
- r1083731 - trunk
(Hudson's Lucene-Solr-tests-onl
Hi.
i have a problem with logic operator OR in dismax query search.
some days ago the query worked well. now it returns me anything (0
documents)
i explain:
the query is:
http://localhost:8983/solr/select/?q=
"1324"OR"4322"OR"2324"OR%20hello+world&defType=dismax&qf=code%20title
the schema has th
On Mon, Mar 21, 2011 at 12:52 AM, Shai Erera wrote:
> Can we remove the declaration? The method never throws IOE, but instead
> catches it and returns false. I think it's reasonable that such a method
> will not throw exceptions.
+1
--
Mike
http://blog.mikemccandless.com
-
Oh, in this case I also welcome RynekMedyczny.pl as a Solr user ;)
Dawid
P.S. RynekMedyczny ~= HealthCareMarket
On Mon, Mar 21, 2011 at 11:07 AM, Andrzej Bialecki wrote:
> On 3/21/11 10:51 AM, Dawid Weiss wrote:
>>
>> Is it just me, or was that last e-mail sent with the header:
>>
>> From: "Ryn
On 3/21/11 10:51 AM, Dawid Weiss wrote:
Is it just me, or was that last e-mail sent with the header:
From: "RynekMedyczny.pl (JIRA)"
JIRA comment notifications put username in front of JIRA's own address.
Apparently someone uses RynekMedyczny.pl as their username.
This is weird :)
I, fo
[
https://issues.apache.org/jira/browse/LUCENE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009080#comment-13009080
]
Shai Erera commented on LUCENE-2964:
bq. So, I rather keep the additional class file
Is it just me, or was that last e-mail sent with the header:
From: "RynekMedyczny.pl (JIRA)"
This is weird :)
Dawid
On Mon, Mar 21, 2011 at 10:35 AM, RynekMedyczny.pl (JIRA)
wrote:
>
> [
> https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanel
[
https://issues.apache.org/jira/browse/LUCENE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-2964:
Attachment: LUCENE-2964.patch
Updated patch, fixing per Shai suggestion on the exception.
Plannin
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009071#comment-13009071
]
RynekMedyczny.pl commented on LUCENE-2454:
--
Mark, do you have any plans for incl
[
https://issues.apache.org/jira/browse/LUCENE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009062#comment-13009062
]
Doron Cohen commented on LUCENE-2964:
-
Apparently using '$' is safe in that it is alw
[
https://issues.apache.org/jira/browse/LUCENE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009060#comment-13009060
]
Doron Cohen commented on LUCENE-2964:
-
Thanks for reviewing.
bq. The CNFE message th
[
https://issues.apache.org/jira/browse/LUCENE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-2978:
Description:
In LUCENE-1540 TrecContentSource moved from Java's GZipInputStream to
common-compres
Build: https://hudson.apache.org/hudson/job/Solr-trunk/1449/
No tests ran.
Build Log (for compile errors):
[...truncated 19027 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-ma
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6179/
1 tests failed.
REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration
Error Message:
expected:<2> but was:<3>
Stack Trace:
junit.framework.AssertionFailedError: expected:<2> but was:<3>
86 matches
Mail list logo
