2011/6/30 Jörn Kottmann <[email protected]>
> On 6/30/11 12:18 PM, Tommaso Teofili wrote: > >> 2011/6/29 Jörn Kottmann<[email protected]> >> >> On 6/29/11 3:51 PM, Tommaso Teofili wrote: >>> >>> I think I can better help with the Corpus Server, as I've also some >>>> experience with Lucene (by the way, I imagine Lucas could be used to >>>> save >>>> CASes inside the index) I think I can help with CAS searching and task >>>> queueing (with UIMA AAE process). >>>> >>>> +1, I am pretty sure we can reuse Lucas, or eventually adapt a little >>> to be >>> suitable for our needs. We need to have one index loaded and concurrently >>> update and query it. Maybe we need to modify Lucas a little to give as a >>> reference >>> to the index its writing the CASes to. >>> >>> right, I will start inspecting if it's worth modifying it or rewrite a >> new >> component; it may be useful also to switch it to latest Lucene (as it's >> 2.9.3 now). >> >> > I hope the required changes to Lucas are not that big, it already contains > a lot of functionality we need, for example Type System to Lucene Index > mapping. > > > I tried to have a look some weeks ago, the most important change is in the new declarative Token API used in Lucene 3+ however it should not be so hard. Regarding Apache Derby "CorpusStore" I think it'd be good to create a CorpusStore interface so that implementations can be created/switched easily in the future. Tommaso
