[
https://issues.apache.org/jira/browse/SOLR-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker resolved SOLR-8374.
-
Resolution: Duplicate
Hi Romit,
This looks like a duplicate of SOLR-7108 which was fixed in Solr 5
I agree with Rob on this — delete the ‘jar’s from git history, for all the
reasons Rob said. If someone wants to attempt to actually *build* an old
release, and thus needs the jars, then they are welcome to use ASF SVN
archives for that purpose instead, and even then apparently it will be a
challe
[
https://issues.apache.org/jira/browse/SOLR-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042671#comment-15042671
]
Anshum Gupta commented on SOLR-8359:
Thanks Jason and Mike. I'll take a look at this.
[
https://issues.apache.org/jira/browse/LUCENE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042672#comment-15042672
]
David Smiley commented on LUCENE-6919:
--
+1 because it seems to perform better. And
[
https://issues.apache.org/jira/browse/SOLR-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Tan updated SOLR-8377:
-
Attachment: 1.patch
Patch removing the loop in question.
> Unnecessary for loop in ReplicaAssigner.tryAllP
Kelvin Tan created SOLR-8377:
Summary: Unnecessary for loop in
ReplicaAssigner.tryAllPermutations()
Key: SOLR-8377
URL: https://issues.apache.org/jira/browse/SOLR-8377
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-8260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042651#comment-15042651
]
David Smiley commented on SOLR-8260:
bq. will update.
Looking forward to that still ;-
[
https://issues.apache.org/jira/browse/SOLR-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042647#comment-15042647
]
Mike Drob commented on SOLR-8359:
-
+1 LGTM
> Restrict child classes from using parent logg
Bill Bell created SOLR-8376:
---
Summary: Jetty 9.2.14.v20151106 upgrade from 9.2.11
Key: SOLR-8376
URL: https://issues.apache.org/jira/browse/SOLR-8376
Project: Solr
Issue Type: Bug
Affects Versi
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15115/
Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED:
org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication
Error Message:
[/home/jenkins/workspace/Lucene-Solr-trunk-
This is good ! :)
just so that you know, make sure that your key is up on id.apache.org too!
I struggled with that for almost a day during my first release (I believe I
added that to the wiki too).
On Sat, Dec 5, 2015 at 12:59 AM, Upayavira wrote:
>
>
> On Fri, Dec 4, 2015, at 06:10 PM, Michael
[
https://issues.apache.org/jira/browse/SOLR-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Tan updated SOLR-8375:
-
Attachment: patch.txt
Patch attached against trunk.
> ReplicaAssigner rejects valid positions
> --
Kelvin Tan created SOLR-8375:
Summary: ReplicaAssigner rejects valid positions
Key: SOLR-8375
URL: https://issues.apache.org/jira/browse/SOLR-8375
Project: Solr
Issue Type: Bug
Componen
[
https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042528#comment-15042528
]
Uwe Schindler edited comment on LUCENE-6920 at 12/5/15 1:14 AM:
---
[
https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-6920:
--
Attachment: LUCENE-6920.patch
New patch with permission removed. Solr never had this permission
[
https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042522#comment-15042522
]
Uwe Schindler commented on LUCENE-6920:
---
Thanks for the hint. There is another getC
[
https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042515#comment-15042515
]
Robert Muir commented on LUCENE-6920:
-
+1, looks good.
We may also try removing the
[
https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-6920:
--
Attachment: LUCENE-6920.patch
Patch. All tests pass.
> Simplify callable function checks in Ex
Uwe Schindler created LUCENE-6920:
-
Summary: Simplify callable function checks in Expression module
Key: LUCENE-6920
URL: https://issues.apache.org/jira/browse/LUCENE-6920
Project: Lucene - Core
The only downside is GitHub is a convenient way to run blame, etc. It's
very convenient for sleuthing through code. (If only their search wasn't
abysmal in terms of relevancy, but I digress)
Is the more systemic problem large binaries checked in I'm the past? Can we
do any surgery to svn or git to
[
https://issues.apache.org/jira/browse/SOLR-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042452#comment-15042452
]
Erick Erickson commented on SOLR-8374:
--
How is the ping request generated? This is pro
Hi,
This looks like a good idea to me. Maybe we just have a limited amount of
history and branches in Git/Github, so people can work and create pull
requests. Nobody wants to create pull request on a very old branch or against a
revision years ago.
Maybe Infra can mirror only the last 2 years
In the original report, the Infrastructure team said that throwing
memory at it did not solve the problem. And I believe they threw *a lot*
of memory at it.
There may well be other options - just needs someone to dive in and
look!
Upayavira
On Fri, Dec 4, 2015, at 11:10 PM, Alexandre Rafalovitch
Maybe a silly question, but has anybody actually looked into the
git-svn itself. E.g. talking to git-svn team with our example to help
them troubleshoot the link. Or run a test sync under profiler.
Also, it is running into OOM, but how big is a system doing the sync.
If the issue is upgrading the s
As I said earlier - our history is inside the ASF SVN repo. The only way
our history would be lost would be if the whole repo was deleted, which
I suspect won't happen for a while. So even if we imported a snapshot
over to Git, our full SVN history is immutably stored in SVN (even if we
did svn rm
[
https://issues.apache.org/jira/browse/SOLR-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romit Singhai updated SOLR-8374:
Summary: Issue with _text_ field in schema file (was: Issue with _text_
type in schema file)
> Issu
Romit Singhai created SOLR-8374:
---
Summary: Issue with _text_ type in schema file
Key: SOLR-8374
URL: https://issues.apache.org/jira/browse/SOLR-8374
Project: Solr
Issue Type: Bug
Comp
[
https://issues.apache.org/jira/browse/LUCENE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042367#comment-15042367
]
Ryan Ernst commented on LUCENE-6919:
+1 to the idea
> Change the Scorer API to expos
Many old builds will also have problems even with a git checkout. If you
actually wanted to try and build them it would be much more sane to work
from the SVN history I'd hope we can retain.
Mark
On Fri, Dec 4, 2015 at 4:55 PM Robert Muir wrote:
> On Fri, Dec 4, 2015 at 4:25 PM, Dawid Weiss wr
[
https://issues.apache.org/jira/browse/SOLR-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-7304:
-
Attachment: SOLR-7304.patch
Here is a patch with the fix. I will commit this next week if everything
chec
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5445/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseParallelGC
1 tests failed.
FAILED: org.apache.solr.handler.TestReplicationHandler.doTestStressReplication
Error Message:
[index.20151204232218770, index.20151204232219448, index.properti
On Fri, Dec 4, 2015 at 4:25 PM, Dawid Weiss wrote:
>> I don't think jar files are 'history' and it was a mistake we had so
>> many in source control before we cleaned that up. it is much better
>> without them.
>
> Depends how you look at it. If your goal is to be able to actually
> build ancient
I know Infra has tried a number of things to resolve this, to no avail. But
did we try "git-svn --revision=" to only mirror "post-LUCENE-3930" (ivy,
r1307099)? Or if that's not lean enough for the git-svn mirror to work, then
cut off when 4.x was branched or whenever. The hope would be to giv
> Does anyone know of a link to this git-svn issue? Is it a known
issue? If there's something simple we can do (remove old jars from
our svn history, remove old branches), maybe we can sidestep the issue
and infra will allow it to keep running?
I believe it is partially covered under
https://iss
Oh, nevermind -- I think I know why:
License
GNU Library or Lesser General Public License version 2.0 (LGPLv2)
D.
On Fri, Dec 4, 2015 at 10:33 PM, Dawid Weiss wrote:
> It'd be cool to actually reintegrate ancient CVS history as well (I
> think not all of it was moved to SVN).
>
> https://source
It'd be cool to actually reintegrate ancient CVS history as well (I
think not all of it was moved to SVN).
https://sourceforge.net/projects/lucene/
D.
On Fri, Dec 4, 2015 at 10:30 PM, Upayavira wrote:
> Even if we moved to git and did an svn rm on
> https://svn.apache.org/repos/asf/lucene/dev,
Even if we moved to git and did an svn rm on
https://svn.apache.org/repos/asf/lucene/dev, the entire history of Lucene would
remain in the ASF Subversion repository. Nothing we can do to prevent that!!
Upayavira
On Fri, Dec 4, 2015, at 09:26 PM, Gus Heck wrote:
> If we moved to git would a read
[
https://issues.apache.org/jira/browse/LUCENE-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042258#comment-15042258
]
Michael McCandless commented on LUCENE-6837:
[~cm] are you planning to backpo
> I don't think jar files are 'history' and it was a mistake we had so
> many in source control before we cleaned that up. it is much better
> without them.
Depends how you look at it. If your goal is to be able to actually
build ancient versions then dropping those JARs is going to be a real
pain
If we moved to git would a read only svn for older versions still exist? If
so no reason to keep any jars at all in git.
On Dec 4, 2015 4:22 PM, "Robert Muir" wrote:
> On Fri, Dec 4, 2015 at 4:14 PM, Dawid Weiss wrote:
> >> [...] several GBs unless we remove those JARs from our history.
> >
> >
[
https://issues.apache.org/jira/browse/SOLR-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-8373:
---
Attachment: SOLR-8373.patch
I'm testing this patch that lets the clients ignore the coo
On Fri, Dec 4, 2015 at 4:14 PM, Dawid Weiss wrote:
>> [...] several GBs unless we remove those JARs from our history.
>
> 1) History is important, don't dump it.
I don't think jar files are 'history' and it was a mistake we had so
many in source control before we cleaned that up. it is much bette
Ishan Chattopadhyaya created SOLR-8373:
--
Summary: KerberosPlugin: Using multiple nodes on same machine
leads clients to fetch TGT for every request
Key: SOLR-8373
URL: https://issues.apache.org/jira/browse/SO
[
https://issues.apache.org/jira/browse/LUCENE-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042248#comment-15042248
]
Michael McCandless commented on LUCENE-6908:
Those benchmark results are nice
> [...] several GBs unless we remove those JARs from our history.
1) History is important, don't dump it.
2) git isn't dumb -- git clone -b master --single-branch would only
fetch what's actually needed/ referenced. We could split the history
into "pre-ivy" and "post-ivy" branches so that fetching
Ouch... not having an official mirror would be a huge burden on those of us
managing org-specific forks. :(
On Fri, Dec 4, 2015 at 3:57 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> Hello devs,
>
> The infra team has notified us (Lucene/Solr) that in 26 days our
> git-svn mirror wi
[
https://issues.apache.org/jira/browse/SOLR-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042237#comment-15042237
]
James Dyer edited comment on SOLR-7304 at 12/4/15 9:06 PM:
---
Attac
[
https://issues.apache.org/jira/browse/SOLR-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-7304:
-
Attachment: SOLR-7304.patch
Attached is a patch with a failing unit test. To reproduce this issue we use
[
https://issues.apache.org/jira/browse/SOLR-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated SOLR-8292:
Attachment: SOLR-8292.patch
Here's the start of a patch to get better logging around what is happening.
I th
On Fri, Dec 4, 2015, at 08:59 PM, Michael McCandless wrote:
> On Fri, Dec 4, 2015 at 2:29 PM, Upayavira wrote:
> >
> > On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote:
> >>
> >> On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote:
> >>
> >> > As a first time Release Manager
> >>
> >> Th
[
https://issues.apache.org/jira/browse/SOLR-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-7304:
-
Summary: Spellcheck.collate Sometimes Invalidates Range Queries (was:
SyntaxError in SpellcheckComponent)
On Fri, Dec 4, 2015 at 2:29 PM, Upayavira wrote:
>
> On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote:
>>
>> On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote:
>>
>> > As a first time Release Manager
>>
>> Thanks Upayavira!
>>
>> But please, please, please take advantage of your newness
Hello devs,
The infra team has notified us (Lucene/Solr) that in 26 days our
git-svn mirror will be turned off, because running it consumes too
many system resources, affecting other projects, apparently because of
a memory leak in git-svn.
Does anyone know of a link to this git-svn issue? Is it
[
https://issues.apache.org/jira/browse/SOLR-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042220#comment-15042220
]
David Smiley commented on SOLR-7495:
Ok; you could use two fields then, one for sorting
Yonik Seeley created SOLR-8372:
--
Summary: Canceled recovery can lead to data loss
Key: SOLR-8372
URL: https://issues.apache.org/jira/browse/SOLR-8372
Project: Solr
Issue Type: Bug
Re
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/14818/
Java: 32bit/jdk1.8.0_66 -client -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.handler.TestReplicationHandler.doTestStressReplication
Error Message:
timed out waiting for collection1 startAt time to exceed: Fri Dec 04 16:04
[
https://issues.apache.org/jira/browse/LUCENE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer closed LUCENE-3341.
--
Resolution: Not A Problem
We can do what the user wants, using DirectSolrSpellChecker and setting the
[
https://issues.apache.org/jira/browse/SOLR-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042147#comment-15042147
]
Peter Ciuffetti commented on SOLR-7495:
---
The multi value work around is not available
[
https://issues.apache.org/jira/browse/LUCENE-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved LUCENE-6912.
--
Resolution: Fixed
> Grouping's Collectors should have smart needsScores()
> ---
[
https://issues.apache.org/jira/browse/LUCENE-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042062#comment-15042062
]
ASF subversion and git services commented on LUCENE-6912:
-
Commit
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.4-Linux/316/
Java: 64bit/jdk1.7.0_80 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Error from server at https://127.0.0.1:36810/bg_vnk/nd/awholynewcollectio
On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote:
> On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote:
>
> > As a first time Release Manager
>
> Thanks Upayavira!
>
> But please, please, please take advantage of your newness to this, to
> edit https://wiki.apache.org/lucene-java/Rele
[
https://issues.apache.org/jira/browse/LUCENE-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042039#comment-15042039
]
ASF subversion and git services commented on LUCENE-6912:
-
Commit
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/233/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC
1 tests failed.
FAILED: org.apache.solr.handler.TestReplicationHandler.doTestStressReplication
Error Message:
timed out waiting for collection1 startAt time to exce
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/1036/
2 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Captured an uncaught exception in thread: Thread[id=32047, name=collection4,
state=RUNNABLE, group=TGRP-CollectionsAPIDistrib
[
https://issues.apache.org/jira/browse/LUCENE-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke resolved LUCENE-6910.
-
Resolution: Fixed
Fix Version/s: 5.5
Trunk
> fix 2 inte
[
https://issues.apache.org/jira/browse/LUCENE-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041965#comment-15041965
]
ASF subversion and git services commented on LUCENE-6910:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer resolved SOLR-6271.
--
Resolution: Fixed
Fix Version/s: 5.5
Thanks Igor & Fabiano for reporting this one.
> ConjunctionS
[
https://issues.apache.org/jira/browse/LUCENE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-6919:
-
Attachment: LUCENE-6919.patch
Here is the (hacky) patch that I used for the benchmark.
This woul
On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote:
> As a first time Release Manager
Thanks Upayavira!
But please, please, please take advantage of your newness to this, to
edit https://wiki.apache.org/lucene-java/ReleaseTodo when things are
confusing/missing/etc.!
Being new to something is unf
Github user asfgit closed the pull request at:
https://github.com/apache/lucene-solr/pull/135
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
[
https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041891#comment-15041891
]
ASF GitHub Bot commented on SOLR-6271:
--
Github user asfgit closed the pull request at:
Adrien Grand created LUCENE-6919:
Summary: Change the Scorer API to expose an iterator instead of
extending DocIdSetIterator
Key: LUCENE-6919
URL: https://issues.apache.org/jira/browse/LUCENE-6919
Pro
[
https://issues.apache.org/jira/browse/SOLR-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-8371:
--
Attachment: SOLR-8371.patch
> Try and prevent too many recovery requests from stacking up and clean up so
[
https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041855#comment-15041855
]
Mark Miller commented on SOLR-8368:
---
I keep trying to think of reasons we don't have to d
[
https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041831#comment-15041831
]
ASF subversion and git services commented on SOLR-6271:
---
Commit 17180
[
https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041829#comment-15041829
]
ASF subversion and git services commented on SOLR-6271:
---
Commit 17179
[
https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-6271:
-
Attachment: SOLR-6271.patch
Here is an updated patch with a slightly different unit test.
This is a trivia
[
https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer reassigned SOLR-6271:
Assignee: James Dyer
> ConjunctionSolrSpellChecker wrong check for same string distance
> --
Github user Lakedaemon closed the pull request at:
https://github.com/apache/lucene-solr/pull/34
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
[
https://issues.apache.org/jira/browse/SOLR-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-8371:
--
Attachment: SOLR-8371.patch
patch ive started playing with attatched
> Try and prevent too many recovery
Mark Miller created SOLR-8371:
-
Summary: Try and prevent too many recovery requests from stacking
up and clean up some faulty logic.
Key: SOLR-8371
URL: https://issues.apache.org/jira/browse/SOLR-8371
Pro
[
https://issues.apache.org/jira/browse/SOLR-8364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041747#comment-15041747
]
James Dyer commented on SOLR-8364:
--
Ok, looking closely at the log, I see this:
{noformat
[
https://issues.apache.org/jira/browse/LUCENE-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041744#comment-15041744
]
ASF subversion and git services commented on LUCENE-6910:
-
Commit
Thanks Varun.
As a first time Release Manager, I'm currently working through the steps
needed to build a release. I'll call a vote as soon as I have uploaded
artifacts that are passing smoke tests.
Upayavira
On Fri, Dec 4, 2015, at 07:16 AM, Varun Thacker wrote:
> Hi Upayavira,
>
> I have commit
[
https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041693#comment-15041693
]
Mark Miller commented on SOLR-8368:
---
Of course, replaying a tlog when everything works we
[
https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041691#comment-15041691
]
Mark Miller commented on SOLR-8368:
---
It could take a long time, but it's simply necessary
[
https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041686#comment-15041686
]
Mike Drob commented on SOLR-8368:
-
This could take a long time, though, right? Is there any
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15111/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Error from server at http://127.0.0.1:34822/xukg/i/awholynewcollection_0: non
ok st
[
https://issues.apache.org/jira/browse/SOLR-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-8366.
-
Resolution: Fixed
Assignee: Shalin Shekhar Mangar
> ConcurrentUpdateSolrClien
[
https://issues.apache.org/jira/browse/SOLR-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041641#comment-15041641
]
ASF subversion and git services commented on SOLR-8366:
---
Commit 17179
[
https://issues.apache.org/jira/browse/SOLR-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-8366:
Summary: ConcurrentUpdateSolrClient attempts to use response's content type
as charse
[
https://issues.apache.org/jira/browse/SOLR-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041635#comment-15041635
]
ASF subversion and git services commented on SOLR-8366:
---
Commit 17179
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/5313/
Java: 64bit/jdk1.8.0_66 -XX:-UseCompressedOops -XX:+UseParallelGC
1 tests failed.
FAILED: org.apache.solr.cloud.SyncSliceTest.test
Error Message:
expected:<5> but was:<4>
Stack Trace:
java.lang.AssertionError: expected:<5> but
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/14816/
Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Error from server at http://127.0.0.1:46245/_ra/b/awholynewcollecti
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/678/
18 tests failed.
FAILED: org.apache.solr.TestDistributedGrouping.test
Error Message:
IOException occured when talking to server at:
https://127.0.0.1:54842//collection1
Stack Trace:
org.apache.solr.client.solrj.SolrServerE
Jan Høydahl created SOLR-8370:
-
Summary: Display Similarity Factory in use in Schema-Browser
Key: SOLR-8370
URL: https://issues.apache.org/jira/browse/SOLR-8370
Project: Solr
Issue Type: Improvem
[
https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-6918.
--
Resolution: Fixed
Fix Version/s: Trunk
> LRUQueryCache.onDocIdSetEviction should not be
[
https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041557#comment-15041557
]
ASF subversion and git services commented on LUCENE-6918:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041509#comment-15041509
]
ASF subversion and git services commented on LUCENE-6918:
-
Commit
1 - 100 of 107 matches
Mail list logo
