From dev-return-316510-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Tue Mar 27 20:32:05 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 C172F18064E for ; Tue, 27 Mar 2018 20:32:04 +0200 (CEST) Received: (qmail 20970 invoked by uid 500); 27 Mar 2018 18:32: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 20960 invoked by uid 99); 27 Mar 2018 18:32:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Mar 2018 18:32:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CD341C0286 for ; Tue, 27 Mar 2018 18:32:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 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, T_RP_MATCHES_RCVD=-0.01, 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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 2TREBNog-HD6 for ; Tue, 27 Mar 2018 18:32:02 +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 7C0E15F3FF for ; Tue, 27 Mar 2018 18:32: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 B1D6BE0917 for ; Tue, 27 Mar 2018 18:32: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 760F02150F for ; Tue, 27 Mar 2018 18:32:00 +0000 (UTC) Date: Tue, 27 Mar 2018 18:32:00 +0000 (UTC) From: "Dean Gurvitz (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-9185) Solr's edismax and "Lucene"/standard query parsers should optionally not split on whitespace before sending terms to analysis 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/SOLR-9185?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16416= 051#comment-16416051 ]=20 Dean Gurvitz commented on SOLR-9185: ------------------------------------ I missed that comment. Anyways, I just think that we should be more careful= with such changes in minor versions, and at least explicitly mention them = in the changes.txt file for=C2=A0those who with to upgrade their version. > Solr's edismax and "Lucene"/standard query parsers should optionally not = split on whitespace before sending terms to analysis > -------------------------------------------------------------------------= ---------------------------------------------------- > > Key: SOLR-9185 > URL: https://issues.apache.org/jira/browse/SOLR-9185 > Project: Solr > Issue Type: New Feature > Reporter: Steve Rowe > Assignee: Steve Rowe > Priority: Major > Fix For: 6.5, 7.0 > > Attachments: SOLR-9185.patch, SOLR-9185.patch, SOLR-9185.patch, S= OLR-9185.patch > > > Copied from LUCENE-2605: > The queryparser parses input on whitespace, and sends each whitespace sep= arated term to its own independent token stream. > This breaks the following at query-time, because they can't see across wh= itespace boundaries: > n-gram analysis > shingles > synonyms (especially multi-word for whitespace-separated languages) > languages where a 'word' can contain whitespace (e.g. vietnamese) > Its also rather unexpected, as users think their charfilters/tokenizers/t= okenfilters will do the same thing at index and querytime, but > in many cases they can't. Instead, preferably the queryparser would parse= around only real 'operators'. -- 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