Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05B5C1089B for ; Tue, 13 Jan 2015 15:16:36 +0000 (UTC) Received: (qmail 37280 invoked by uid 500); 13 Jan 2015 15:16:35 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 37156 invoked by uid 500); 13 Jan 2015 15:16:35 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 36921 invoked by uid 99); 13 Jan 2015 15:16:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2015 15:16:35 +0000 Date: Tue, 13 Jan 2015 15:16:35 +0000 (UTC) From: "Adrien Grand (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (LUCENE-6179) Remove out-of-order scoring MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Adrien Grand created LUCENE-6179: ------------------------------------ Summary: Remove out-of-order scoring Key: LUCENE-6179 URL: https://issues.apache.org/jira/browse/LUCENE-6179 Project: Lucene - Core Issue Type: Improvement Reporter: Adrien Grand Assignee: Adrien Grand Fix For: 5.0, Trunk Out-of-order currently adds complexity that I would like to remove. Here is a selection of issues that come from out-of-order scoring. - lots of specializations with collectors: we have two versions of every top score/field collector depending on whether it should support out-of-order collection or not - it feels like it should be an implementation detail of our bulk scorers but it also makes our APIs more complicated, eg. LeafCollector.acceptsDocsOutOfOrder - if you create a TopFieldCollector, how do you know if you should pass docsScoredInOrder=true or false? To make the decision, you actually need to know whether your query supports out-of-order scoring while the API is on Weight. I initially wanted to keep it and improve the decision process in LUCENE-6172 but I'm not sure it's the right approach as it would require to make the API even more complicated... hence the suggestion to remove out-of-order scoring completely. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org