Yeah, now I kind of understood. Is this why BlockTreeTermsWriter plugs in it's freezeTail logic of meeting min-nbr of terms per block and building a trie for locating sub-blocks?
-- Ravi On Fri, Nov 15, 2013 at 11:17 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > When you turn on pruning, FST Builder will just remove nodes that > don't have a high enough count of input terms traversing through them. > E.g. if minSuffixCount1 is 100 then only FST nodes that see >= 100 > input terms coming through them, are preserved. > > You can use this to build a prefix trie instead of the full FST. > > Creating a custom tail freezer is very expert: it lets you implement > arbitrary logic on which nodes are pruned or not. > > Mike McCandless > > http://blog.mikemccandless.com > > > On Fri, Nov 15, 2013 at 12:16 PM, Ravikumar Govindarajan > <ravikumar.govindara...@gmail.com> wrote: > > I was trying to understand some logic in Builder class of FST. > > > > The method freezeTail() looks quite hairy. I gather that there is an some > > logic for pruning a node or compiling it. > > > > What exactly is pruning a node? An example of it will be really really > > helpful > > > > -- > > Ravi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
