Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALPm_-CO+3Gg7oX2cS3Y37fY0JF2RuCWmbEgtYy7M9Gz2oD7-g@mail.gmail.com>
References: 
 <CALPm_-DESXBv=DJgiKqCOFdgYxhqKxK_ciPzs0fU2ooWiNqfSw@mail.gmail.com>
 <1455797081.156046.524833242.751DBB13@webmail.messagingengine.com>
 <CALPm_-DstpuSnuhb8pTTQJ30HqmBqTuUMXpN=NO9=nFsABAMrw@mail.gmail.com>
 <56C5D661.60902@elyograg.org>
 <CALPm_-CO+3Gg7oX2cS3Y37fY0JF2RuCWmbEgtYy7M9Gz2oD7-g@mail.gmail.com>
From: Anil <anilklce@gmail.com>
Date: Mon, 22 Feb 2016 11:48:15 +0530
Message-ID: 
 <CALPm_-DZswEyPgi576F0D5seviGJz+noz_XAD5Vu5Jh4Nw6vkw@mail.gmail.com>
Subject: Re: Facet Filter
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=089e0139fd0cb30316052c55ce09

--089e0139fd0cb30316052c55ce09
Content-Type: text/plain; charset=UTF-8

HI Shawn,

solr Documentation says docValues=true/false works for only few fields.
will that work on Text field ?

Copy from the reference guide -

DocValues are only available for specific field types. The types chosen
determine the underlying Lucene
docValue type that will be used. The available Solr field types are:
StrField and UUIDField.
If the field is single-valued (i.e., multi-valued is false), Lucene will
use the SORTED type.
If the field is multi-valued, Lucene will use the SORTED_SET type.
If you have already indexed data into your Solr index, you will need to
completely re-index your content
after changing your field definitions in schema.xml in order to
successfully use docValues.

Any Trie* numeric fields and EnumField.
If the field is single-valued (i.e., multi-valued is false), Lucene will
use the NUMERIC type.
If the field is multi-valued, Lucene will use the SORTED_SET type.


Regards,
Anil

On 19 February 2016 at 08:49, Anil <anilklce@gmail.com> wrote:

> Thanks Shawn. This really helps. we are using 4.10.3 now.. will look into
> 5.4.1. Thanks.
>
> Regards,
> Anil
>
> On 18 February 2016 at 20:04, Shawn Heisey <apache@elyograg.org> wrote:
>
>> On 2/18/2016 7:12 AM, Anil wrote:
>> > Thank you, i just checked in 5.1.
>> >
>> > as facet fields has to be Strings and cannot be tockenized. is there any
>> > way to search on case insensitive search on this field (not in a facet
>> > filter scenario).
>>
>> If you configure docValues on the field in schema.xml and reindex, then
>> the returned facets will be the original input values even if the field
>> is tokenized, just as if you had used a string type without docValues.
>> This should allow you to use one field for queries *and* facets.
>>
>> The reindex *is* required after adding docValues, and the index will be
>> larger.
>>
>> Note that using 5.1 isn't recommended at this point.  You should use the
>> latest version available.  Currently that's 5.4.1, but soon it will be
>> 5.5.
>>
>> Thanks,
>> Shawn
>>
>>
>

--089e0139fd0cb30316052c55ce09--