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. Dawid On Mon, Apr 4, 2011 at 11:40 AM, Andrzej Bialecki <[email protected]> wrote: > On 4/4/11 11:29 AM, Dawid Weiss wrote: >> >> Hi guys. FST currently uses IndexInput/IndexOutput to perform >> serialization and the suggester framework expects a single file. Is >> there any nice way to do this? I ask because I considered these, but >> they all seem clumsy: >> >> a) serialize suggester data to a subfolder (using regular >> FSDirectory); this would be different than other suggesters, >> b) use FSDirectory, serialize using this and then move the file from a >> subfolder, then delete it. >> c) use custom subclasses of IndexInput IndexOutput that accept a >> simple File and serialize directy. >> >> At the moment I use option (c), actually, but better hints would be >> welcome. > > Suggester expects a File, but both Jaspell and TST actually use this File as > a parent directory name where they store their data. > > > -- > 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]
