-
1. Re: Transaction/Batch With Jboss Searchable cache is not wor
manik Mar 18, 2009 12:40 PM (in response to kmarikkani)Someone has just raised a JIRA on this:
https://jira.jboss.org/jira/browse/JBCACHE-1495
Can you confirm that this is what you are seeing as well? -
2. Re: Transaction/Batch With Jboss Searchable cache is not wor
seahawk Mar 18, 2009 1:57 PM (in response to kmarikkani)I just added there one more comment: the index directory after the transaction seems to be not updated .. so that's the reason for the empty query collection ..
cheers
Y -
3. Re: Transaction/Batch With Jboss Searchable cache is not wor
kmarikkani Mar 19, 2009 5:35 AM (in response to kmarikkani)"manik.surtani@jboss.com" wrote:
Someone has just raised a JIRA on this:
https://jira.jboss.org/jira/browse/JBCACHE-1495
Can you confirm that this is what you are seeing as well?
Yes.But if i am setting the property "hibernate.search.worker.batch_size" to 1 to the searchable configuration ,search is working fine.
One morething, while adding or updating the Object to cache, the index is getting updated properly.But if i am removing the Objects from Cache, the index is not Updating properly.
Thanks,
marikkani.K -
4. Re: Transaction/Batch With Jboss Searchable cache is not wor
seahawk Mar 19, 2009 10:15 AM (in response to kmarikkani)"kmarikkani" wrote:
Yes.But if i am setting the property "hibernate.search.worker.batch_size" to 1 to the searchable configuration ,search is working fine.
One morething, while adding or updating the Object to cache, the index is getting updated properly.But if i am removing the Objects from Cache, the index is not Updating properly.
Thanks,
marikkani.K
ok - same problem ... -
5. Re: Transaction/Batch With Jboss Searchable cache is not wor
navssurtani Mar 19, 2009 8:31 PM (in response to kmarikkani)Just a quick update on where we stand currently (appx 0030 UTC Fri 20th) -
The original listener wasn't picking up any events for the @NodeRemoved so temporarily I have created a separate listener with that annotation to deal with this.
I have a simple test that puts an object in, searches, then removes the node and searches again. That is successfully returning 0 objects in the second search.
The current issue, however is that even the new listener isn't picking up the annotation with your test. Both listeners are attached and even a simple log.debug() doesn't give any output.
I will be back online Friday afternoon and will be on IRC if anyone wishes to speak to me then.