Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of furkankamaci@gmail.com
 designates 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1394546793081-4122864.post@n3.nabble.com>
References: <1394017221300-4121355.post@n3.nabble.com>
	<1394030169.53310.YahooMailNeo@web124701.mail.ne1.yahoo.com>
	<1394190972350-4121957.post@n3.nabble.com>
	<1394203685.45639.YahooMailNeo@web124702.mail.ne1.yahoo.com>
	<1394546793081-4122864.post@n3.nabble.com>
Date: Tue, 11 Mar 2014 16:20:39 +0200
Message-ID: 
 <CAHsXEHVaPKsTiLy38p5vTpK7URJZX6VpD4MVNa24Dg4aY8JmTA@mail.gmail.com>
Subject: Re: Implementing a customised tokenizer
From: Furkan KAMACI <furkankamaci@gmail.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=089e0139fc60b015df04f4556ca0

--089e0139fc60b015df04f4556ca0
Content-Type: text/plain; charset=ISO-8859-1

Hi;

I suggest you to look at the source code. NGramTokenizer.java has some
explanations as comments and it may help you.

Thanks;
Furkan KAMACI


2014-03-11 16:06 GMT+02:00 epnRui <rui_bandarra@hotmail.com>:

> Hi Ahmet,
>
> I think the expungesDelete is done automatically through SolrJ. So I don't
> think it was that.
> THe problem solved by itself apparently. I wonder if it has to do with an
> automatic optimization of Solr indexes?
> Otherwise it was something similar to XY problem :P
>
> Thanks for the help!
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Implementing-a-customised-tokenizer-tp4121355p4122864.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

--089e0139fc60b015df04f4556ca0--