I think this would be useful. The other day I hit this problem of fq=.... not working. It turned out that the schema was changed (some non-indexed fields were made indexed), the bulk upload was done, but that bulk upload left the old index files in place, so ended up with "double index" within the same index dir.
Otis ----- Original Message ---- From: Ryan McKinley <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Wednesday, June 13, 2007 3:40:52 PM Subject: Re: Delete entire index >> : >> : Actually, it's not quite equivalent if there was a schema change. >> : There are some "sticky" field properties that are per-segment global. >> : For example, if you added omitNorms="true" to a field, then did >> >> Hmmm... I thought the optimize would take care of that? > > Oh yes, sorry, I was thinking about optimize after you reindexed. If > you forget to do optimize, you get a different index though... > definitely spooky stuff to someone not expecting it. > Is there an easy way to check if the lucene per/field properties are out of sync with the solr schema? If so, maybe we should display it on the admin page. Are there other sticky field properties besides omitNorms? I know I have made changes to a production server where I: 1. change the field definition for a field 2. get the last indexed time for a document of that type 3. index all documents of that type 4. delete everything of that type not addded since the start time 5. optimize It appeared to work fine...
