heh, I thought the peculiar thing was that it was just building the .NET
3.5 version randomly instead of being an actual deliberate change. I was
trying to think how that was possible. =)
On Sun, Jul 22, 2012 at 2:55 PM, Christopher Currens
currens.ch...@gmail.com wrote:
It is, but I didn't
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14922/
2 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SyncSliceTest
Error Message:
ERROR: SolrIndexSearcher opens=24 closes=23
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearcher opens=24
[
https://issues.apache.org/jira/browse/SOLR-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420495#comment-13420495
]
Markus Jelsma commented on SOLR-1781:
-
The problem is resolved. The `bad` node created
Thanks for also taking a look at the test failures!
On 20 July 2012 19:14, Robert Muir rcm...@gmail.com wrote:
Hi Martinj: thanks for looking into this!
I think have a better fix for these:
the problem is actually in the AssertingAtomicReaders that
AssertingDirectoryReader wraps its
Hi,
Thanks for also taking a look at the test failures!
On 20 July 2012 19:14, Robert Muir rcm...@gmail.com wrote:
Hi Martinj: thanks for looking into this!
I think have a better fix for these:
the problem is actually in the AssertingAtomicReaders that
AssertingDirectoryReader
That is wanted! We want to test SlowMultiReaderWrapper and verify that it
really behaves like a full conformant AtomicReader. Because of that we
sometimes war with it. The fix Robert did is fine and is identical to the one
we did in the past. As this is no real Lucene usage pattern, not
Just for completeness -- something I forgot about.
There is one more option that I forgot about -- that junit4 ANT
target is meant to simplify splitting suites into multiple JVMs and
providing nicer integration with the randomized runner (seed passing
etc). You can still use a regular ANT's junit
[
https://issues.apache.org/jira/browse/LUCENE-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420504#comment-13420504
]
Shai Erera commented on LUCENE-3793:
Noticed that TestTaxonomyCombined has an ignored
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/316/
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SyncSliceTest
Error Message:
ERROR: SolrIndexSearcher opens=24 closes=23
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearcher opens=24
Hi,
If you use a plain SlowCompositeReaderWrapper without an FCInvisible wrapper on
the MultiReader behind, the FC insanity checker will warn the user! So
FieldCache.DEFAULT.getInts(SlowCompositeReaderWrapper.wrap(directoryReader),
field) will create insanity and the detector will find that.
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2951/
1 tests failed.
FAILED: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Shard still reported as live in zk
Stack Trace:
java.lang.AssertionError: Shard still reported as live in zk
at
I'll make some attempts today to try and get this happy on the apache Jenkins
sever.
Sent from my iPhone
On Jul 23, 2012, at 5:55 AM, Apache Jenkins Server jenk...@builds.apache.org
wrote:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2951/
1 tests failed.
[
https://issues.apache.org/jira/browse/LUCENE-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420548#comment-13420548
]
Michael McCandless commented on LUCENE-4242:
bq. A pro-rate is just a guess
[
https://issues.apache.org/jira/browse/LUCENE-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420556#comment-13420556
]
Shai Erera commented on LUCENE-4234:
Committed to trunk rev 1364576. Porting now to
Build: https://builds.apache.org/job/Solr-4.x/46/
1 tests failed.
REGRESSION: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Shard still reported as live in zk
Stack Trace:
java.lang.AssertionError: Shard still reported as live in zk
at
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420569#comment-13420569
]
Michael McCandless commented on LUCENE-4245:
If IndexWriter.close throws
[
https://issues.apache.org/jira/browse/LUCENE-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-4234.
Resolution: Fixed
Lucene Fields: New,Patch Available (was: New)
Committed r1364582 (4x)
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420589#comment-13420589
]
Mark Miller commented on LUCENE-4245:
-
You don't always have control over these
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420594#comment-13420594
]
Uwe Schindler commented on LUCENE-4245:
---
I think my patch does exactly that. If you
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420600#comment-13420600
]
Mark Miller commented on LUCENE-4245:
-
bq. that calls IndexWriter.close() be a while
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420603#comment-13420603
]
Robert Muir commented on LUCENE-4245:
-
The trap is that close() does slow things at
[
https://issues.apache.org/jira/browse/LUCENE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-3505.
-
Resolution: Fixed
BooleanScorer2.freq() doesnt work unless you call score() first.
Robert Muir created LUCENE-4246:
---
Summary: Fix IndexWriter.close() to not commit or wait for pending
merges
Key: LUCENE-4246
URL: https://issues.apache.org/jira/browse/LUCENE-4246
Project: Lucene -
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420606#comment-13420606
]
Robert Muir commented on LUCENE-4245:
-
I'm gonna spin off an issue for this. Its so
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4246:
Fix Version/s: 4.0
Assignee: Robert Muir
Fix IndexWriter.close() to not commit or
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420610#comment-13420610
]
Shai Erera commented on LUCENE-4245:
bq. I'm gonna spin off an issue for this. Its so
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420613#comment-13420613
]
Uwe Schindler commented on LUCENE-4245:
---
What is the problem with the attached
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420612#comment-13420612
]
Shai Erera commented on LUCENE-4246:
Moving my comment from LUCENE-4245:
Why is that
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420616#comment-13420616
]
Uwe Schindler commented on LUCENE-4246:
---
bq. Perhaps, if you want to simplify,
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420618#comment-13420618
]
Michael McCandless commented on LUCENE-4245:
bq. I don't think close should
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420619#comment-13420619
]
Robert Muir commented on LUCENE-4246:
-
Because is transactional. Outputstream is not
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420621#comment-13420621
]
Robert Muir commented on LUCENE-4245:
-
This is so broken for something transactional
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420622#comment-13420622
]
Shai Erera commented on LUCENE-4246:
Still, I don't want to call commit(), then
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420627#comment-13420627
]
Michael McCandless commented on LUCENE-4246:
{quote}
Perhaps, if you want to
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420628#comment-13420628
]
Robert Muir commented on LUCENE-4246:
-
Close should alias to rollback. Otherwise its
Committed a fix to trunk and 4x which simplifies addCategory -- it only
checks the cache outside the synchronized block, otherwise everything runs
in a sync'ed block.
Hopefully that does it ...
Shai
On Sat, Jul 14, 2012 at 9:56 AM, Policeman Jenkins Server
jenk...@sd-datasolutions.de wrote:
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420634#comment-13420634
]
Robert Muir commented on LUCENE-4246:
-
I don't think we need to worry too much about
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420633#comment-13420633
]
Mark Miller commented on LUCENE-4245:
-
bq. What is the problem with the attached
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420638#comment-13420638
]
Uwe Schindler commented on LUCENE-4246:
---
I am fine with either proposal, but this
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420644#comment-13420644
]
Uwe Schindler edited comment on LUCENE-4245 at 7/23/12 1:23 PM:
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420644#comment-13420644
]
Uwe Schindler commented on LUCENE-4245:
---
bq. If that means waiting for all merge
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/317/
1 tests failed.
REGRESSION: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Timeout occured while waiting response from server at:
http://localhost:60639/solr/collection1
Stack Trace:
[
https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420692#comment-13420692
]
Jan Høydahl commented on SOLR-3439:
---
bq. 1. Any reason to limit it to 5.0 and not
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420693#comment-13420693
]
Robert Muir commented on LUCENE-4246:
-
I think its related: I think close() is too
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420696#comment-13420696
]
Robert Muir commented on LUCENE-4246:
-
{quote}
By this issue we just have less
[
https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-3439:
--
Attachment: SOLR-3439.patch
New patch:
* Uses filename from resource.name - new field resourcename,
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420700#comment-13420700
]
Uwe Schindler commented on LUCENE-4246:
---
OK. That's all I wanted to make the test
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420710#comment-13420710
]
Robert Muir commented on LUCENE-4246:
-
{quote}
Would close() throw an exception if
I fired up my FreeBSD virt machine this morning - ill get this worked out.
Sent from my iPhone
On Jul 23, 2012, at 10:28 AM, Apache Jenkins Server jenk...@builds.apache.org
wrote:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/317/
1 tests failed.
REGRESSION:
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4245:
--
Attachment: LUCENE-4245.patch
Much more easier patch:
- In preparation for Roberts work on
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420732#comment-13420732
]
Robert Muir commented on LUCENE-3892:
-
FYI: I committed the TestPostingsFormat here
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14924/
1 tests failed.
REGRESSION: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Timeout occured while waiting response from server at:
http://localhost:34674/solr/collection1
Stack Trace:
[
https://issues.apache.org/jira/browse/SOLR-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420750#comment-13420750
]
Robert Muir commented on SOLR-3623:
---
+1 to commit. I agree lets fix this for now and move
Hello,
We released the 4.0-alpha at the beginning of the month, I think its
time we start figuring out what/when the beta should be.
What:
Originally one proposal was that the 4.0-beta would offer some
additional guarantees (such as keeping API backwards compatibility /
config-file backwards
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x-java7/182/
1 tests failed.
REGRESSION: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Shard still reported as live in zk
Stack Trace:
java.lang.AssertionError: Shard still reported as live in zk
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/553/
5 tests failed.
FAILED: org.apache.lucene.index.TestPostingsFormat.test
Error Message:
Thread threw an uncaught exception, thread: Thread[Thread-1101,5,]
Stack Trace:
java.lang.RuntimeException: Thread threw an uncaught
[
https://issues.apache.org/jira/browse/LUCENE-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-4197:
-
Attachment: LUCENE-4197_rename_CachedDistanceValueSource.patch
renamed
maybe a simpletext bug... I'll look into it!
On Mon, Jul 23, 2012 at 12:53 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/553/
5 tests failed.
FAILED: org.apache.lucene.index.TestPostingsFormat.test
Error Message:
Looks like http://svn.apache.org/viewvc?view=revisionrevision=1364083
I'll merge the fix from the pfor branch.
On Mon, Jul 23, 2012 at 1:04 PM, Robert Muir rcm...@gmail.com wrote:
maybe a simpletext bug... I'll look into it!
On Mon, Jul 23, 2012 at 12:53 PM, Apache Jenkins Server
[
https://issues.apache.org/jira/browse/SOLR-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-3662.
Resolution: Fixed
Fix Version/s: 4.0
core reload can go back in time
Zied Hamdi created LUCENE-4247:
--
Summary: QueryParser doesn't call Analyzer
Key: LUCENE-4247
URL: https://issues.apache.org/jira/browse/LUCENE-4247
Project: Lucene - Core
Issue Type: Bug
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/318/
1 tests failed.
FAILED: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Timeout occured while waiting response from server at:
http://localhost:44781/solr/collection1
Stack Trace:
[
https://issues.apache.org/jira/browse/LUCENE-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-4247.
---
Resolution: Invalid
Assignee: Uwe Schindler
This is not a bug, because you are using
In the spatial utils package I've got a ValueSourceFilter which is a Filter
based on a ValueSource with a minimum and maximum range. It does what you'd
think it does. This seems like something useful in the query module in the
org.apache.lucene.queries.function package. Any opinions? Here
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14925/
1 tests failed.
FAILED: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Timeout occured while waiting response from server at:
http://localhost:45023/solr/collection1
Stack Trace:
[
https://issues.apache.org/jira/browse/SOLR-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-3623.
Resolution: Fixed
Committed revision 1364728. - trunk
Committed revision 1364738. - 4x
[
https://issues.apache.org/jira/browse/SOLR-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3623:
---
Summary: inconsistent treatment of lucene jars third-party deps in
analysis-extras uima (in war and in
[
https://issues.apache.org/jira/browse/LUCENE-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420826#comment-13420826
]
Uwe Schindler commented on LUCENE-4247:
---
Just to add some background information:
My opinions inline:
On Jul 23, 2012, at 12:28 PM, Robert Muir wrote:
Hello,
We released the 4.0-alpha at the beginning of the month, I think its
time we start figuring out what/when the beta should be.
What:
Originally one proposal was that the 4.0-beta would offer some
additional
[
https://issues.apache.org/jira/browse/SOLR-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-3656.
Resolution: Fixed
Fix Version/s: 4.0
use same data dir in core reload
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x-java7/183/
2 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SyncSliceTest
Error Message:
ERROR: SolrIndexSearcher opens=24 closes=23
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearcher opens=24
Robert Muir created LUCENE-4248:
---
Summary: Producers to the Codec API don't always follow the spec
Key: LUCENE-4248
URL: https://issues.apache.org/jira/browse/LUCENE-4248
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4248:
Attachment: LUCENE-4248.patch
the start to a patch: some tests still fail.
I figure we can get
I hate the black hole :)
I can repro this on my freebsd machine - it's due to the unlimited connection
timeout and black hole.
I need to modify the test to explicitly wait to make sure it doesn't try to
query when it will be directed to a downed node. I hate that because I'd like
to test that
[
https://issues.apache.org/jira/browse/LUCENE-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn van Groningen updated LUCENE-4224:
--
Affects Version/s: 4.0-ALPHA
Fix Version/s: 4.0
Simplify
+1 Good idea. I think that there also should be other implementations
for the different primitive types.
Maybe the inclusive or exclusive filtering can be a boolean option?
Martijn
On 23 July 2012 19:37, Smiley, David W. dsmi...@mitre.org wrote:
In the spatial utils package I've got a
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2953/
1 tests failed.
REGRESSION: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Timeout occured while waiting response from server at:
http://localhost:32077/solr/collection1
Stack Trace:
[
https://issues.apache.org/jira/browse/LUCENE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4248:
Attachment: LUCENE-4248.patch
Updated patch: fixing some more bugs in these producers.
I added a
[
https://issues.apache.org/jira/browse/SOLR-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420881#comment-13420881
]
Dan Kogan commented on SOLR-3585:
-
Michael, would this patch work with version 3.6?
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420884#comment-13420884
]
Shai Erera commented on LUCENE-4246:
I still don't understand why change behavior
[
https://issues.apache.org/jira/browse/LUCENE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4248:
Attachment: LUCENE-4248.patch
one more check, and also fix a bad assert in BlockTree writer
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420890#comment-13420890
]
Robert Muir commented on LUCENE-4246:
-
{quote}
I still don't understand why change
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420894#comment-13420894
]
Yonik Seeley commented on LUCENE-4246:
--
bq. But I don't think there is a good
[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420898#comment-13420898
]
Robert Muir commented on LUCENE-4246:
-
Thats ok: resistance to change is just
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4245:
--
Attachment: LUCENE-4245.patch
Improved patch, much simplier. close() is no longer
[
https://issues.apache.org/jira/browse/SOLR-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420934#comment-13420934
]
Mikhail Khludnev commented on SOLR-3585:
The code itself (solr/core/src/java/)
[
https://issues.apache.org/jira/browse/LUCENE-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420936#comment-13420936
]
David Smiley commented on LUCENE-4223:
--
I added some docs in trunk r1364782 (4x:
[
https://issues.apache.org/jira/browse/LUCENE-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420936#comment-13420936
]
David Smiley edited comment on LUCENE-4223 at 7/23/12 8:22 PM:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x-java7/184/
1 tests failed.
FAILED: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch
Error Message:
Shard still reported as live in zk
Stack Trace:
java.lang.AssertionError: Shard still reported as live in zk
at
[
https://issues.apache.org/jira/browse/LUCENE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4248:
Attachment: LUCENE-4248.patch
Here's a patch for the rest of the postings API.
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/419/
All tests passed
Build Log:
[...truncated 2712 lines...]
[javac] Compiling 12 source files to
C:\Jenkins\workspace\Lucene-Solr-4.x-Windows-Java6-64\lucene\build\spatial\classes\test
[javac]
I committed a fix for this.
On Mon, Jul 23, 2012 at 4:49 PM, Policeman Jenkins Server
jenk...@sd-datasolutions.de wrote:
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/419/
All tests passed
Build Log:
[...truncated 2712 lines...]
[javac] Compiling 12
Scott Smerchek created LUCENE-4249:
--
Summary: The PayloadTermWeight explanation hides the details of
the payload score
Key: LUCENE-4249
URL: https://issues.apache.org/jira/browse/LUCENE-4249
[
https://issues.apache.org/jira/browse/LUCENE-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420957#comment-13420957
]
Scott Smerchek commented on LUCENE-4249:
Once I can get past the hurdles of
[
https://issues.apache.org/jira/browse/LUCENE-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420958#comment-13420958
]
Robert Muir commented on LUCENE-4249:
-
Thanks Scott. git formatted patches are fine
[
https://issues.apache.org/jira/browse/LUCENE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4248.
-
Resolution: Fixed
Fix Version/s: 5.0
4.0
Producers to the Codec
Thank you Robert!
-
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in context:
http://lucene.472066.n3.nabble.com/JENKINS-Lucene-Solr-4-x-Windows-Java6-64-Build-419-Failure-tp3996835p3996843.html
Sent from the Lucene - Java Developer
[
https://issues.apache.org/jira/browse/SOLR-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420972#comment-13420972
]
Tobias Berg commented on SOLR-2094:
---
I'm having the same issue in 3.6. If there is a
Yeah. In Visual Studio you can just change the release configuration
manually, and no matter what, it will only build for the framework you have
selected. With the build script, I didn't know how to update jenkins and I
knew that in all deploy cases we needed both built, so for the time being
it
[
https://issues.apache.org/jira/browse/LUCENE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4245:
--
Attachment: LUCENE-4245.patch
Patch that preserves Thread interrupt status and handles thread
1 - 100 of 144 matches
Mail list logo