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). > > The index must be updated, when a CAS is added and when a CAS is changed. > That should be simple to do. Then we have a search method which returns a > list > of matched CAS references, that should also be easy to implement with > Lucene APIs. > > Would be nice if you can open a jira for this, and then attach a patch. > > To implement a task queue I think we should use a DB table to keep track of > what should be handed out, and what was already sent to a client. In case > an > item is not returned in time, we might need to reschedule it. > > I think it would be good to create three jiras: > - one to add search support based on Lucas > - one to use derby for CAS persistence instead of the simple java.util.Map > used by the dummy > - and one issue to add support to create a task queue > > What do you think? > It sounds good, I'll open such jiras. Regards, Tommaso
