Potential IndexReader leak in SearcherManager and NRTManager
Key: LUCENE-3798
URL: https://issues.apache.org/jira/browse/LUCENE-3798
Project: Lucene - Java
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-3096.
Resolution: Fixed
Published; closed issue.
> Add book information to the new websit
[
https://issues.apache.org/jira/browse/SOLR-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley closed SOLR-3096.
--
> Add book information to the new website
> ---
>
>
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12443/
All tests passed
Build Log (for compile errors):
[...truncated 15407 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210814#comment-13210814
]
Bill Bell commented on LUCENE-3795:
---
+1 getting polygon support ootb is huge as is geoh
In trunk, org.apache.solr.handler.extraction.ExtractingDocumentLoader.java.
Is this thread-safe from somewhere else? If so, please describe why or
remove the comment.
/**
* this must be MT safe... may be called concurrently from multiple threads.
*
* @param
* @param
*/
void doA
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1749/
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
shard2 is not consistent, expected:16 and got:18
Stack Trace:
junit.framework.AssertionFailedError: shard2 is no
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x-java7/1778/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.LargeVolumeJettyTest.testMultiThreaded
Error Message:
expected:<500> but was:<400>
Stack Trace:
junit.framework.AssertionFailedError: expected:<500> but
[
https://issues.apache.org/jira/browse/SOLR-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210748#comment-13210748
]
Adam Lane commented on SOLR-2907:
-
FYI: Found an alternate way of doing delta here in this
[
https://issues.apache.org/jira/browse/SOLR-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-3125.
---
Resolution: Fixed
This is good for now - works - any improvement can go to another issue.
[
https://issues.apache.org/jira/browse/SOLR-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-3122.
---
Resolution: Fixed
> RecoveryStrat can not use interrupt due to the use of Channels.
>
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1748/
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
shard5 is not consistent, expected:38 and got:40
Stack Trace:
junit.framework.AssertionFailedError: shard5 is no
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12441/
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
shard5 is not consistent, expected:27 and got:28
Stack Trace:
junit.framework.AssertionFailedError: shard5 is not con
[
https://issues.apache.org/jira/browse/LUCENE-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3797:
Attachment: LUCENE-3797.patch
yet another patch. not sure if this is really the way to go
[
https://issues.apache.org/jira/browse/LUCENE-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210622#comment-13210622
]
Simon Willnauer commented on LUCENE-3797:
-
scratch that I the tests actually fail
thanks david for the hard work this is awesome!
simon
On Fri, Feb 17, 2012 at 11:16 PM, Tommaso Teofili wrote:
> Nice improvements! +1
> Tommaso
>
>
> 2012/2/17 Dawid Weiss
>
>> Hi everyone,
>>
>> as part of this:
>> https://issues.apache.org/jira/browse/LUCENE-3785
>>
>> I've been working
[
https://issues.apache.org/jira/browse/LUCENE-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3797:
Attachment: LUCENE-3797.patch
here is a simple patch
> 3xCodec should thr
3xCodec should throw UOE if a DocValuesConsumer is pulled
--
Key: LUCENE-3797
URL: https://issues.apache.org/jira/browse/LUCENE-3797
Project: Lucene - Java
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-3797:
---
Assignee: Simon Willnauer
> 3xCodec should throw UOE if a DocValuesConsumer is p
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1747/
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
shard2 is not consistent, expected:53 and got:55
Stack Trace:
junit.framework.AssertionFailedError: shard2 is no
Nice improvements! +1
Tommaso
2012/2/17 Dawid Weiss
> Hi everyone,
>
> as part of this:
> https://issues.apache.org/jira/browse/LUCENE-3785
>
> I've been working on moving away from ant-macros to a custom ANT task;
> potential benefits are mentioned as part of the issue's description.
>
> There
I've got one last piece to https://issues.apache.org/jira/browse/SOLR-3126 that
I'm working on that might address this.
On Feb 17, 2012, at 4:35 PM, Apache Jenkins Server wrote:
> Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12440/
>
> 1 tests failed.
> REGRESSION: org.apa
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12440/
1 tests failed.
REGRESSION: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
shard1 is not consistent, expected:116 and got:112
Stack Trace:
junit.framework.AssertionFailedError: shard1 is n
[
https://issues.apache.org/jira/browse/SOLR-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210538#comment-13210538
]
Greg Fodor commented on SOLR-2202:
--
Any updates on this?
> Money FieldTy
Nice work! I also like the ant test-help target (I also forget the
test options quite often).
Are all options going to be specified in there? I don't see the
tests.iter option.
Martijn
On 17 February 2012 20:17, Mark Miller wrote:
> Sweet.
>
>
> On Fri, Feb 17, 2012 at 12:56 PM, Dawid Weiss
> w
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1746/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestReaderClosed.test
Error Message:
null
Stack Trace:
java.lang.NullPointerException
at org.apache.lucene.util.fst.FSTEnum.(FSTEnum.java:48)
at
org
Build: https://builds.apache.org/job/Solr-trunk/1765/
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
shard2 is not consistent, expected:48 and got:31
Stack Trace:
junit.framework.AssertionFailedError: shard2 is not consistent, expected:4
[
https://issues.apache.org/jira/browse/LUCENE-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-3776.
Resolution: Fixed
Thanks Shai!
> NRTManager shouldn't expose its
Sweet.
On Fri, Feb 17, 2012 at 12:56 PM, Dawid Weiss
wrote:
> Hi everyone,
>
> as part of this:
> https://issues.apache.org/jira/browse/LUCENE-3785
>
> I've been working on moving away from ant-macros to a custom ANT task;
> potential benefits are mentioned as part of the issue's description.
>
>
On Fri, Feb 17, 2012 at 1:19 PM, Jan Høydahl wrote:
> If omitNorms is default for all numeric field types
That's only true for Lucene, not Solr currently.
> , could we simplify Solr's example schema and perhaps document the defaults
> in a comment?
They may make sense to simplify the schema, b
Build: https://builds.apache.org/job/Lucene-trunk/1831/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestReaderClosed.test
Error Message:
Abusing closed IndexInput!
Stack Trace:
java.lang.RuntimeException: Abusing closed IndexInput!
at
org.apache.lucene.store.MockIndexInputWrapp
If omitNorms is default for all numeric field types, could we simplify Solr's
example schema and perhaps document the defaults in a comment?
--
Jan Høydahl
Den 17. feb. 2012 kl. 17:16 skrev Yonik Seeley :
> On Fri, Feb 17, 2012 at 11:04 AM, Uwe Schindler wrote:
>> We dont prohibit anything. If
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210418#comment-13210418
]
Dawid Weiss commented on LUCENE-3774:
-
No worries, I'm glad you're double checking af
Hi everyone,
as part of this:
https://issues.apache.org/jira/browse/LUCENE-3785
I've been working on moving away from ant-macros to a custom ANT task;
potential benefits are mentioned as part of the issue's description.
There is a lot of code I already pruned from LuceneTestCase as part of
this
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210415#comment-13210415
]
Steven Rowe commented on LUCENE-3774:
-
Crap, my last comment is wrong too: {{trunk/mo
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210412#comment-13210412
]
Steven Rowe commented on LUCENE-3774:
-
bq. It needs to be in a separate file because
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210406#comment-13210406
]
Steven Rowe commented on LUCENE-3774:
-
Aha - sorry for the noise - I was restricting
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210402#comment-13210402
]
Dawid Weiss commented on LUCENE-3774:
-
It's under lucene/tools/custom-tasks.xml? It n
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210400#comment-13210400
]
Dawid Weiss commented on LUCENE-3774:
-
Mhmm... this would be weird, wouldn't it? I'll
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210399#comment-13210399
]
Dawid Weiss commented on LUCENE-3774:
-
Mhmm... this would be weird, wouldn't it? I'll
[
https://issues.apache.org/jira/browse/LUCENE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210392#comment-13210392
]
Steven Rowe commented on LUCENE-3774:
-
Hi Dawid,
I noticed that on branch_3x, there
Fix committed in r1245661. - Steve
> -Original Message-
> From: Steven A Rowe [mailto:sar...@syr.edu]
> Sent: Friday, February 17, 2012 11:20 AM
> To: dev@lucene.apache.org
> Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-3.x #394: POMs out of sync
>
> Thanks Robert, I'll look into adding
[
https://issues.apache.org/jira/browse/LUCENE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210381#comment-13210381
]
Mark Miller commented on LUCENE-3750:
-
bq. unless you use --offline mode locally, in
On Thu, Feb 9, 2012 at 3:48 PM, Grant Ingersoll wrote:
> I could see that we move "official docs" to the CMS and leave the wiki for
> new things, etc. and for user generated recipes, etc.
OK, so how about this for Solr documentation on the website:
pseudo-versioned live docs.
The docs for 4x liv
On Fri, Feb 17, 2012 at 11:53 AM, Uwe Schindler wrote:
>
> In my opinion, per document boosts should maybe removed in trunk and people
> should be instructed to use DocValues and CustomScoreQuery.
>
This is already the case since last summer: boosts are only per-field
in trunk (there is no concep
Yeah. I was not sure if you was referring to Robert's patch where we throw
ex when boost!=1.0f and norms omitted.
In general, boosting documents (not fields) was never really supported by
Lucene, it was always just a "norms hack". And it only works when TermQuery
is involved. If you really want to
[
https://issues.apache.org/jira/browse/LUCENE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210360#comment-13210360
]
Grant Ingersoll commented on LUCENE-3750:
-
I hear you on the commit approach, jus
Thanks Robert, I'll look into adding this to the Maven configuration. - Steve
> -Original Message-
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Friday, February 17, 2012 11:06 AM
> To: dev@lucene.apache.org
> Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-3.x #394: POMs out of syn
On Fri, Feb 17, 2012 at 11:04 AM, Uwe Schindler wrote:
> We dont prohibit anything. If the field type/field has norms omitted (which
> is the default for those fields), applying a boost will never work. That's
> all.
That's a fine default, but your answer to Jan suggested that boosts
*never* wor
This one needs a classpath addition, the 'conf/' directory.
Its a challenge sorta like testing the solr example, the way we did
this is to copy conf/ as if its in the test classpath (just like test
resources get copied).
Here was the addition to the ant build.xml as an example:
Hi Yonik,
We dont prohibit anything. If the field type/field has norms omitted (which
is the default for those fields), applying a boost will never work. That's
all.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Messa
[
https://issues.apache.org/jira/browse/LUCENE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210347#comment-13210347
]
Mark Miller commented on LUCENE-3750:
-
bq. FWIW, you can all just commit and then loo
Build: https://builds.apache.org/job/Lucene-Solr-Maven-3.x/394/
1 tests failed.
FAILED: org.apache.lucene.benchmark.byTask.TestPerfTasksParse.testParseExamples
Error Message:
could not find any .alg files!
Stack Trace:
java.lang.AssertionError: could not find any .alg files!
at org.juni
On Fri, Feb 17, 2012 at 5:50 AM, Uwe Schindler wrote:
> Index time boost is not applied, because e.g. NumericRangeQuery is a
> ConstantScoreQuery.
Someone could add boosts to these fields and use term queries though.
I've seen it done in the past, and there's not a good reason to
prohibit that.
[
https://issues.apache.org/jira/browse/LUCENE-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210342#comment-13210342
]
Uwe Schindler commented on LUCENE-3796:
---
+1, heavy committing!
> D
[
https://issues.apache.org/jira/browse/LUCENE-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210340#comment-13210340
]
Michael McCandless commented on LUCENE-3796:
+1
> Disallow s
[
https://issues.apache.org/jira/browse/LUCENE-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210337#comment-13210337
]
Michael McCandless commented on LUCENE-3776:
Thanks Shai -- I'll share a comm
[
https://issues.apache.org/jira/browse/LUCENE-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3796:
Attachment: LUCENE-3796.patch
updated patch: also fixing tests, and making the exception clearer (
[
https://issues.apache.org/jira/browse/LUCENE-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210327#comment-13210327
]
Shai Erera commented on LUCENE-3776:
Looks good Mike.
Do we still need that assert,
[
https://issues.apache.org/jira/browse/LUCENE-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210328#comment-13210328
]
Fis Ka commented on LUCENE-3220:
Hi All,
pardon my ignorance, I'm new to this. What I ne
[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210325#comment-13210325
]
David Smiley commented on LUCENE-3795:
--
Uwe,
Thanks for bringing java.awt.geom.Area
[
https://issues.apache.org/jira/browse/LUCENE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210320#comment-13210320
]
Uwe Schindler commented on LUCENE-3736:
---
Committed trunk revision: 1245605
[
https://issues.apache.org/jira/browse/LUCENE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210319#comment-13210319
]
Grant Ingersoll commented on LUCENE-3750:
-
Also, I would suggest reporting your e
[
https://issues.apache.org/jira/browse/LUCENE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3736:
--
Attachment: LUCENE-3736-improveTestCoverage.patch
Here is a patch that improves test coverage
[
https://issues.apache.org/jira/browse/LUCENE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210318#comment-13210318
]
Grant Ingersoll commented on LUCENE-3750:
-
FWIW, you can all just commit and then
[
https://issues.apache.org/jira/browse/LUCENE-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210299#comment-13210299
]
Michael McCandless commented on LUCENE-3777:
Thanks Robert, I committed first
[
https://issues.apache.org/jira/browse/LUCENE-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210293#comment-13210293
]
Robert Muir commented on LUCENE-3777:
-
Thanks Mike, such patches go out of date quick
[
https://issues.apache.org/jira/browse/SOLR-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210289#comment-13210289
]
Steven Rowe commented on SOLR-3096:
---
+1
> Add book information to the ne
[
https://issues.apache.org/jira/browse/SOLR-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210282#comment-13210282
]
Mark Miller commented on SOLR-3096:
---
+1, looks fine to me.
> Add book in
[
https://issues.apache.org/jira/browse/LUCENE-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3776:
---
Attachment: LUCENE-3776.patch
OK, I made the evil SearcherFactory a real check; it's
[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210263#comment-13210263
]
Michael McCandless commented on LUCENE-3795:
+1, Lucene badly needs good ootb
So can we always omit norms for these types and remove the (then) unnecessary
omitNorms="true" in Solr's schema?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
On 17. feb. 2012, at 11:50, Uwe Schindler wrote:
> Index time boost is
Index time boost is not applied, because e.g. NumericRangeQuery is a
ConstantScoreQuery.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Jan Høydahl [mailto:jan@cominvent.com]
> Sent: Friday, Februar
A question related to this. Is it ever meaningful to include norms for "int",
"date", "long"... fieldTypes? Length normalization certainly doesn't make sense
and what happens if you add an index-time boost to an int field? Would the
boost be applied for queries like price:100 or price:[100 TO 20
[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210163#comment-13210163
]
Uwe Schindler commented on LUCENE-3795:
---
bq. From a functional perspective, as Davi
[
https://issues.apache.org/jira/browse/LUCENE-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210134#comment-13210134
]
Uwe Schindler commented on LUCENE-3796:
---
+1 to apply patch. This also effects Numer
[
https://issues.apache.org/jira/browse/LUCENE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210135#comment-13210135
]
Uwe Schindler commented on LUCENE-3792:
---
+1 for KeywordField
For symmetry i would
77 matches
Mail list logo
