Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4FCD2F10F for ; Fri, 12 Dec 2014 13:06:00 +0000 (UTC) Received: (qmail 55326 invoked by uid 500); 12 Dec 2014 13:05:55 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 55265 invoked by uid 500); 12 Dec 2014 13:05:55 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 55248 invoked by uid 99); 12 Dec 2014 13:05:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 13:05:54 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tomoko.uchida.1111@gmail.com designates 209.85.215.51 as permitted sender) Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 13:05:29 +0000 Received: by mail-la0-f51.google.com with SMTP id ms9so5974049lab.24 for ; Fri, 12 Dec 2014 05:03:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=eG4LNwSVtsZmmYIGmWjZ3DMT8rOYrjB9kinNty46jEs=; b=E/NDAIb8APD1ORMZCnAQzQB/R0lN86ED3gzYV14/59SBpM8K+fEMWINES5ai2uv7aO RTSssPFL374bDtQukhFukBC3L+pha97FvXMZIQj9lq3x6nBDVpXopRdeIJKxK1LPkn/n 7UcSwp2s6gDcp7GD6TFYo3RGmRFOJ5rPeRdzrs1+KGXCTgB0BT8pdpHjUJpNk6xt+I0B 5OAMmGhAiL7aB0Mb11Xhefak8oWyyHbOqvPDJ+sNxRsNtWccgB9Ec2+YZAKPIDvZpgxr e0G5FdlcVWinKJbWFaFANRjk0Luerqmw+kR85+o3AxoMstSf9La9NQxAU4RIIc48Oa3C fqUQ== MIME-Version: 1.0 X-Received: by 10.112.202.71 with SMTP id kg7mr15123099lbc.16.1418389392847; Fri, 12 Dec 2014 05:03:12 -0800 (PST) Received: by 10.112.98.168 with HTTP; Fri, 12 Dec 2014 05:03:12 -0800 (PST) In-Reply-To: References: <548A28A0.3030808@safaribooksonline.com> Date: Fri, 12 Dec 2014 22:03:12 +0900 Message-ID: Subject: Re: Highlighting integer field From: Tomoko Uchida To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=001a11c3714ae9f83f050a048321 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3714ae9f83f050a048321 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I did not know about LUCENE-3080. (and take a look now) So discussion seems to be beyond user mailing list, but thank you for your information. Regards, Tomoko 2014-12-12 21:04 GMT+09:00 Pawel : > > Hi again, > When I removed those lines from DefaultSolrHighlighter and rebuilt Solr i= t > seems to work. > > final SchemaField schemaField =3D schema.getFieldOrNull(fieldName); > if (schemaField !=3D null && ((schemaField.getType() instanceof > org.apache.solr.schema.TrieField) > || (schemaField.getType() instanceof > org.apache.solr.schema.TrieDateField))) { > return; > } > > There is still information about LUCENE-3080 in comments (and this JIRA > issue is still open) but some other issue seems to be resolved: SOLR-249= 7 > which says it is blocked by LUCENE-3080. > > > On Fri, Dec 12, 2014 at 12:51 PM, Tomoko Uchida < > tomoko.uchida.1111@gmail.com> wrote: > > > > Hi, > > > > As Mike have pointed, there is no way to highlight numeric fields. > > If you want to highlight, you have to index them as *text* field. It's > not > > about Solr, but Lucene. > > > > (Maybe it's possible to "highlight" them in application layer, server > side > > program or client side JavaScript, rather than Solr?) > > > > -- > > Tomoko > > > > > > 2014-12-12 18:27 GMT+09:00 Pawel : > > > > > > Hi, > > > Thanks for your response. Do you maybe have an idea how to handle > > integers > > > (even on low level - Lucene) in highlighter? > > > > > > -- > > > Pawe=C5=82 > > > > > > On Fri, Dec 12, 2014 at 12:28 AM, Michael Sokolov < > > > msokolov@safaribooksonline.com> wrote: > > > > > > > > So the short answer to your original question is "no." Highlighting > is > > > > designed to find matches *within* a tokenized (text) field only. > That > > is > > > > difficult because text gets processed and there are all sorts of > > > > complications, but for integers it should be pretty easy to match t= he > > > > values in the document and those in the query in the client, ie > without > > > > help from Solr? > > > > > > > > -Mike > > > > > > > > > > > > On 12/11/14 6:19 PM, Pawel wrote: > > > > > > > >> Hi, > > > >> Thanks for response. It is quite important to me for example to > > > highlight > > > >> multivalued field with many int or long tokens. > > > >> > > > >> -- > > > >> Pawe=C5=82 > > > >> > > > >> On Thu, Dec 11, 2014 at 3:08 PM, Tomoko Uchida < > > > >> tomoko.uchida.1111@gmail.com > > > >> > > > >>> wrote: > > > >>> > > > >>> Hi Pawel, > > > >>> > > > >>> Essentially, highlighting is a feature to show "fragments of > > documents" > > > >>> that matche user queries. > > > >>> With that, he/she can find occurrence of their query in long > > documents > > > >>> and > > > >>> can understand their results well. > > > >>> > > > >>> For tint or tlong fields (or other non-text field types), > "fragments" > > > >>> usually have no meaning. > > > >>> > > > >>> So, excuse me, I cannot understand your intent. > > > >>> If you specify your need a little bit more, I or other fellows ma= y > be > > > >>> able > > > >>> to help you. > > > >>> > > > >>> Regards, > > > >>> Tomoko > > > >>> > > > >>> 2014-12-11 19:12 GMT+09:00 Pawel Rog : > > > >>> > > > >>> Hi, > > > >>>> Is it possible to highlight int (TrieLongField) or long > > > (TrieLongField) > > > >>>> field in Solr? > > > >>>> > > > >>>> -- > > > >>>> Pawe=C5=82 > > > >>>> > > > >>>> > > > > > > > > > > --001a11c3714ae9f83f050a048321--