Eric,
The 200 million docs are all large as they are content indexed. Also it
would be hard to convince the customer to rebuild their index. But more
than that, I also want to clear my understanding on this topic and know if
it’s an expected behaviour for a distributed update processor to not call
_Why_ is reindexing not an option? 200M doc isn't that many.
Since you have Atomic updates working, you could easily
write a little program that pulled the docs from you existing
collection and pushed them to a new one with the new schema.
Do use CursorMark if you try that You have to be ready
Eric, Markus,
Thank you for your inputs. I made sure that the jar file is found correctly
since the core reloads fine and also prints the log lines from my processor
during update request (getInstane() method of the update factory). The
reason why I want to insert the processor between distributed
It Depends (tm). This is a little confused. Why do you have
distributed processor in stand-alone Solr? Stand-alone doesn't, well,
distribute updates so that seems odd. Do try switching it around and
putting it on top, this should be OK since distributed is irrelevant.
You can also just set a break
Hello Rahul,
I don't know why you don't see your logs lines, but if i remember correctly,
you must put all custom processors above Log, Distributed and Run, at least i
remember i read it somewhere a long time ago.
We put all our custom processors on top of the three default processors and
they
