LuceneTestCase should not have a static method could throw exceptions.
Key: LUCENENET-418
URL: https://issues.apache.org/jira/browse/LUCENENET-418
Project: Lucene.Net
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040083#comment-13040083
]
Simon Willnauer commented on LUCENE-3147:
-
bq. Short summary - we're leaking
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040096#comment-13040096
]
Bill Bell commented on SOLR-2242:
-
From rajini:
The patch solr 2242 for getting
[
https://issues.apache.org/jira/browse/SOLR-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040124#comment-13040124
]
Adrien Grand commented on SOLR-2548:
Hello Janne,
Is there any reason why you didn't
[
https://issues.apache.org/jira/browse/SOLR-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040129#comment-13040129
]
Robert Muir commented on SOLR-2519:
---
A few opinions:
1. First of all, I am +1 to the
Build: https://builds.apache.org/hudson/job/Solr-trunk/1518/
All tests passed
Build Log (for compile errors):
[...truncated 17248 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
[
https://issues.apache.org/jira/browse/SOLR-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040142#comment-13040142
]
Janne Majaranta commented on SOLR-2548:
---
Hi Adrien,
It's a initial patch. I don't
I think this jdoc warning is causing the build failure:
[javadoc]
/usr/home/hudson/hudson-slave/workspace/Solr-trunk/checkout/solr/src/java/org/apache/solr/highlight/DefaultSolrHighlighter.java:293:
warning - Tag @link: reference not found:
org.apache.lucene.search.highlight.GapFragmenter
Same javadoc warning is failing 3.x too I think.
I'll fix.
Mike
http://blog.mikemccandless.com
On Fri, May 27, 2011 at 1:55 AM, Apache Jenkins Server
hud...@hudson.apache.org wrote:
Build: https://builds.apache.org/hudson/job/Solr-3.x/367/
No tests ran.
Build Log (for compile errors):
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040189#comment-13040189
]
Shai Erera commented on LUCENE-3147:
bq. In BlockTermsWriter, the success boolean is
Build: https://builds.apache.org/hudson/job/Lucene-Solr-Maven-3.x/135/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestCheckIndex.testLuceneConstantVersion
Error Message:
Invalid version: 3.2-SNAPSHOT
Stack Trace:
java.lang.AssertionError: Invalid version: 3.2-SNAPSHOT
at
Apache Solr needs an updated TIKA version in its extraction libraries
-
Key: SOLR-2550
URL: https://issues.apache.org/jira/browse/SOLR-2550
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-3147:
---
Attachment: LUCENE-3147.patch
More leak fixes. Do you think I should commit what I've fixed
[
https://issues.apache.org/jira/browse/SOLR-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C S updated SOLR-2551:
--
Summary: Checking dataimport.properties for write access during startup
(was: Checking dataimport.properties for write
Checking dataimport.properties for write access
---
Key: SOLR-2551
URL: https://issues.apache.org/jira/browse/SOLR-2551
Project: Solr
Issue Type: Improvement
Components: contrib -
[
https://issues.apache.org/jira/browse/SOLR-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040243#comment-13040243
]
Koji Sekiguchi commented on SOLR-2546:
--
Please use solr-user mailing list before
[
https://issues.apache.org/jira/browse/SOLR-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi resolved SOLR-2546.
--
Resolution: Invalid
Using hl.useFastVectorHighlighter with copyfield multivalued boosted we
[
https://issues.apache.org/jira/browse/SOLR-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040255#comment-13040255
]
syed abdul kather commented on SOLR-1093:
-
Please add this feauture
A
Please vote to release the artifacts at:
http://people.apache.org/~mikemccand/lucene_solr_320/rc1/
as Lucene 3.2.0 and Solr 3.2.0.
Mike
http://blog.mikemccandless.com
-
To unsubscribe, e-mail:
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040295#comment-13040295
]
Uwe Schindler edited comment on LUCENE-3147 at 5/27/11 3:54 PM:
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040295#comment-13040295
]
Uwe Schindler commented on LUCENE-3147:
---
Can we also add a closeSafely others
[
https://issues.apache.org/jira/browse/SOLR-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040298#comment-13040298
]
Michael McCandless commented on SOLR-2519:
--
bq. I think we need to stop kidding
[
https://issues.apache.org/jira/browse/LUCENE-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040304#comment-13040304
]
Michael McCandless commented on LUCENE-3097:
Right, I think for post-grouping
Michael,
A while ago I submitted SOLR-2462 with a patch to fix a critical bug in Solr's
spellchecker. I'm not sure if the patch included is the best approach to
fixing the problem but I do think any next release should include a fix for
this.
James Dyer
E-Commerce Systems
Ingram Content
Mike
Thanks for taking the initiative !
Do you think we can allow for 1 week or so in order for people to be able to
finish things they're currently working on (and expect to finish within the
next few days) and want them to be in 3.2?
I ask because I don't recall seeing a feature freeze note,
+1
i found a 'foo.txt' in the root of lucene-3.2.0.zip with the text
'kajdsfkj' in it, but I don't think this need to block anything.
On Fri, May 27, 2011 at 8:50 AM, Michael McCandless
luc...@mikemccandless.com wrote:
Please vote to release the artifacts at:
On Fri, May 27, 2011 at 9:57 AM, Shai Erera ser...@gmail.com wrote:
from releasing. However, by following a certain protocol about a release, we
give people enough time to prepare for it.
I am confused why we need to have a protocol where people have time to plan?
Isn't it true that what we
[
https://issues.apache.org/jira/browse/SOLR-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040324#comment-13040324
]
Ryan McKinley commented on SOLR-2400:
-
bq. I would prefer / (like a fs path), any other
I am confused why we need to have a protocol where people have time to
plan?
Why not :)? Are protocols bad? From my experience, protocols only help
clarify things. And it's not a 100 pages protocol -- the one that you've
followed (even though not written one) makes sense to me. But then, we
True. Only thought that we might want to give people time to ensure that
things that are important to them are included in 3.2.
Why? if these issues are so critical they should be marked as blockers!
Again, why wait a week, we could release again in a week instead!
This whole lifecycle is
I think robert is right here. We want to do more frequent releases and
to go that path we need to stop waiting for a week for feature /
improvement X. We can spin another release in 4 weeks I think we
should actually. If we do that and increment the version number by 1
each time we reach 3.9 by
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040348#comment-13040348
]
Simon Willnauer commented on LUCENE-3147:
-
bq. Can we also add a closeSafely
[
https://issues.apache.org/jira/browse/SOLR-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040349#comment-13040349
]
Simon Willnauer commented on SOLR-1093:
---
We got lots of votes on this issue, seems
[
https://issues.apache.org/jira/browse/SOLR-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned SOLR-1093:
-
Assignee: Simon Willnauer
A RequestHandler to run multiple queries in a batch
On Fri, May 27, 2011 at 1:18 PM, Shai Erera ser...@gmail.com wrote:
Only thought that we might want to give people time to ensure that
things that are important to them are included in 3.2.
I know this approach is tempting, and what we normally do, but I
think this is the core problem of why
Ok let's give it a try. I'll test the artifacts by Sunday.
Shai
On Fri, May 27, 2011 at 8:43 PM, Michael McCandless
luc...@mikemccandless.com wrote:
On Fri, May 27, 2011 at 1:18 PM, Shai Erera ser...@gmail.com wrote:
Only thought that we might want to give people time to ensure that
[
https://issues.apache.org/jira/browse/SOLR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040373#comment-13040373
]
Michael McCandless commented on SOLR-2524:
--
Martijn, with this patch, Solr 3.x is
[
https://issues.apache.org/jira/browse/SOLR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040377#comment-13040377
]
Martijn van Groningen commented on SOLR-2524:
-
bq. Solr 3.x is able to return
[
https://issues.apache.org/jira/browse/SOLR-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040381#comment-13040381
]
Michael McCandless commented on SOLR-2543:
--
I'm not sure why, but when I apply
AbstractSolrTestCase should also assert that all opened SolrIndexSearchers are
closed
-
Key: SOLR-2552
URL: https://issues.apache.org/jira/browse/SOLR-2552
Project:
[
https://issues.apache.org/jira/browse/SOLR-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved SOLR-2543.
--
Resolution: Fixed
Thanks Martijn!
Backport the trunk's version of SolrTestCaseJ4 to
[
https://issues.apache.org/jira/browse/SOLR-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040421#comment-13040421
]
Michael McCandless commented on SOLR-2543:
--
OK got to the bottom of this... it was
[
https://issues.apache.org/jira/browse/SOLR-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated SOLR-2552:
-
Attachment: SOLR-2552.patch
Patch.
I'll commit soon, and port to trunk too.
[
https://issues.apache.org/jira/browse/SOLR-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040439#comment-13040439
]
Robert Muir commented on SOLR-2523:
---
Hi Martijn, there are some fun things if you run
[
https://issues.apache.org/jira/browse/SOLR-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040440#comment-13040440
]
Robert Muir commented on SOLR-2523:
---
Hi Martijn, there are some fun things if you run
[
https://issues.apache.org/jira/browse/SOLR-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated SOLR-2552:
-
Attachment: SOLR-2552.patch
New patch, also moving the start/endTrackingSearchers to
[
https://issues.apache.org/jira/browse/SOLR-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040444#comment-13040444
]
Robert Muir commented on SOLR-2552:
---
this looks good, maybe this was causing the test
[
https://issues.apache.org/jira/browse/SOLR-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040450#comment-13040450
]
Michael McCandless commented on SOLR-2552:
--
Yes, I believe it was!
In fact there
[
https://issues.apache.org/jira/browse/SOLR-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved SOLR-2552.
--
Resolution: Fixed
AbstractSolrTestCase should also assert that all opened
On Thu, 12 May 2011, Christian Heimes wrote:
Am 12.05.2011 21:10, schrieb Andi Vajda:
Indeed.
Thank you for patch.
You are welcome!
How's yesterday's issue's patch doing ?
Is it reliable enough ?
So far the patch is reliable and has improved the stability a lot. I
haven't seen a single
Nested Field Collapsing
---
Key: SOLR-2553
URL: https://issues.apache.org/jira/browse/SOLR-2553
Project: Solr
Issue Type: Improvement
Components: SearchComponents - other
Reporter: Martijn Laarman
[
https://issues.apache.org/jira/browse/SOLR-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn van Groningen updated SOLR-2523:
Attachment: SOLR-2523.patch
Nice catch! I've updated the patch, so for the Thai
upgrade icu to 4.8
--
Key: LUCENE-3149
URL: https://issues.apache.org/jira/browse/LUCENE-3149
Project: Lucene - Java
Issue Type: Task
Reporter: Robert Muir
Fix For: 3.3, 4.0
we should upgrade from
[
https://issues.apache.org/jira/browse/LUCENE-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3149:
Attachment: LUCENE-3149.patch
upgrade icu to 4.8
--
Key:
[
https://issues.apache.org/jira/browse/SOLR-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040478#comment-13040478
]
Martijn van Groningen commented on SOLR-2553:
-
This looks like an interesting
+1 (if I get a vote)
On 5/27/11 10:27 AM, Dyer, James james.d...@ingrambook.com wrote:
Michael,
A while ago I submitted SOLR-2462 with a patch to fix a critical bug in
Solr's spellchecker. I'm not sure if the patch included is the best
approach to fixing the problem but I do think any next
Won't have time to test the artifacts today, but my opinion (even though it
sounds settled):
If someone really wants a few features in, lets release 3.3 next month :)
Otherwise, lets just start releasing - that's the whole point of the make it
easier to release push. People shouldn't need to
[
https://issues.apache.org/jira/browse/LUCENE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujit Pal updated LUCENE-3141:
--
Attachment: lucene-3141-patch-2.diff
Path restoring fragInfos to package protected and exposing a
[
https://issues.apache.org/jira/browse/LUCENE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujit Pal updated LUCENE-3141:
--
Attachment: LIABookTest.java
Modified test case (to verify patch) to work against modified patch.
[
https://issues.apache.org/jira/browse/LUCENE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujit Pal updated LUCENE-3141:
--
Attachment: lucene-3141-patch-2.diff
Adding same patch again, this time with Grant License to ASF...
[
https://issues.apache.org/jira/browse/LUCENE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujit Pal updated LUCENE-3141:
--
Attachment: (was: lucene-3141-patch-2.diff)
FastVectorHighlighter - expose
[
https://issues.apache.org/jira/browse/LUCENE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040538#comment-13040538
]
Sujit Pal commented on LUCENE-3141:
---
Thanks Koji, I have attached the updated patch
[
https://issues.apache.org/jira/browse/LUCENE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated LUCENE-3141:
---
Attachment: LUCENE-3141.patch
I changed the member private and used the new getter method
[
https://issues.apache.org/jira/browse/LUCENE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi resolved LUCENE-3141.
Resolution: Fixed
Fix Version/s: (was: 3.2)
3.3
trunk:
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-3147:
---
Attachment: LUCENE-3147.patch
Added IOUtils.closeSafely variants that take IterableCloseable,
[
https://issues.apache.org/jira/browse/LUCENE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040550#comment-13040550
]
Shai Erera commented on LUCENE-3147:
Another thing to clarify, everyone can reproduce
Clearly a year+ is too long to release, and thankfully it appears that's in
the past for Lucene/Solr. But on the other extreme, one can release too
quickly as well, of course. There is overhead to performing the release
itself. Consequently there should be enough goodness in the release to
make
[
https://issues.apache.org/jira/browse/SOLR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040551#comment-13040551
]
David Smiley commented on SOLR-2524:
Shouldn't the fix version be 3.2 ? It appears
68 matches
Mail list logo
