What worked for me was tweaking a code from velocity file, head.vm, I changed
'terms.prefix': function() { return $("#q").val().toLowerCase();}, which
solved my issue as I am using terms component for suggestions.
Dmitry Kan-2 wrote
> what kind of suggester are you using? Does its index get rebuil
what kind of suggester are you using? Does its index get rebuilt when you
reindex your data?
>From the analysis page at least I see, that you get a hit on Game, which is
lowercased to game.
On Thu, Apr 17, 2014 at 10:55 AM, Sunayana wrote:
> 1.My field definition:
>positionIncrementGap="100
1.My field definition:
2.On analysis page, it shows me the lowercased word,for both index
Could you show the updated field definition?
Does analysis page show sensible output for your query on indexing/querying
sides?
On Wed, Apr 16, 2014 at 5:52 PM, Sunayana wrote:
> Thanks for replying,
> 1.Yes,I re-indexed data after the changes.
> 2.Changing to STF, did not help..
>
>
>
>
> --
>
Thanks for replying,
1.Yes,I re-indexed data after the changes.
2.Changing to STF, did not help..
--
View this message in context:
http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131499.html
Sent from the Solr - User mailing list archive at Nabble.com.
1. did you re-index after changing schema?
2. Why do use KeywordTokenizerFactory and not StandardTokenizerFactory? KTF
treats entire field contents as one token. Does it do what you really want?
[1]
3. If you'd use STF, TrimFilterFactory would be obsolete, as tokenization
has been done already.
[
Hi,
Did u mean changing field type as
Hi,
Configure LowerCaseFilterFactory into the "query" side of your type config.
Dmitry
On Tue, Apr 15, 2014 at 10:50 AM, Sunayana wrote:
> Hi All,
>
> I have been trying out this autocomplete feature in Solr4.7.1 using
> Suggester.I have configured it to display phrase suggestions also.Proble
