From dev-return-320941-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Thu May 3 14:34:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5D7CC180625 for ; Thu, 3 May 2018 14:34:04 +0200 (CEST) Received: (qmail 24610 invoked by uid 500); 3 May 2018 12:34:03 -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 24596 invoked by uid 99); 3 May 2018 12:34:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2018 12:34:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 7672DC854D for ; Thu, 3 May 2018 12:34:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id wD4UngBAt23v for ; Thu, 3 May 2018 12:34:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3056D5F520 for ; Thu, 3 May 2018 12:34:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6537EE12BB for ; Thu, 3 May 2018 12:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 16EFF21296 for ; Thu, 3 May 2018 12:34:00 +0000 (UTC) Date: Thu, 3 May 2018 12:34:00 +0000 (UTC) From: "Adrien Grand (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (LUCENE-8286) UnifiedHighlighter should support the new Weight.matches API for better match accuracy MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LUCENE-8286?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D164= 62361#comment-16462361 ]=20 Adrien Grand commented on LUCENE-8286: -------------------------------------- bq. MI has things we don't need =E2=80=93 position spans I don't know the unified highlighter well, but I would expect this informat= ion to be important to score passages? For instance if you run a sloppy phr= ase query, matches that have a smaller width should get a higher weight, sh= ouldn't they? > UnifiedHighlighter should support the new Weight.matches API for better m= atch accuracy > -------------------------------------------------------------------------= ------------- > > Key: LUCENE-8286 > URL: https://issues.apache.org/jira/browse/LUCENE-8286 > Project: Lucene - Core > Issue Type: Improvement > Components: modules/highlighter > Reporter: David Smiley > Priority: Major > > The new Weight.matches() API should allow the UnifiedHighlighter to more = accurately highlight some BooleanQuery patterns correctly -- see LUCENE-790= 3. > In addition, this API should make the job of highlighting easier, reducin= g the LOC and related complexities, especially the UH's PhraseHelper. Note= : reducing/removing PhraseHelper is not a near-term goal since Weight.match= es is experimental and incomplete, and perhaps we'll discover some gaps in = flexibility/functionality. > This issue should introduce a new UnifiedHighlighter.HighlightFlag enum o= ption for this method of highlighting. Perhaps call it {{WEIGHT_MATCHES}}= ? Longer term it could go away and it'll be implied if you specify enum va= lues for PHRASES & MULTI_TERM_QUERY? -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org