Return-Path: 
 <dev-return-77241-apmail-lucene-dev-archive=lucene.apache.org@lucene.apache.org>
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 971F7814F
	for <apmail-lucene-dev-archive@www.apache.org>;
 Wed, 10 Aug 2011 22:37:34 +0000 (UTC)
Received: (qmail 64216 invoked by uid 500); 10 Aug 2011 22:37:33 -0000
Delivered-To: apmail-lucene-dev-archive@lucene.apache.org
Received: (qmail 64087 invoked by uid 500); 10 Aug 2011 22:37:32 -0000
Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:dev@lucene.apache.org>
List-Id: <dev.lucene.apache.org>
Reply-To: dev@lucene.apache.org
Delivered-To: mailing list dev@lucene.apache.org
Received: (qmail 64080 invoked by uid 99); 10 Aug 2011 22:37:32 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2011 22:37:32 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of erik.hatcher@gmail.com
 designates 209.85.212.48 as permitted sender)
Received: from [209.85.212.48] (HELO mail-vw0-f48.google.com) (209.85.212.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2011 22:37:24 +0000
Received: by vws7 with SMTP id 7so1934248vws.35
        for <dev@lucene.apache.org>; Wed, 10 Aug 2011 15:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        bh=weZIWUwm2xjLj9On+qizlFFl6JMqlKkNOdvXWgh4YSo=;
        b=XCeLsioJxjId/SuaKJDBe9+tKjuDVX2gcYefXMWzShiGt3MOK0eRetvzXFpbhf2E9v
         gZZmMD/zHSfbRSrOdLg5D9UjeldkJryO+7uCDZbj0RlvY8fTM0pQZlvu9iBWVt79t7s7
         UqBTyws6vmomxJpweQBmXZycnfqLyu4C5uihc=
Received: by 10.52.89.105 with SMTP id bn9mr3709518vdb.416.1313015823865;
        Wed, 10 Aug 2011 15:37:03 -0700 (PDT)
Received: from [10.0.1.11] (c-24-125-38-32.hsd1.va.comcast.net [24.125.38.32])
        by mx.google.com with ESMTPS id a6sm651663vcp.15.2011.08.10.15.37.01
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 10 Aug 2011 15:37:02 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Solr schema: Sentence to refine copyField command
From: Erik Hatcher <erik.hatcher@gmail.com>
In-Reply-To: <003b01cc57a4$4066be30$c1343a90$@gmail.com>
Date: Wed, 10 Aug 2011 18:37:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA262A1F-0495-4756-8E97-C7047CFBCD13@gmail.com>
References: <003b01cc57a4$4066be30$c1343a90$@gmail.com>
To: dev@lucene.apache.org
X-Mailer: Apple Mail (2.1084)

Eugeny -

Rather than add another feature like this, consider using the hl.fl =
parameter (see http://wiki.apache.org/solr/HighlightingParameters for =
details) for specifying the other fields you want highlighted.  And also =
consider not storing the TEXT field as you don't really need it given =
you will be storing FIELD1...FIELD3.

	Erik

On Aug 10, 2011, at 17:27 , Eugeny Balakhonov wrote:

> Hello, all!
> =20
> According to documentation Solr one field for search by default is =
possible only:
> =20
> <defaultSearchField>TEXT</defaultSearchField>
> =20
> This field can be filled with following commands:
> =20
> <copyField source=3D"FIELD1" dest=3D"TEXT"/>
> <copyField source=3D"FIELD2" dest=3D"TEXT"/>
> <copyField source=3D"FIELD3" dest=3D"TEXT"/>
> =20
> In this case the =93TEXT=94 field is purely technical and isn't =
intended for an output to the user.
> =20
> By search with q=3Dfoo we will receive result as is resulted in a =
following example::
> =20
> =85=85=85=85.
> <lst name=3D"highlighting">
>     <lst name=3D"154203.6194667...">
>         <arr name=3D"TEXT">
>             <str>Something <em>foo</em></str>
>         </arr>
>     </lst>
>     <lst name=3D"154203.6711988...">
>         <arr name=3D"TEXT">
>             <str> Something <em>foo</em></str>
>         </arr>
>     </lst>
> </lst>
> =85=85=85=85..
> =20
> But in this case we have no information where really the found string =
"Something foo" is stored in the source document.
> I suggest to expand of copyField command for storing a name of source =
field:
> =20
> In the Solr schema:
> =20
> <copyField source=3D"ENT_LIST_ENT_GCP" dest=3D"TEXT" =
saveSourceFieldName=3D=94true=94 />
> =20
> In the search result:
> =20
> =85=85=85=85.
> <arr name=3D"TEXT">
>     <str source=3D"FIELD1">Something foo</str>
>     <str source=3D"FIELD2">foo foo</str>
>     <str source=3D"FIELD3">123 123 123</str>
> </arr>
> =85=85=85=85.
> <lst name=3D"highlighting">
>     <lst name=3D"154203.6194667...">
>         <arr name=3D"TEXT">
>             <str source=3D"FIELD1">Something <em>foo</em></str>
>         </arr>
>     </lst>
>     <lst name=3D"154203.6711988...">
>         <arr name=3D"TEXT">
>             <str source=3D"FIELD1"> Something <em>foo</em></str>
>         </arr>
>     </lst>
> </lst>
> =85=85=85=85..
> =20
> I think that this is very useful feature. There can be someone from =
developers will become interested in its implementation?
> =20
> Best regards,
> Eugeny


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org