Re: [hibernate-dev] hsearch-69 Purge

2007-08-15 Thread Emmanuel Bernard
You should not need to have access, I think. Workers from the WorkerFactory take entity and work type. All of them are stored by the BatchedQueueingProcessor Then before tx commit, QueueingProcessor.prepareWorks prepare the queue and create Lucene specific works (queue of LuceneWork). after tx

[hibernate-dev] hsearch-69 Purge

2007-08-15 Thread John Griffin
By default the WorkerFactory creates a TransactionalWorker. How can I set up the Configuration object in my tests so that the SearchFactory will return an instance of LuceneWorker? This is critical to the Purge implementation. Thx, John G. ___ hi

Re: [hibernate-dev] HSEARCH-69 Purge a class from index

2007-08-08 Thread Emmanuel Bernard
You should reuse as much as possible the Work infrastructure. Probably adding a new WorkType.PURGE Pretty much how WorkType.INDEX is done, I guess There is 2 types of purge however, purge by class and id, ie purge a given document, or purge the whole index(es) by class. I also mentionned thw

[hibernate-dev] HSEARCH-69 Purge a class from index

2007-08-07 Thread John Griffin
Everyone, I'm starting on HSEARCH-69. Emmanuel, what were you saying last night about the way you wanted me to look at this? I can't log IM messages so I need the pointers again. I remember I'll have to look at the code because I was unfamiliar with the classes you mentioned but I don't rememb