[jira] [Comment Edited] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041236#comment-15041236 ] Mikhail Khludnev edited comment on SOLR-5211 at 12/4/15 8:10 AM: - I want to

[jira] [Comment Edited] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041236#comment-15041236 ] Mikhail Khludnev edited comment on SOLR-5211 at 12/4/15 8:09 AM: - I want to

[JENKINS] Lucene-Solr-trunk-Windows (32bit/jdk1.8.0_66) - Build # 5443 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5443/ Java: 32bit/jdk1.8.0_66 -server -XX:+UseG1GC 2 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test Error Message: Error from server at http://127.0.0.1:65069/zmld/awholynewcollection_0: non ok

[jira] [Commented] (LUCENE-6918) LRUQueryCache.onDocIdSetEviction should not be called when nothing is evicted

[ https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041509#comment-15041509 ] ASF subversion and git services commented on LUCENE-6918: - Commit 1717947 from

[jira] [Commented] (LUCENE-6918) LRUQueryCache.onDocIdSetEviction should not be called when nothing is evicted

[ https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041379#comment-15041379 ] Ryan Ernst commented on LUCENE-6918: +1, looks good. For the changes entry, I think you mean to

[jira] [Commented] (LUCENE-6918) LRUQueryCache.onDocIdSetEviction should not be called when nothing is evicted

[ https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041490#comment-15041490 ] Adrien Grand commented on LUCENE-6918: -- Good catch! > LRUQueryCache.onDocIdSetEviction should not

[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk1.9.0-ea-b93) - Build # 15110 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15110/ Java: 32bit/jdk1.9.0-ea-b93 -client -XX:+UseSerialGC -XX:-CompactStrings 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.CollectionsAPIDistributedZkTest Error Message: 5 threads leaked from SUITE scope

[JENKINS] Lucene-Solr-NightlyTests-trunk - Build # 871 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/871/ All tests passed Build Log: [...truncated 10989 lines...] [junit4] JVM J1: stdout was not empty, see:

[jira] [Commented] (SOLR-8366) ConcurrentUpdateSolrClient attempts to use response's content type as charset encoding

[ https://issues.apache.org/jira/browse/SOLR-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041635#comment-15041635 ] ASF subversion and git services commented on SOLR-8366: --- Commit 1717978 from

[jira] [Updated] (SOLR-8366) ConcurrentUpdateSolrClient attempts to use response's content type as charset encoding for parsing exceptions

[ 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

[jira] [Resolved] (SOLR-8366) ConcurrentUpdateSolrClient attempts to use response's content type as charset encoding for parsing exceptions

[ 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 >

[jira] [Commented] (SOLR-8366) ConcurrentUpdateSolrClient attempts to use response's content type as charset encoding

[ https://issues.apache.org/jira/browse/SOLR-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041641#comment-15041641 ] ASF subversion and git services commented on SOLR-8366: --- Commit 1717982 from

[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0_66) - Build # 15111 - Still Failing!

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

[jira] [Created] (SOLR-8370) Display Similarity Factory in use in Schema-Browser

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:

[jira] [Commented] (LUCENE-6918) LRUQueryCache.onDocIdSetEviction should not be called when nothing is evicted

[ https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041557#comment-15041557 ] ASF subversion and git services commented on LUCENE-6918: - Commit 1717963 from

[jira] [Resolved] (LUCENE-6918) LRUQueryCache.onDocIdSetEviction should not be called when nothing is evicted

[ 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

[JENKINS] Lucene-Solr-5.x-Windows (64bit/jdk1.8.0_66) - Build # 5313 - Failure!

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

[JENKINS] Lucene-Solr-Tests-trunk-Java8 - Build # 678 - Failure

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:

[JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.8.0_66) - Build # 14816 - Failure!

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

[jira] [Assigned] (SOLR-6271) ConjunctionSolrSpellChecker wrong check for same string distance

[ 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 >

[jira] [Updated] (SOLR-6271) ConjunctionSolrSpellChecker wrong check for same string distance

[ 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

[GitHub] lucene-solr pull request: Fix Typo/Bug for AND operation on queryn...

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

[jira] [Commented] (SOLR-6271) ConjunctionSolrSpellChecker wrong check for same string distance

[ https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041829#comment-15041829 ] ASF subversion and git services commented on SOLR-6271: --- Commit 1717999 from

[jira] [Commented] (SOLR-6271) ConjunctionSolrSpellChecker wrong check for same string distance

[ https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041831#comment-15041831 ] ASF subversion and git services commented on SOLR-6271: --- Commit 1718000 from

[jira] [Commented] (SOLR-8368) A SolrCore needs to replay it's tlog before the leader election process.

[ https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041855#comment-15041855 ] Mark Miller commented on SOLR-8368: --- I keep trying to think of reasons we don't have to do this. But I

[jira] [Commented] (SOLR-8368) A SolrCore needs to replay it's tlog before the leader election process.

[ https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041693#comment-15041693 ] Mark Miller commented on SOLR-8368: --- Of course, replaying a tlog when everything works well should be an

[jira] [Commented] (SOLR-8364) SpellCheckComponentTest occasionally fails

[ https://issues.apache.org/jira/browse/SOLR-8364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041747#comment-15041747 ] James Dyer commented on SOLR-8364: -- Ok, looking closely at the log, I see this: {noformat} [junit4] 2>

[jira] [Created] (SOLR-8371) Try and prevent too many recovery requests from stacking up and clean up some faulty logic.

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

[jira] [Updated] (SOLR-8371) Try and prevent too many recovery requests from stacking up and clean up some faulty logic.

[ 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

[jira] [Commented] (SOLR-8368) A SolrCore needs to replay it's tlog before the leader election process.

[ https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041686#comment-15041686 ] Mike Drob commented on SOLR-8368: - This could take a long time, though, right? Is there any danger/downside

[jira] [Commented] (LUCENE-6910) fix 2 interesting and 2 trivial issues found by "Coverity scan results of Lucene"

[ https://issues.apache.org/jira/browse/LUCENE-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041744#comment-15041744 ] ASF subversion and git services commented on LUCENE-6910: - Commit 1717993 from

[jira] [Commented] (SOLR-8368) A SolrCore needs to replay it's tlog before the leader election process.

[ https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041691#comment-15041691 ] Mark Miller commented on SOLR-8368: --- It could take a long time, but it's simply necessary for the

Re: A 5.4 release?

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

[jira] [Created] (SOLR-8372) Canceled recovery can lead to data loss

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: A 5.4 release?

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,

Re: Lucene/Solr git mirror will soon turn off

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

Re: Lucene/Solr git mirror will soon turn off

> 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

Re: Lucene/Solr git mirror will soon turn off

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

Re: Lucene/Solr git mirror will soon turn off

> 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

[jira] [Updated] (SOLR-7304) Spellcheck.collate Sometimes Invalidates Range Queries

[ 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

[jira] [Comment Edited] (SOLR-7304) Spellcheck.collate Sometimes Invalidates Range Queries

[ https://issues.apache.org/jira/browse/SOLR-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042237#comment-15042237 ] James Dyer edited comment on SOLR-7304 at 12/4/15 9:06 PM: --- Attached is a patch

[jira] [Updated] (SOLR-7304) Spellcheck.collate Sometimes Invalidates Range Queries

[ 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

[jira] [Updated] (SOLR-8292) TransactionLog.next() does not honor contract and return null for EOF

[ 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

Re: Lucene/Solr git mirror will soon turn off

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

[jira] [Updated] (SOLR-8373) KerberosPlugin: Using multiple nodes on same machine leads clients to fetch TGT for every request

[ 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

Re: Lucene/Solr git mirror will soon turn off

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 >

Re: Lucene/Solr git mirror will soon turn off

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

Re: Lucene/Solr git mirror will soon turn off

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

Re: Lucene/Solr git mirror will soon turn off

> [...] 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

[jira] [Commented] (SOLR-7495) Unexpected docvalues type NUMERIC when grouping by a int facet

[ https://issues.apache.org/jira/browse/SOLR-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042147#comment-15042147 ] Peter Ciuffetti commented on SOLR-7495: --- The multi value work around is not available to me because I

[jira] [Updated] (SOLR-7304) Spellcheck.collate Sometimes Invalidates Range Queries

[ 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)

[JENKINS] Lucene-Solr-5.x-Linux (32bit/jdk1.8.0_66) - Build # 14818 - Failure!

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

Re: Lucene/Solr git mirror will soon turn off

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

[jira] [Commented] (LUCENE-6919) Change the Scorer API to expose an iterator instead of extending DocIdSetIterator

[ https://issues.apache.org/jira/browse/LUCENE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042367#comment-15042367 ] Ryan Ernst commented on LUCENE-6919: +1 to the idea > Change the Scorer API to expose an iterator

[jira] [Created] (SOLR-8374) Issue with _text_ type in schema file

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

[jira] [Closed] (LUCENE-3341) Spellcheker is not checking word with less than 3 characters

[ 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

Lucene/Solr git mirror will soon turn off

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

[jira] [Commented] (LUCENE-6908) TestGeoUtils.testGeoRelations is buggy with irregular rectangles

[ https://issues.apache.org/jira/browse/LUCENE-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042248#comment-15042248 ] Michael McCandless commented on LUCENE-6908: Those benchmark results are nice [~nknize]! Is

RE: Lucene/Solr git mirror will soon turn off

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

[jira] [Created] (SOLR-8373) KerberosPlugin: Using multiple nodes on same machine leads clients to fetch TGT for every request

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:

[jira] [Commented] (LUCENE-6837) Add N-best output capability to JapaneseTokenizer

[ https://issues.apache.org/jira/browse/LUCENE-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042258#comment-15042258 ] Michael McCandless commented on LUCENE-6837: [~cm] are you planning to backport this for 5.5?

Re: Lucene/Solr git mirror will soon turn off

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

Re: Lucene/Solr git mirror will soon turn off

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

Re: Lucene/Solr git mirror will soon turn off

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

[JENKINS] Lucene-Solr-trunk-Windows (32bit/jdk1.8.0_66) - Build # 5445 - Failure!

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,

[jira] [Updated] (SOLR-8374) Issue with _text_ field in schema file

[ 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) >

Re: Lucene/Solr git mirror will soon turn off

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

[jira] [Commented] (SOLR-7495) Unexpected docvalues type NUMERIC when grouping by a int facet

[ https://issues.apache.org/jira/browse/SOLR-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042220#comment-15042220 ] David Smiley commented on SOLR-7495: Ok; you could use two fields then, one for sorting purposes, one

Re: A 5.4 release?

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

[jira] [Commented] (LUCENE-6920) Simplify callable function checks in Expression module

[ https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042522#comment-15042522 ] Uwe Schindler commented on LUCENE-6920: --- Thanks for the hint. There is another getClassLoader and

[jira] [Commented] (SOLR-8374) Issue with _text_ field in schema file

[ https://issues.apache.org/jira/browse/SOLR-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042452#comment-15042452 ] Erick Erickson commented on SOLR-8374: -- How is the ping request generated? This is probably the result

[jira] [Updated] (LUCENE-6920) Simplify callable function checks in Expression module

[ 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

[jira] [Created] (LUCENE-6920) Simplify callable function checks in Expression module

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

[jira] [Updated] (LUCENE-6920) Simplify callable function checks in Expression module

[ 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

[jira] [Comment Edited] (LUCENE-6920) Simplify callable function checks in Expression module

[ https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042528#comment-15042528 ] Uwe Schindler edited comment on LUCENE-6920 at 12/5/15 1:14 AM: New patch

RE: Lucene/Solr git mirror will soon turn off

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

Re: Lucene/Solr git mirror will soon turn off

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

[jira] [Commented] (LUCENE-6920) Simplify callable function checks in Expression module

[ https://issues.apache.org/jira/browse/LUCENE-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042515#comment-15042515 ] Robert Muir commented on LUCENE-6920: - +1, looks good. We may also try removing the hack for it in

[jira] [Updated] (SOLR-8375) ReplicaAssigner rejects valid positions

[ 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 >

[jira] [Created] (SOLR-8375) 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

[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_66) - Build # 15115 - Failure!

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:

Re: A 5.4 release?

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,

[jira] [Created] (SOLR-8376) Jetty 9.2.14.v20151106 upgrade from 9.2.11

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

[jira] [Commented] (SOLR-8359) Restrict child classes from using parent logger's state

[ https://issues.apache.org/jira/browse/SOLR-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042647#comment-15042647 ] Mike Drob commented on SOLR-8359: - +1 LGTM > Restrict child classes from using parent logger's state >

[jira] [Commented] (SOLR-8260) Use NIO2 APIs in core discovery

[ https://issues.apache.org/jira/browse/SOLR-8260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042651#comment-15042651 ] David Smiley commented on SOLR-8260: bq. will update. Looking forward to that still ;-) > Use NIO2

[jira] [Created] (SOLR-8377) Unnecessary for loop in ReplicaAssigner.tryAllPermutations()

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:

[jira] [Updated] (SOLR-8377) Unnecessary for loop in ReplicaAssigner.tryAllPermutations()

[ 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

[jira] [Commented] (SOLR-8359) Restrict child classes from using parent logger's state

[ https://issues.apache.org/jira/browse/SOLR-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042671#comment-15042671 ] Anshum Gupta commented on SOLR-8359: Thanks Jason and Mike. I'll take a look at this. > Restrict child

[jira] [Commented] (LUCENE-6919) Change the Scorer API to expose an iterator instead of extending DocIdSetIterator

[ https://issues.apache.org/jira/browse/LUCENE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042672#comment-15042672 ] David Smiley commented on LUCENE-6919: -- +1 because it seems to perform better. And I could see it

Re: Lucene/Solr git mirror will soon turn off

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

[jira] [Resolved] (SOLR-8374) Issue with _text_ field in schema file

[ 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

[GitHub] lucene-solr pull request: SOLR-6271: ConjunctionSolrSpellChecker w...

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

Re: A 5.4 release?

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

[jira] [Updated] (SOLR-8371) Try and prevent too many recovery requests from stacking up and clean up some faulty logic.

[ 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

[jira] [Commented] (SOLR-6271) ConjunctionSolrSpellChecker wrong check for same string distance

[ https://issues.apache.org/jira/browse/SOLR-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041891#comment-15041891 ] ASF GitHub Bot commented on SOLR-6271: -- Github user asfgit closed the pull request at:

[jira] [Updated] (LUCENE-6919) Change the Scorer API to expose an iterator instead of extending DocIdSetIterator

[ 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

[jira] [Resolved] (LUCENE-6910) fix 2 interesting and 2 trivial issues found by "Coverity scan results of Lucene"

[ 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

[jira] [Commented] (LUCENE-6910) fix 2 interesting and 2 trivial issues found by "Coverity scan results of Lucene"

[ https://issues.apache.org/jira/browse/LUCENE-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041965#comment-15041965 ] ASF subversion and git services commented on LUCENE-6910: - Commit 1718007 from

[jira] [Created] (LUCENE-6919) Change the Scorer API to expose an iterator instead of extending DocIdSetIterator

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

[jira] [Resolved] (SOLR-6271) ConjunctionSolrSpellChecker wrong check for same string distance

[ 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. >

  1   2   >