Simplify configuration API of contrib Query Parser
--
Key: LUCENE-2979
URL: https://issues.apache.org/jira/browse/LUCENE-2979
Project: Lucene - Java
Issue Type: Improvement
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
at
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,
[
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
[
https://issues.apache.org/jira/browse/LUCENE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009060#comment-13009060
]
Doron Cohen commented on LUCENE-2964:
-
Thanks for reviewing.
bq. The CNFE message
[
https://issues.apache.org/jira/browse/LUCENE-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009062#comment-13009062
]
Doron Cohen commented on LUCENE-2964:
-
Apparently using '$' is safe in that it is
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009071#comment-13009071
]
RynekMedyczny.pl commented on LUCENE-2454:
--
Mark, do you have any plans for
[
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.
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)j...@apache.org
JIRA comment notifications put username in front of JIRA's own address.
Apparently someone uses RynekMedyczny.pl as their username.
This is
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 a...@getopt.org 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:
[
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
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009111#comment-13009111
]
Mark Harwood commented on LUCENE-2454:
--
bq. Mark, do you have any plans for
[
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
[
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
[
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
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
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
luc...@mikemccandless.com
2011/3/21 Earwin Burrfoot ear...@gmail.com:
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
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009141#comment-13009141
]
Jamal Natour commented on LUCENE-2454:
--
Mark,
For my project this is a must have
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
2011/3/21 Shai Erera ser...@gmail.com:
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
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009163#comment-13009163
]
Mark Harwood commented on LUCENE-2454:
--
Lucene does not dictate a schema and so
[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009169#comment-13009169
]
Grant Ingersoll commented on LUCENE-2952:
-
Third time is the charm. I don't
2011/3/21 Shai Erera ser...@gmail.com:
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
[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009173#comment-13009173
]
Uwe Schindler commented on LUCENE-2952:
---
Unfortunately as analyzers moved to
[
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
-
[
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
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
[
https://issues.apache.org/jira/browse/LUCENE-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009240#comment-13009240
]
Yonik Seeley commented on LUCENE-2894:
--
bq. Do you mean Solr javadocs see the
[
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-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009268#comment-13009268
]
Troy Howard commented on LUCENENET-391:
---
Amanuel: +1 Agreed
Luke.Net for
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.
[
https://issues.apache.org/jira/browse/LUCENE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009321#comment-13009321
]
Doron Cohen commented on LUCENE-2978:
-
bq. Consolidate all of them in one place will
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:
Hi,
2011/3/21 soheila dehghanzadeh sally...@gmail.com:
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
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:
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:
[
https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009340#comment-13009340
]
Michael McCandless commented on LUCENE-2881:
OK beast chewed on this for a
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:
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:
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
[
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
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:
[
https://issues.apache.org/jira/browse/LUCENENET-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009375#comment-13009375
]
Prescott Nasser commented on LUCENENET-405:
---
Any objections to committing
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:
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
[
https://issues.apache.org/jira/browse/LUCENENET-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009390#comment-13009390
]
Digy commented on LUCENENET-405:
No. I just forgot to commit :)
DIGY
Port:
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:
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:
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:
[
https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009422#comment-13009422
]
Digy commented on LUCENENET-399:
There are only a few minor remaining issues for
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:
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:
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:
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:
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:
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,
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:
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
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:
[
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.
[
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 updated SOLR-2061:
--
Attachment: SOLR-2061.patch
attached is a patch that makes a test-framework like lucene's.
The solr
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:
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:
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:
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:
Use IndexWriter.deleteAll() in DUH2.deleteAll() instead of closing and
reopening writer w/ create=true
---
Key: SOLR-2437
URL:
[
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
[
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
[
https://issues.apache.org/jira/browse/SOLR-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009504#comment-13009504
]
Robert Muir commented on SOLR-2387:
---
Tommaso, thanks again!
UIMA tests are unstable
[
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
[
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
[
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/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009522#comment-13009522
]
Adriano Crestani commented on LUCENE-1768:
--
I think this is also a good
(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
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
[
https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009224#comment-13009224
]
Amanuel Workneh commented on LUCENENET-391:
---
The bitbucket version is a WPF
While I understand that and thank you for taking the time to respond, my
concern was that passing a perfectly valid parameter leads to an
exception. So this is bad design.
Regards,
Steve Hoff
From: Digy digyd...@gmail.com
To: lucene-net-dev@lucene.apache.org
Date: 03/21/2011 01:53
No, I don't think it is a bad design. It could be limited to some number,
but what would it be? 10,100,1000,100 or 1?
Besides that you have other alternatives to use while searching.
DIGY.
-Original Message-
From: steven.h...@pattersoncompanies.com
I agree that it should not throw an overflow exception. That's not
very helpful for debugging.
The valid range of that parameter is essentially [0...
Int32.MaxValue-1].. That's because it needs one extra slot in it's
internal array, beyond the max size for juggling values during sort.
The
[
https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009436#comment-13009436
]
Digy commented on LUCENENET-399:
There are two public fields in TopDocs, totalHits and
83 matches
Mail list logo
