:
: 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...
