No, it's a single file, but the only way to serialize it is via IndexOutput/IndexInput and these require a Directory. I'll switch to using a subfolder, but this use case makes me think a simple serializer/deserializer from InputStream/OutputStream would be probably a good addition to the automaton class...
Dawid On Mon, Apr 4, 2011 at 1:39 PM, Andrzej Bialecki <[email protected]> wrote: > On 4/4/11 1:26 PM, Dawid Weiss wrote: >> >> Yeah, I know, but you create a subfile in that folder and in case of >> FSDirectory a subfolder would be created for the automaton... so for >> 'parent' you'd have something like: >> >> parent/fstlookup/fst.file >> >> Can it look this way or is: >> >> parent/fst.file >> >> more suitable? This is most likely a matter of taste, but I wanted to >> confirm it first. > > I think that no-one should be looking in that folder unless they want to > implement their own lookup (and then he just needs to avoid a name clash) or > need to debug things. I think that if you need to create a bunch of files > for your Lookup then it's better if they are in a subdir, so as not to mix > them with data files from other Lookup-s. > > > -- > Best regards, > Andrzej Bialecki <>< > ___. ___ ___ ___ _ _ __________________________________ > [__ || __|__/|__||\/| Information Retrieval, Semantic Web > ___|||__|| \| || | Embedded Unix, System Integration > http://www.sigram.com Contact: info at sigram dot com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
