Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-java7/565/
No tests ran.
Build Log:
[...truncated 9019 lines...]
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected
termination of the channel
hudson.remoting.RequestAbortedException:
hudson.remoting.Request
[
https://issues.apache.org/jira/browse/SOLR-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3933:
--
Priority: Critical (was: Major)
> Distributed commits are not guaranteed to be ordered within a req
[
https://issues.apache.org/jira/browse/SOLR-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479573#comment-13479573
]
Otis Gospodnetic commented on SOLR-2305:
[~mbonaci] comments:
* please remove @auth
On Thu, Oct 18, 2012 at 4:53 PM, Mark Miller wrote:
> I don't think a 4.0.1 would be strange at all.
I just think it would be strange since there aren't really any serious
bugs yet in the lucene CHANGES.txt? I also don't think there has been
enough time for anyone to actually find any bugs, its o
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: LUCENE-4488.patch
Patch also supporting OpenJDK.
> Jenkins builds
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479502#comment-13479502
]
Uwe Schindler commented on LUCENE-4488:
---
I also have to add "OpenJDK" to the regex.
I don't think a 4.0.1 would be strange at all.
4.X is essentially trunk to me now. I would put in changes that I want
to bake for future 4.1, 4.2, 4.3, etc changes.
When you have bad bugs, you don't want to worry about what's baking -
you just want to put out a bug fix release.
It's also a signa
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: LUCENE-4488.patch
Patch that only enabled heapdumps if the property "java.vm.name"
Thanks :)
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 7:29 PM, wrote:
> Author: rmuir
> Date: Thu Oct 18 23:29:29 2012
> New Revision: 1399923
>
> URL: http://svn.apache.org/viewvc?rev=1399923&view=rev
> Log:
> use _TestUtil helper instead of lots of coe
>
> Modifie
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: LUCENE-4488.patch
> Jenkins builds aren't saving heap dumps anymore
>
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: (was: LUCENE-4488.patch)
> Jenkins builds aren't saving heap dumps anymore
There is a helper for this in _TestUtil. I'll commit a fix.
On Thu, Oct 18, 2012 at 3:01 PM, wrote:
> Author: mikemccand
> Date: Thu Oct 18 22:01:22 2012
> New Revision: 1399883
>
> URL: http://svn.apache.org/viewvc?rev=1399883&view=rev
> Log:
> make test easier if it get SimpleText postings for
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: (was: LUCENE-4488.patch)
> Jenkins builds aren't saving heap dumps anymore
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: LUCENE-4488.patch
> Jenkins builds aren't saving heap dumps anymore
>
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: LUCENE-4488.patch
Patch that fixes the -Dargs=... override. This is similar to the
[
https://issues.apache.org/jira/browse/SOLR-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479456#comment-13479456
]
Hoss Man commented on SOLR-3963:
Bill: i'm not understanding the error message you've ppost
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479447#comment-13479447
]
Uwe Schindler commented on LUCENE-4488:
---
The patch has another problem: If you pass
On Thu, Oct 18, 2012 at 2:51 PM, Mark Miller wrote:
> I suppose it depends. If people think we are on track for a 4.1 soon,
> perhaps we should skip 4.0.1 and just do a fairly fast 4.1.
>
> I think people would have to feel comfortable about some of the 4.1
> changes - that nothing is that invasiv
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4488:
--
Attachment: LUCENE-4488.patch
Here a patch that enabled heap-dumps when you run "ant jenkins-h
OK I committed a fix ...
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 5:59 PM, Michael McCandless
wrote:
> SimpleText + SerialMergeScheduler + tons of docs ... a slow combination ...
>
> I'll fix.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Oct
SimpleText + SerialMergeScheduler + tons of docs ... a slow combination ...
I'll fix.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 4:45 PM, Apache Jenkins Server
wrote:
> Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-4.x/68/
>
> 2 tests failed.
> REGRE
I suppose it depends. If people think we are on track for a 4.1 soon,
perhaps we should skip 4.0.1 and just do a fairly fast 4.1.
I think people would have to feel comfortable about some of the 4.1
changes - that nothing is that invasive. Otherwise it would probably
be nice to do a bug fix only 4.
[
https://issues.apache.org/jira/browse/SOLR-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3933:
--
Attachment: SOLR-3933.patch
Here is patch with a fixed test and fix. Also includes fix for SOLR-3932.
[
https://issues.apache.org/jira/browse/SOLR-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-3943.
---
Resolution: Invalid
i was out in the weeds trying to track down something else...
> W
[
https://issues.apache.org/jira/browse/SOLR-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3939:
--
Attachment: SOLR-3939.patch
Here is a patch that should address point 1 - point 2 still has no fix or te
[
https://issues.apache.org/jira/browse/SOLR-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479350#comment-13479350
]
Mark Miller commented on SOLR-3939:
---
Sorry - not starting versions - recent versions.
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-4.x/68/
2 tests failed.
REGRESSION: org.apache.lucene.index.TestBagOfPostings.test
Error Message:
Test abandoned because suite timeout was reached.
Stack Trace:
java.lang.Exception: Test abandoned because suite timeout was reached.
[
https://issues.apache.org/jira/browse/SOLR-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479332#comment-13479332
]
Marko Bonaci commented on SOLR-2305:
[~erickerickson]
Isn't the number of votes enough
[
https://issues.apache.org/jira/browse/SOLR-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479322#comment-13479322
]
Mark Miller commented on SOLR-3939:
---
Joel: It could just be timing - live nodes are likel
[
https://issues.apache.org/jira/browse/LUCENE-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-4483:
-
Fix Version/s: (was: 4.1)
4.0.1
> Make Term constructor javadoc refer
[
https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot resolved LUCENE-1345.
--
Resolution: Won't Fix
Enough time has passed to show that there is not sufficient interestin t
[
https://issues.apache.org/jira/browse/LUCENE-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479246#comment-13479246
]
Simon Willnauer commented on LUCENE-4486:
-
bq.I am wondering about if it is possi
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux/1836/
Java: 64bit/ibm-j9-jdk6
-Xjit:exclude={org/apache/lucene/util/fst/FST.pack(IIF)Lorg/apache/lucene/util/fst/FST;}
All tests passed
Build Log:
[...truncated 1273 lines...]
[junit4:junit4] ERROR: JVM J0 ended with an exceptio
I'm just getting into Solr, so take my opinion as the opinion of an
uninformed noob. A recent post on the list had this text:
On Thu, Oct 18, 2012 at 5:06 PM, Erick Erickson wrote:
> Question: There's been some confusion about core admin commands lately
> on the users list since "load" is not imp
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479214#comment-13479214
]
Uwe Schindler commented on LUCENE-4488:
---
OK, I will come up with a patch later this
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479211#comment-13479211
]
Michael McCandless commented on LUCENE-4488:
OK I committed @Ignore of TestPa
OK I committed the fixes to smoke tester for this ...
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 12:34 PM, Uwe Schindler wrote:
>> Hmm I'm confused ... I changed the script (locally) to require
>> solr/SYSTEM_REQUIREMENTS.txt to exist ... but when I run "ant nightly-
[
https://issues.apache.org/jira/browse/LUCENE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-4182.
-
Resolution: Fixed
Fix Version/s: 5.0
4.1
Lucene Fields: New
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479175#comment-13479175
]
Uwe Schindler commented on LUCENE-4488:
---
bq. If it's hotspot then a crash should be
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479149#comment-13479149
]
Dawid Weiss commented on LUCENE-4488:
-
If it's hotspot then a crash should be (it's t
> Not sure which test(s) we should use for this ... I guess we'd want a
> fixed seed ... and things like concurrent merges could mess up the
> numbers if the threads schedule differently / IO gets slower ... hrmm.
Yeah, the benchmarks I was referring to are pretty static (no
randomness). But even
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479145#comment-13479145
]
Michael McCandless commented on LUCENE-4488:
OK it's TestPackedInts.testIntOv
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479133#comment-13479133
]
Michael McCandless commented on LUCENE-4488:
OK this seems to repro the heap
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479125#comment-13479125
]
Uwe Schindler commented on LUCENE-4488:
---
Cool, which test?
> Jenki
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479124#comment-13479124
]
Michael McCandless commented on LUCENE-4488:
OK I managed to get a heap dump!
> Hmm I'm confused ... I changed the script (locally) to require
> solr/SYSTEM_REQUIREMENTS.txt to exist ... but when I run "ant nightly-
> smoke" it fails on artifact apache-solr-5.0.0.tgz.
That is easy to explain:
The *binary* tgz contains only solr, so the root dir of the tar file is Solr
The *
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479123#comment-13479123
]
Robert Muir commented on LUCENE-4488:
-
Can you also run the test with verbose to see
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479119#comment-13479119
]
Michael McCandless commented on LUCENE-4488:
If I also add -XX:HeapDumpPath=/
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479115#comment-13479115
]
Robert Muir commented on LUCENE-4488:
-
If someone can come up with the commandline to
On Wed, Oct 17, 2012 at 2:59 PM, Dawid Weiss
wrote:
> Just a though -- we have a benchmark regression test that attempts to
> estimate the 'minimum required memory before it hits an OOM' for a
> known task (a fixed data set for clustering). Essentially we do a
> binary search between not hitting a
On Wed, Oct 17, 2012 at 2:55 PM, Dawid Weiss
wrote:
>> repros if I use randomized runner but not if I use JUnit's runner.
>
> Maybe it's close enough to the memory limit to be a non-significant
> difference? You could try decreasing memory to see when JUnit's runner
> starts failing for the same s
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479110#comment-13479110
]
Uwe Schindler commented on LUCENE-4488:
---
Can you run the full test suite from root
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479108#comment-13479108
]
Uwe Schindler commented on LUCENE-4488:
---
Maybe it is already fixed. I disabled the
[
https://issues.apache.org/jira/browse/LUCENE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479106#comment-13479106
]
Michael McCandless commented on LUCENE-4488:
Hmmm when I run:
{noformat}
a
[
https://issues.apache.org/jira/browse/LUCENE-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Dimitrov Vasilev closed LUCENE-4490.
-
Resolution: Invalid
Yes the reason is the Analyzer. With WhitespaceAnalyzer ther
[
https://issues.apache.org/jira/browse/LUCENE-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479098#comment-13479098
]
Simon Willnauer commented on LUCENE-3846:
-
FYI - I cleaned up the code & tests, s
[
https://issues.apache.org/jira/browse/LUCENE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479097#comment-13479097
]
Simon Willnauer commented on LUCENE-4472:
-
Committed to trunk in revision 1399712
[
https://issues.apache.org/jira/browse/LUCENE-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479088#comment-13479088
]
Michael McCandless commented on LUCENE-4490:
I think the problem is 'a' is a
[
https://issues.apache.org/jira/browse/LUCENE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479087#comment-13479087
]
Simon Willnauer commented on LUCENE-4472:
-
I will go ahead and commit this. I wil
[
https://issues.apache.org/jira/browse/LUCENE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479080#comment-13479080
]
Michael McCandless commented on LUCENE-4472:
Thanks Simon, looks good!
Ivan Dimitrov Vasilev created LUCENE-4490:
-
Summary: TermPositions misses some terms in some cases
Key: LUCENE-4490
URL: https://issues.apache.org/jira/browse/LUCENE-4490
Project: Lucene - Core
I'm going to be doing some work on this issue. The background here is
that there is a use-case for having 10-15K cores on a single server
that follow the pattern
open-search-close
where the application is tolerant of the inherent problems with speed
for the first-time queries after a core is opened
[
https://issues.apache.org/jira/browse/LUCENE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-4472:
Attachment: LUCENE-4472.patch
fair enough mike. I think as long as we don't have a modular
Hi Erick!
> The usual process for contributions from people who aren't committers is to
> create a JIRA and attach a patch. One of the committers then picks up the
> patch and commits it to the repo. Sometimes you have to nudgh ..
>
Great, will do.
> Here's a primer on creating patches:
>
> htt
The usual process for contributions from people who aren't committers is to
create a JIRA and attach a patch. One of the committers then picks up the
patch and commits it to the repo. Sometimes you have to nudgh ..
Here's a primer on creating patches:
http://wiki.apache.org/solr/HowToContribute#C
OK for now I fixed it to only check that SYSTEM_REQUIREMENTS.txt
exists for Lucene artifacts ... once we sort out where it's suppose to
be for Solr we can re-enable.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 7:54 AM, Michael McCandless
wrote:
> Hmm I'm confused ...
I've also only been porting to 4.1 so far (I'm assuming we'll release
4.1 soonish) but if we do a 4.0.1 I can re-visit ...
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 8:28 AM, Mark Miller wrote:
> Initially, I started adding a 4.01 fix version to issues I thought shou
Argh, still no heap dump.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 8:13 AM, wrote:
> Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java6-64-test-only/10239/
>
> 1 tests failed.
> REGRESSION:
> org.apache.lucene.search.TestTimeLimitingCollector.testSearchMul
Initially, I started adding a 4.01 fix version to issues I thought should go in
if we did 4.01 - but then I could not resolve those issues without back porting
- which I didn't want to do in case we jumped to 4.1 or something - call me
lazy :) So I started labeling until it became clear we would
Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java6-64-test-only/10239/
1 tests failed.
REGRESSION:
org.apache.lucene.search.TestTimeLimitingCollector.testSearchMultiThreaded
Error Message:
Captured an uncaught exception in thread: Thread[id=78, name=Thread-49,
state=RUNNABLE, group=TGRP-
[
https://issues.apache.org/jira/browse/SOLR-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren updated SOLR-3965:
-
Affects Version/s: 4.0
> CoreAdminHandler does not do "property expansion" on values wren creating new
Sami Siren created SOLR-3965:
Summary: CoreAdminHandler does not do "property expansion" on
values wren creating new core
Key: SOLR-3965
URL: https://issues.apache.org/jira/browse/SOLR-3965
Project: Solr
Hmm I'm confused ... I changed the script (locally) to require
solr/SYSTEM_REQUIREMENTS.txt to exist ... but when I run "ant
nightly-smoke" it fails on artifact apache-solr-5.0.0.tgz.
And then when I look in that tgz I see SYSTEM_REQUIREMENTS.txt in the
root directory of that archive (ie, side by
[
https://issues.apache.org/jira/browse/SOLR-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478929#comment-13478929
]
Markus Jelsma commented on SOLR-3705:
-
I took me a while to get back to this. The probl
Woops, I'll fix!
Mike McCandless
http://blog.mikemccandless.com
On Thu, Oct 18, 2012 at 2:22 AM, Uwe Schindler wrote:
> Hi,
>
> the system requirements TXT file is in the SOLR src-tgz, but as its
> Sol-specfific, it is in the solr/ subfolder, maybe that’s the problem here. I
> think this scr
[
https://issues.apache.org/jira/browse/LUCENE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478911#comment-13478911
]
Michael McCandless commented on LUCENE-4182:
+1
> DocumentsW
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478903#comment-13478903
]
Nathan Visagan edited comment on SOLR-3960 at 10/18/12 10:57 AM:
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478903#comment-13478903
]
Nathan Visagan edited comment on SOLR-3960 at 10/18/12 10:56 AM:
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Visagan updated SOLR-3960:
-
Summary: Searching: PostFilter plugins ignored by solr cloud for queries
with grouping (was: Sear
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478903#comment-13478903
]
Nathan Visagan commented on SOLR-3960:
--
You are correct. Its only happening with group
[
https://issues.apache.org/jira/browse/LUCENE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-4182:
Attachment: LUCENE-4182.patch
here is a patch fixing the upperbound and adding some more i
[
https://issues.apache.org/jira/browse/LUCENE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478870#comment-13478870
]
Simon Willnauer commented on LUCENE-4182:
-
Ok guys, I think I have found the prob
milesli created SOLR-3964:
-
Summary: Solr does not return error, even though create collection
unsuccessfully
Key: SOLR-3964
URL: https://issues.apache.org/jira/browse/SOLR-3964
Project: Solr
Issue
83 matches
Mail list logo
