I question this point: "But, if only an optimize has happened (the data in the index didn't change), the component doesn't need to be modified"
An optimize may, for instance, change the internal Lucene document IDs. What is your component doing? Also, optimize should be a fairly rare occurrence. I'm wondering if it's worth the hassle to detect it. Best Erick On Wed, Jul 6, 2011 at 3:37 AM, gquaire <gquaire....@gmail.com> wrote: > Hello everybody, > > I am new in this forum and I need your expertize on Solr-Lucene. > I'm currently develop a new component for Solr for a professional project. > This component has to be refreshed when some mofications have been applied > in the index. But, if only an optimize has happened (the data in the index > didn't change), the component doesn't need to be modified. To do that, I'm > testing the version number stored in the index which can be retrieved by the > IndexReader class with "IndexReader.getCurrentVersion()". But, I need to > know if the version number is incremented after an optimize operation. Can > you tell me if it is the case? > If it is, how can I detect that the data have changed in the index ? > > Thanks for your help! > > gquaire > > > > ----- > Jouve ITS France > -- > View this message in context: > http://lucene.472066.n3.nabble.com/the-version-of-a-Lucene-index-changes-after-an-optimize-tp3143822p3143822.html > Sent from the Solr - User mailing list archive at Nabble.com. >
