[jira] [Commented] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007767#comment-14007767 ] Anshum Gupta commented on SOLR-6026: Yes. Though I should be able to get to it by the w

[jira] [Created] (LUCENE-5703) Don't allocate/copy bytes all the time in binary DV producers

Adrien Grand created LUCENE-5703: Summary: Don't allocate/copy bytes all the time in binary DV producers Key: LUCENE-5703 URL: https://issues.apache.org/jira/browse/LUCENE-5703 Project: Lucene - Core

[jira] [Commented] (LUCENE-5703) Don't allocate/copy bytes all the time in binary DV producers

[ https://issues.apache.org/jira/browse/LUCENE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007749#comment-14007749 ] Adrien Grand commented on LUCENE-5703: -- On a side note, I think that the fact that t

[jira] [Commented] (LUCENE-5702) Per-segment comparator API

[ https://issues.apache.org/jira/browse/LUCENE-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007733#comment-14007733 ] Michael McCandless commented on LUCENE-5702: +1, it would be great to massive

[jira] [Created] (LUCENE-5702) Per-segment comparator API

Adrien Grand created LUCENE-5702: Summary: Per-segment comparator API Key: LUCENE-5702 URL: https://issues.apache.org/jira/browse/LUCENE-5702 Project: Lucene - Core Issue Type: New Feature

[jira] [Commented] (LUCENE-5701) Move core closed listeners to AtomicReader

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

[jira] [Commented] (LUCENE-5701) Move core closed listeners to AtomicReader

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

[jira] [Commented] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007596#comment-14007596 ] Shalin Shekhar Mangar commented on SOLR-6026: - Does this mean that if there is

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007553#comment-14007553 ] ASF subversion and git services commented on SOLR-5681: --- Commit 15971

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007549#comment-14007549 ] ASF subversion and git services commented on SOLR-5681: --- Commit 15971

[jira] [Commented] (SOLR-5468) Option to enforce a majority quorum approach to accepting updates in SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007543#comment-14007543 ] ASF subversion and git services commented on SOLR-5468: --- Commit 15971

[jira] [Commented] (SOLR-5468) Option to enforce a majority quorum approach to accepting updates in SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007541#comment-14007541 ] ASF subversion and git services commented on SOLR-5468: --- Commit 15971

[jira] [Commented] (SOLR-5468) Option to enforce a majority quorum approach to accepting updates in SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007531#comment-14007531 ] ASF subversion and git services commented on SOLR-5468: --- Commit 15971

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007533#comment-14007533 ] ASF subversion and git services commented on SOLR-5681: --- Commit 15971

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007525#comment-14007525 ] ASF subversion and git services commented on SOLR-5681: --- Commit 15971

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007437#comment-14007437 ] ASF subversion and git services commented on SOLR-5681: --- Commit 15971

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007431#comment-14007431 ] ASF subversion and git services commented on SOLR-5681: --- Commit 15971

[jira] [Commented] (LUCENE-5701) Move core closed listeners to AtomicReader

[ https://issues.apache.org/jira/browse/LUCENE-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007398#comment-14007398 ] Robert Muir commented on LUCENE-5701: - Looks good, nice improvement! > Move core clo

[jira] [Updated] (LUCENE-5701) Move core closed listeners to AtomicReader

[ https://issues.apache.org/jira/browse/LUCENE-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-5701: - Attachment: LUCENE-5701.patch Good catch, I had missed that SCRW didn't return this as a cache k

[jira] [Commented] (LUCENE-5701) Move core closed listeners to AtomicReader

[ https://issues.apache.org/jira/browse/LUCENE-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007362#comment-14007362 ] Robert Muir commented on LUCENE-5701: - Patch looks great. Can SlowCompositeReaderWrap

[jira] [Commented] (LUCENE-5012) Make graph-based TokenFilters easier

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

[jira] [Updated] (LUCENE-5701) Move core closed listeners to AtomicReader

[ https://issues.apache.org/jira/browse/LUCENE-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-5701: - Attachment: LUCENE-5701.patch > Move core closed listeners to AtomicReader > ---

[jira] [Updated] (LUCENE-5701) Move core closed listeners to AtomicReader

[ https://issues.apache.org/jira/browse/LUCENE-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-5701: - Attachment: (was: LUCENE-5701.patch) > Move core closed listeners to AtomicReader >

[jira] [Updated] (LUCENE-5701) Move core closed listeners to AtomicReader

[ https://issues.apache.org/jira/browse/LUCENE-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-5701: - Attachment: LUCENE-5701.patch Here is a patch: * add/removeCoreClosedListener is abstract on At

Change the group.field name in the solr response

Hi, How can I change the field name in the "grouped" section of the solr response. I know for changing the field names in the response where solr returns documents you can make a query with "fl" changed as "fl=mapping1:fieldname1,mapping2:fieldname2" How do I achieve the same thing for "grouping"

[jira] [Commented] (LUCENE-5700) Add 'accountable' interface for various ramBytesUsed

[ https://issues.apache.org/jira/browse/LUCENE-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007183#comment-14007183 ] Michael McCandless commented on LUCENE-5700: +1 to clean this up. > Add 'ac

[jira] [Commented] (LUCENE-5701) Move core closed listeners to AtomicReader

[ https://issues.apache.org/jira/browse/LUCENE-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007180#comment-14007180 ] Robert Muir commented on LUCENE-5701: - +1 > Move core closed listeners to AtomicRead

[jira] [Created] (LUCENE-5701) Move core closed listeners to AtomicReader

Adrien Grand created LUCENE-5701: Summary: Move core closed listeners to AtomicReader Key: LUCENE-5701 URL: https://issues.apache.org/jira/browse/LUCENE-5701 Project: Lucene - Core Issue Type

[jira] [Updated] (LUCENE-5697) Preview issue

[ https://issues.apache.org/jira/browse/LUCENE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schoenmakers updated LUCENE-5697: Description: In DocFetcher, which uses Lucene v3.5.0, we stumbled on a bug. The le

[jira] [Updated] (LUCENE-5697) Preview issue

[ https://issues.apache.org/jira/browse/LUCENE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schoenmakers updated LUCENE-5697: Description: In DocFetcher, which uses Lucene v3.5.0, we stumbled on a bug. The le

[jira] [Updated] (LUCENE-5697) Preview issue

[ https://issues.apache.org/jira/browse/LUCENE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schoenmakers updated LUCENE-5697: Description: In DocFetcher, which uses Lucene v3.5.0, we stumbled on a bug. The le

[jira] [Commented] (LUCENE-5680) Allow updating multiple DocValues fields atomically

[ https://issues.apache.org/jira/browse/LUCENE-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007150#comment-14007150 ] Shai Erera commented on LUCENE-5680: bq. why do we have both MISSING and createMissin

[jira] [Commented] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module

[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007147#comment-14007147 ] rashi gandhi commented on LUCENE-2899: -- Hi, I have one running solr core with some

[jira] [Resolved] (LUCENE-5690) expose sub-Terms from MultiTerms

[ https://issues.apache.org/jira/browse/LUCENE-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved LUCENE-5690. -- Resolution: Fixed Fix Version/s: 5.0 4.9 I slapped "Expert" on these

[jira] [Commented] (LUCENE-5690) expose sub-Terms from MultiTerms

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

[jira] [Commented] (LUCENE-5690) expose sub-Terms from MultiTerms

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

[jira] [Resolved] (SOLR-6111) The 'deleteshard' collection API should be able to delete a shard in 'construction' state

[ https://issues.apache.org/jira/browse/SOLR-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar resolved SOLR-6111. - Resolution: Fixed > The 'deleteshard' collection API should be able to delete a sh

[jira] [Commented] (SOLR-6111) The 'deleteshard' collection API should be able to delete a shard in 'construction' state

[ https://issues.apache.org/jira/browse/SOLR-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007101#comment-14007101 ] ASF subversion and git services commented on SOLR-6111: --- Commit 15970

[jira] [Commented] (SOLR-6111) The 'deleteshard' collection API should be able to delete a shard in 'construction' state

[ https://issues.apache.org/jira/browse/SOLR-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007099#comment-14007099 ] ASF subversion and git services commented on SOLR-6111: --- Commit 15970

[jira] [Updated] (SOLR-6111) The 'deleteshard' collection API should be able to delete a shard in 'construction' state

[ https://issues.apache.org/jira/browse/SOLR-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-6111: Attachment: SOLR-6111.patch # Allow shards in 'construction' state to be deleted. #

[jira] [Commented] (LUCENE-5680) Allow updating multiple DocValues fields atomically

[ https://issues.apache.org/jira/browse/LUCENE-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007092#comment-14007092 ] Robert Muir commented on LUCENE-5680: - I'm gonna restate: I don't think we should all

[jira] [Commented] (LUCENE-5680) Allow updating multiple DocValues fields atomically

[ https://issues.apache.org/jira/browse/LUCENE-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007088#comment-14007088 ] Robert Muir commented on LUCENE-5680: - A few concerns: why do we have _both_ MISSING

[jira] [Created] (LUCENE-5700) Add 'accountable' interface for various ramBytesUsed

Robert Muir created LUCENE-5700: --- Summary: Add 'accountable' interface for various ramBytesUsed Key: LUCENE-5700 URL: https://issues.apache.org/jira/browse/LUCENE-5700 Project: Lucene - Core Is

Re: (Issue) How improve solr facet performance

On Fri, 2014-05-23 at 11:45 +0200, Alice.H.Yang (mis.cnsh04.Newegg) 41493 wrote: >We are blocked by solr facet performance when query hits many > documents. (about 10,000,000) [320M documents, immediate response for plain search with 1M hits] > But when we add several facet.field to do fa

[jira] [Resolved] (LUCENE-5683) Improve SegmentReader.getXXXDocValues

[ https://issues.apache.org/jira/browse/LUCENE-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-5683. - Resolution: Fixed Fix Version/s: 5.0 4.9 > Improve SegmentReader.getXX

[jira] [Commented] (LUCENE-5683) Improve SegmentReader.getXXXDocValues

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

[jira] [Commented] (LUCENE-5682) NPE in QueryRescorer when Scorer is null

[ https://issues.apache.org/jira/browse/LUCENE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007079#comment-14007079 ] Joel Bernstein commented on LUCENE-5682: Yes, thanks for resolving. > NPE in Que

[jira] [Created] (SOLR-6111) The 'deleteshard' collection API should be able to delete a shard in 'construction' state

Shalin Shekhar Mangar created SOLR-6111: --- Summary: The 'deleteshard' collection API should be able to delete a shard in 'construction' state Key: SOLR-6111 URL: https://issues.apache.org/jira/browse/SOLR-611

Re: [JENKINS] Lucene-4x-Linux-Java7-64-test-only - Build # 22242 - Still Failing!

Damned you flonkings!! Already fixed. Mike McCandless http://blog.mikemccandless.com On Fri, May 23, 2014 at 7:42 AM, wrote: > Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/22242/ > > 2 tests failed. > FAILED: > org.apache.lucene.index.TestDirectoryReaderReopen.testNPE

[JENKINS] Lucene-4x-Linux-Java7-64-test-only - Build # 22242 - Still Failing!

Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/22242/ 2 tests failed. FAILED: org.apache.lucene.index.TestDirectoryReaderReopen.testNPEAfterInvalidReindex1 Error Message: this codec cannot write docvalues Stack Trace: java.lang.UnsupportedOperationException: this codec cann

[jira] [Updated] (LUCENE-5695) Add DocIdSet.ramBytesUsed

[ https://issues.apache.org/jira/browse/LUCENE-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-5695: - Attachment: LUCENE-5695.patch Here is a new patch that makes ramBytesUsed abstract for 5.x. For

Re: [JENKINS] Lucene-4x-Linux-Java7-64-test-only - Build # 22239 - Failure!

I committed a fix. Mike McCandless http://blog.mikemccandless.com On Fri, May 23, 2014 at 6:52 AM, wrote: > Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/22239/ > > 2 tests failed. > REGRESSION: > org.apache.lucene.index.TestDirectoryReaderReopen.testNPEAfterInvalidRein

Re: [JENKINS] Lucene-4x-Linux-Java7-64-test-only - Build # 22241 - Failure!

I committed a fix. Mike McCandless http://blog.mikemccandless.com On Fri, May 23, 2014 at 7:26 AM, wrote: > Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/22241/ > > 2 tests failed. > REGRESSION: > org.apache.lucene.index.TestDirectoryReaderReopen.testNPEAfterInvalidRein

[JENKINS] Lucene-4x-Linux-Java7-64-test-only - Build # 22241 - Failure!

Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/22241/ 2 tests failed. REGRESSION: org.apache.lucene.index.TestDirectoryReaderReopen.testNPEAfterInvalidReindex2 Error Message: this codec cannot write docvalues Stack Trace: java.lang.UnsupportedOperationException: this codec

Re: (Issue) How improve solr facet performance

Thanks varun, but its aman not amit. :) With Regards Aman Tandon On Fri, May 23, 2014 at 4:22 PM, Varun Thacker wrote: > @Amit - https://cwiki.apache.org/confluence/display/solr/DocValues > > > On Fri, May 23, 2014 at 4:15 PM, Jack Krupansky > wrote: > >> (In the future, please submit this t

Re: (Issue) How improve solr facet performance

@Amit - https://cwiki.apache.org/confluence/display/solr/DocValues On Fri, May 23, 2014 at 4:15 PM, Jack Krupansky wrote: > (In the future, please submit this type of request to the solr-user > email list. Thanks.) > > How much system memory is available for OS file system caching? If your > i

[JENKINS] Lucene-4x-Linux-Java7-64-test-only - Build # 22239 - Failure!

Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/22239/ 2 tests failed. REGRESSION: org.apache.lucene.index.TestDirectoryReaderReopen.testNPEAfterInvalidReindex1 Error Message: this codec cannot write docvalues Stack Trace: java.lang.UnsupportedOperationException: this codec

[jira] [Commented] (LUCENE-5683) Improve SegmentReader.getXXXDocValues

[ https://issues.apache.org/jira/browse/LUCENE-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007040#comment-14007040 ] Shai Erera commented on LUCENE-5683: It's not ridiculous :). But +1 to commit. > Imp

[jira] [Commented] (LUCENE-5683) Improve SegmentReader.getXXXDocValues

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

Re: (Issue) How improve solr facet performance

(In the future, please submit this type of request to the solr-user email list. Thanks.) How much system memory is available for OS file system caching? If your index (30G) doesn't fit in memory, that can cause thrashing. I would suggest that 320 million docs is way too much for a single Solr n

Re: (Issue) How improve solr facet performance

What is DocValues i am unaware of this?? With Regards Aman Tandon On Fri, May 23, 2014 at 4:04 PM, Varun Thacker wrote: > Have you tried using DocValues and see the performance gains? > > > On Fri, May 23, 2014 at 3:15 PM, Alice.H.Yang (mis.cnsh04.Newegg) 41493 < > alice.h.y...@newegg.com> wrot

[jira] [Commented] (LUCENE-5683) Improve SegmentReader.getXXXDocValues

[ https://issues.apache.org/jira/browse/LUCENE-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007030#comment-14007030 ] Robert Muir commented on LUCENE-5683: - #1 there was an instanceof check before (the c

Re: (Issue) How improve solr facet performance

Have you tried using DocValues and see the performance gains? On Fri, May 23, 2014 at 3:15 PM, Alice.H.Yang (mis.cnsh04.Newegg) 41493 < alice.h.y...@newegg.com> wrote: > Hi, Solr Developers > > > >We are blocked by solr facet performance when query hits many > documents. (about 10,000,0

(Issue) How improve solr facet performance

Hi, Solr Developers We are blocked by solr facet performance when query hits many documents. (about 10,000,000) Details as follow: I have single solr node (solr version is 4.6 ), total has 320,000,000 documents( local index is about 30G) the index directory as follow： [cid:image0

[jira] [Resolved] (LUCENE-5684) Add best effort detection when index is removed & recreated before openIfChanged

[ https://issues.apache.org/jira/browse/LUCENE-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-5684. Resolution: Fixed > Add best effort detection when index is removed & recreated be

[jira] [Resolved] (LUCENE-5682) NPE in QueryRescorer when Scorer is null

[ https://issues.apache.org/jira/browse/LUCENE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-5682. Resolution: Fixed Fix Version/s: 5.0 4.9 I think this is

[jira] [Commented] (LUCENE-5684) Add best effort detection when index is removed & recreated before openIfChanged

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

[jira] [Commented] (LUCENE-5684) Add best effort detection when index is removed & recreated before openIfChanged

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

[jira] [Created] (LUCENE-5699) Lucene classification score calculation normalize and return lists

Gergő Törcsvári created LUCENE-5699: --- Summary: Lucene classification score calculation normalize and return lists Key: LUCENE-5699 URL: https://issues.apache.org/jira/browse/LUCENE-5699 Project: Luc

[jira] [Commented] (LUCENE-5675) "ID postings format"

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

[jira] [Resolved] (LUCENE-5675) "ID postings format"

[ https://issues.apache.org/jira/browse/LUCENE-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-5675. Resolution: Fixed Fix Version/s: 5.0 4.9 > "ID postings

[jira] [Created] (LUCENE-5698) Evaluate Lucene classification on publicly available datasets

Gergő Törcsvári created LUCENE-5698: --- Summary: Evaluate Lucene classification on publicly available datasets Key: LUCENE-5698 URL: https://issues.apache.org/jira/browse/LUCENE-5698 Project: Lucene -

[jira] [Created] (LUCENE-5697) Preview issue

Martin Schoenmakers created LUCENE-5697: --- Summary: Preview issue Key: LUCENE-5697 URL: https://issues.apache.org/jira/browse/LUCENE-5697 Project: Lucene - Core Issue Type: Bug

Early Access builds for JDK 9 b13, JDK 8u20 b15 and JDK 7u60 b15 are available on java.net

Hi Uwe,Dawid, Early Access builds for JDK 9 b13 , JDK 8u20 b15 and JDK 7u60 b15 are available on java.net. As we enter the later phases of development for JDK 7u60 & JDK 8u20 , please

[jira] [Resolved] (SOLR-6110) DIH increase tcp connections so full-import failed

[ https://issues.apache.org/jira/browse/SOLR-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar resolved SOLR-6110. - Resolution: Duplicate Resolving as a duplicate. If we ever release 4.7.3 then we'

[jira] [Commented] (SOLR-4968) The collection alias api should have a list cmd.

[ https://issues.apache.org/jira/browse/SOLR-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006951#comment-14006951 ] Shalin Shekhar Mangar commented on SOLR-4968: - This information is available wi