[
https://issues.apache.org/jira/browse/SOLR-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211712#comment-13211712
]
Koji Sekiguchi commented on SOLR-3110:
--
Hi Shyam,
From the mail thread:
{quote}
[
https://issues.apache.org/jira/browse/SOLR-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211721#comment-13211721
]
Jun Ohtani commented on SOLR-2909:
--
Yes.
Probably the word of the user's dictionary is not
[
https://issues.apache.org/jira/browse/SOLR-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211736#comment-13211736
]
Christian Moen commented on SOLR-2909:
--
Thanks.
Sekiguchi-san, I'm happy to test and
Welcome Sami!
Mike
On Feb 19, 2012, at 10:32 AM, Robert Muir rcm...@gmail.com wrote:
I'm pleased to announce that Sami Siren has joined our ranks as a committer.
He has been contributing various patches to Lucene/Solr, especially to
Solr's distributed indexing capabilities.
Sami, its
[
https://issues.apache.org/jira/browse/LUCENE-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211766#comment-13211766
]
Jan Høydahl commented on LUCENE-3806:
-
Hmm, shouldn't this be done in HTML/CSS these
Velocity /browse GUI should stick to AND as defaultOperator
---
Key: SOLR-3145
URL: https://issues.apache.org/jira/browse/SOLR-3145
Project: Solr
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SOLR-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211776#comment-13211776
]
Jan Høydahl commented on SOLR-3145:
---
Two options
A) Change schema.xml defaultOperator
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12470/
All tests passed
Build Log (for compile errors):
[...truncated 12911 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For
[
https://issues.apache.org/jira/browse/SOLR-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kaleem Ahmed closed SOLR-2953.
--
Resolution: Not A Problem
Closing as the 4.0 has this feature already implemented through similarity
[
https://issues.apache.org/jira/browse/SOLR-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211802#comment-13211802
]
Robert Muir commented on SOLR-2909:
---
+1, good catch.
Add support for
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211825#comment-13211825
]
Jan Høydahl commented on SOLR-3141:
---
I think 4.0 is a good train in which to do this
You need to follow the instructions here:
http://lucene.apache.org/solr/discussion.html
Best
Erick
2012/2/19 bingbingwang jsuser1...@hotmail.com:
As titled.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For
GitHub user astubbs synchronized the pull request at
https://github.com/apache/lucene-solr/pull/3
Better logging of undefined field error (SOLR-3077)
https://issues.apache.org/jira/browse/SOLR-3077
You can merge this pull request into a Git repository by running
$ git pull
GitHub user JackDanger synchronized the pull request at
https://github.com/apache/lucene-solr/pull/2
Fixing typo in example schema: 'salves' = 'slaves'
Just a typo in a comment. Safe to merge.
You can merge this pull request into a Git repository by running
$ git pull
[
https://issues.apache.org/jira/browse/SOLR-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir reassigned SOLR-3143:
-
Assignee: Robert Muir
Supply a phrase-oriented QueryConverter for Suggesters
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211849#comment-13211849
]
Yonik Seeley commented on SOLR-3141:
bq. The compensation is that they are forced to
[
https://issues.apache.org/jira/browse/SOLR-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-3143:
--
Attachment: SOLR-3143.patch
Wow, phrase suggestions are ridiculously complicated to get working.
I
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211852#comment-13211852
]
Yonik Seeley commented on SOLR-3141:
bq. and another paragraph about
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12471/
All tests passed
Build Log (for compile errors):
[...truncated 13288 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For
Cleanup suggester API
-
Key: LUCENE-3807
URL: https://issues.apache.org/jira/browse/LUCENE-3807
Project: Lucene - Java
Issue Type: Improvement
Components: modules/other
Affects Versions: 3.6, 4.0
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3807:
Attachment: LUCENE-3807.patch
here is a first patch extracting a BytesRefIterator as a
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211890#comment-13211890
]
Dawid Weiss commented on LUCENE-3807:
-
+1.
Cleanup suggester API
What's the workflow for github pull requests? We can't just apply the patches
without the user signing off on the ASL, right? There still needs to be a
JIRA created with a patch that is checked ASL, as I understand it.
Clarification/discussion on this would be good to have.
Erik
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211898#comment-13211898
]
Jan Høydahl commented on SOLR-3141:
---
@Yonik, How would you feel about this approach
Create migration guide from 3.x to 4.0
--
Key: SOLR-3146
URL: https://issues.apache.org/jira/browse/SOLR-3146
Project: Solr
Issue Type: Task
Components: documentation
Reporter: Jan
[
https://issues.apache.org/jira/browse/SOLR-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211900#comment-13211900
]
Jan Høydahl commented on SOLR-3146:
---
Perhaps a page on the WIKI, and when mature, move to
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211902#comment-13211902
]
Jan Høydahl commented on SOLR-3141:
---
bq. This is a much bigger real problem (because
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211909#comment-13211909
]
Yonik Seeley commented on SOLR-3141:
bq. Add the new forceMerge feature, but instead of
[
https://issues.apache.org/jira/browse/SOLR-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren resolved SOLR-3068.
--
Resolution: Fixed
Fix Version/s: 4.0
3.6
Assignee: Sami Siren
[
https://issues.apache.org/jira/browse/SOLR-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211918#comment-13211918
]
Yonik Seeley commented on SOLR-3146:
So I've thought about changing to soft commits by
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211919#comment-13211919
]
Mark Miller commented on SOLR-3141:
---
I think when it comes to API breaks, trying to say
[
https://issues.apache.org/jira/browse/SOLR-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-2909:
-
Attachment: SOLR-2909.patch
Add support for ResourceLoaderAware tokenizerFactories in
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211921#comment-13211921
]
Robert Muir commented on LUCENE-3807:
-
I like the patch, but only one thing (its fine
[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211922#comment-13211922
]
Yonik Seeley commented on SOLR-3141:
bq. It's a terrible name at this point. Why are we
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211926#comment-13211926
]
Robert Muir commented on LUCENE-3807:
-
Again i just wanted to mention, i think its
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/395/
No tests ran.
Build Log (for compile errors):
[...truncated 7280 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
I would like to commit in LUCENE-3785 (tests framework refactoring).
If anybody wants me to delay this speak up within the next two hours
:)
Also, don't be mad at me if something doesn't work :) I've tested
locally as much as I could be I'm sure there'll be cases I didn't
think of. Also: ask if
Cool; pull-requests via GitHub. Has anyone reacted to one of these messages
and applied the change before? If so what was the process? Since
lucene-solr is a mirror, is it impossible?
~ David
-
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12472/
1 tests failed.
REGRESSION:
org.apache.lucene.benchmark.byTask.TestPerfTasksParse.testParseExamples
Error Message:
Could not parse sample file:
FileDataSource throws a FileNotFoundException when reading from named pipes
---
Key: SOLR-3147
URL: https://issues.apache.org/jira/browse/SOLR-3147
Project: Solr
Issue
On Mon, Feb 20, 2012 at 11:07 AM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12472/
1 tests failed.
REGRESSION:
org.apache.lucene.benchmark.byTask.TestPerfTasksParse.testParseExamples
Error Message:
Could not
Turkish uppercasing!
I love this one :)
D.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
On Mon, Feb 20, 2012 at 11:16 AM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
Turkish uppercasing!
I love this one :)
I fixed it in trunk. 3.x doesn't need a fix, it doesnt uppercase
--
lucidimagination.com
-
To
Switch LuceneTestCaseRunner to RandomizedRunner. Enforce Random sharing
contracts. Enforce thread leaks.
Key: LUCENE-3808
URL:
Ok, that's disappointing. So much for ASF projects being part of the social
coding revolution. It's a big deal, by the way. When people ask me what it's
all about, I point them to this blob post by the Springframework team:
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211955#comment-13211955
]
Robert Muir commented on LUCENE-3808:
-
{quote}
Add a validator for testXXX without
It's all part of an ongoing discussion about Git and GitHub at Apache. I don't
know what the official ruling is on this stuff.
Fixing a typo - sure, just fix it.
Larger patches contributed this way? It's a little up in the air I think. But
like I said - Apache seems to find that check box
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211960#comment-13211960
]
Uwe Schindler commented on LUCENE-3808:
---
Dawid: Please let us name our tests like
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211966#comment-13211966
]
Dawid Weiss commented on LUCENE-3808:
-
Ok, ok, ok... I will not enforce @Test, don't
[
https://issues.apache.org/jira/browse/LUCENE-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3800:
--
Attachment: LUCENE-3800.patch
Patch for trunk that enforces a soft-close (make it unuseable)
On Mon, Feb 20, 2012 at 11:07:05AM -0500, Mark Miller wrote:
I think the problem is around the ASF's thoughts on what it means to
contribute a patch in JIRA and click the check box about donating. They seem
to find that important, and you don't have the same mechanism when grabbing
pull
[
https://issues.apache.org/jira/browse/LUCENE-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211977#comment-13211977
]
Mark Miller commented on LUCENE-3806:
-
bq. Hmm, shouldn't this be done in HTML/CSS
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-3808:
Description:
Switch the runner to RandomizedRunner. Enforce the following:
- Random sharing will
[
https://issues.apache.org/jira/browse/LUCENE-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211982#comment-13211982
]
Robert Muir commented on LUCENE-3806:
-
I like any button really... we are hiding the
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211999#comment-13211999
]
Uwe Schindler commented on LUCENE-3808:
---
:-)
Switch
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212001#comment-13212001
]
Uwe Schindler commented on LUCENE-3808:
---
bq. I was wondering if anyone would ever
[
https://issues.apache.org/jira/browse/LUCENE-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212003#comment-13212003
]
DM Smith commented on LUCENE-3806:
--
Regarding image vs txt, an image is harder to
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212004#comment-13212004
]
Robert Muir commented on LUCENE-3808:
-
{quote}
@Override is indeed not really
[
https://issues.apache.org/jira/browse/LUCENE-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212012#comment-13212012
]
Dawid Weiss commented on LUCENE-3808:
-
I like @Override, I even wish it were an
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212036#comment-13212036
]
Simon Willnauer commented on LUCENE-3807:
-
I committed the patch to trunk and
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1774/
2 tests failed.
FAILED: org.apache.lucene.search.suggest.TestBytesRefList.testSort
Error Message:
null
Stack Trace:
junit.framework.AssertionFailedError
at
[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212038#comment-13212038
]
Ryan McKinley commented on LUCENE-3795:
---
Thanks for pushing this forward David!
[
https://issues.apache.org/jira/browse/LUCENE-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212039#comment-13212039
]
Dawid Weiss commented on LUCENE-3785:
-
I talked to Robert a bit and I've decided to
[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212041#comment-13212041
]
Ryan McKinley commented on LUCENE-3795:
---
David -- do you want to go ahead and make
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12475/
1 tests failed.
FAILED: org.apache.lucene.search.suggest.TestBytesRefList.testSort
Error Message:
entry 1293 doesn't match expected:[] but was:[]
Stack Trace:
at
I just committed a fix
simon
On Mon, Feb 20, 2012 at 9:06 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12475/
1 tests failed.
FAILED: org.apache.lucene.search.suggest.TestBytesRefList.testSort
Error Message:
I committed cleanups to the svn:ignore values on trunk and branch_3x.
Mostly I just removed things that are now obsolete, but I may have un-ignored
things that should remain ignored. If you find this to be true, please feel
free to fix, or let me know, and I will fix.
I have a question about
pcj-*
simple-xml-*
colt-*
nni-*
downloads
Should any of these still be there?
These are back from the days when these libraries had to be downloaded
separately because of license incompatibilities, Steve. You can remove
them -- we have replaced all
Thanks Dawid. I've removed them. - Steve
-Original Message-
From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of
Dawid Weiss
Sent: Monday, February 20, 2012 3:51 PM
To: dev@lucene.apache.org
Subject: Re: svn:ignore cleanup
pcj-*
simple-xml-*
SystemInfoHandler does not expose all available info
Key: SOLR-3148
URL: https://issues.apache.org/jira/browse/SOLR-3148
Project: Solr
Issue Type: Bug
Affects Versions: 4.0
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12476/
1 tests failed.
FAILED:
org.apache.solr.handler.component.SpellCheckComponentTest.testThresholdTokenFrequency
Error Message:
Path not found: /spellcheck/suggestions/[1]/suggestion
Stack Trace:
java.lang.RuntimeException:
I did notice that according to the post you linked to, Spring also
requires an additional step beyond a pull-request to document license
compliance:
-
I skirted over this in the article, but it's an important point. In
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212090#comment-13212090
]
Robert Muir commented on LUCENE-3807:
-
I think we should go with a simpler solution
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1775/
1 tests failed.
FAILED:
org.apache.solr.handler.component.SpellCheckComponentTest.testThresholdTokenFrequency
Error Message:
Path not found: /spellcheck/suggestions/[1]/suggestion
Stack Trace:
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212130#comment-13212130
]
Simon Willnauer commented on LUCENE-3807:
-
just drop it I will replace that stuff
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12477/
1 tests failed.
FAILED:
org.apache.solr.handler.component.SpellCheckComponentTest.testThresholdTokenFrequency
Error Message:
Path not found: /spellcheck/suggestions/[1]/suggestion
Stack Trace:
java.lang.RuntimeException:
[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212175#comment-13212175
]
David Smiley commented on LUCENE-3795:
--
I created a branch
just committed a fix for this
On Mon, Feb 20, 2012 at 11:18 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12477/
1 tests failed.
FAILED:
[
https://issues.apache.org/jira/browse/LUCENE-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3800:
--
Attachment: LUCENE-3800.patch
Improved patch with some minor things fixed:
- Better test for
[
https://issues.apache.org/jira/browse/SOLR-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212205#comment-13212205
]
Greg Bowyer commented on SOLR-3079:
---
My mistake, I tend to work from the git mirrors as
[
https://issues.apache.org/jira/browse/LUCENE-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212249#comment-13212249
]
Jan Høydahl commented on LUCENE-2566:
-
This should be possible to backport to 3.x. I
GitHub user prb synchronized the pull request at
https://github.com/apache/lucene-solr/pull/1
Branch 3x
The build will fail without this (tiny) change because the solr/examples/work
directory doesn't exist if examples haven't been run. Also, some notation
should be made about the version
GitHub user JackDanger synchronized the pull request at
https://github.com/apache/lucene-solr/pull/2
Fixing typo in example schema: 'salves' = 'slaves'
Just a typo in a comment. Safe to merge.
You can merge this pull request into a Git repository by running
$ git pull
GitHub user astubbs synchronized the pull request at
https://github.com/apache/lucene-solr/pull/3
Better logging of undefined field error (SOLR-3077)
https://issues.apache.org/jira/browse/SOLR-3077
You can merge this pull request into a Git repository by running
$ git pull
[
https://issues.apache.org/jira/browse/SOLR-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi resolved SOLR-2909.
--
Resolution: Fixed
Fix Version/s: 4.0
3.6
trunk: Committed revision
[
https://issues.apache.org/jira/browse/LUCENE-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212290#comment-13212290
]
Mark Miller commented on LUCENE-3806:
-
If we decide we want the css animated button,
[
https://issues.apache.org/jira/browse/LUCENE-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212295#comment-13212295
]
Mark Miller commented on LUCENE-3806:
-
I pub'd the css button - it's growing on me.
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1777/
1 tests failed.
REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch
Error Message:
Not all shards are ACTIVE
Stack Trace:
junit.framework.AssertionFailedError: Not all shards are ACTIVE
Adding some more logging around this.
On Feb 20, 2012, at 10:41 PM, Apache Jenkins Server wrote:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1777/
1 tests failed.
REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch
Error Message:
Not
Build: https://builds.apache.org/job/Lucene-trunk/1835/
1 tests failed.
REGRESSION: org.apache.lucene.search.TestTermVectors.testKnownSetOfDocuments
Error Message:
null
Stack Trace:
junit.framework.AssertionFailedError
at
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12480/
1 tests failed.
REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch
Error Message:
Not all shards are ACTIVE - found a shard that is: down
Stack Trace:
junit.framework.AssertionFailedError: Not all
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212391#comment-13212391
]
Trejkaz commented on LUCENE-2348:
-
The IndexReaderContext API in Lucene trunk looks like
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212423#comment-13212423
]
Uwe Schindler commented on LUCENE-2348:
---
The new AtomicReaderContexts passed to
[
https://issues.apache.org/jira/browse/LUCENE-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212430#comment-13212430
]
Simon Willnauer commented on LUCENE-3807:
-
bq. I think we should go with a
94 matches
Mail list logo
