bytes are good, I am in byte range on this data, and "even simpler" is good :)
It is simple, I just need to know if this automaton I used for AutomatonQuery accepts one stored field, so yes it is the same information as in Term, but I need to run over it once more because my query is not filtering on AutomatonQuery ((AutomatonQuery(A)) OR (OtherQuery) )+ So I get back documents not matched by this Automaton and I do not know which ones are there due to the "OtherQuery" running search in 2 passes, with and without automaton is not practicable On Wed, Aug 31, 2011 at 8:45 PM, Robert Muir <rcm...@gmail.com> wrote: > On Wed, Aug 31, 2011 at 2:37 PM, eks dev <eks...@yahoo.co.uk> wrote: >> Keeping AutomatonQuery around came to me as an option, but do not >> forget, I need Automaton (RunAutomaton) for post processing... There >> is no way to get Automaton back from the AutomatonQuery? >> > > The compiled automaton is not always a RunAutomaton, sometimes its > internal representation is something even simpler :) > Additionally, when it is a RunAutomaton, its a UTF-8 one, for > operating directly on bytes... > > Can you describe a little bit about what 'post processing' you need to > do? I imagine its post processing on something other than the terms? > > -- > lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
