On 6/1/2012 11:51 AM, Savvas Andreas Moysidis wrote:
Hello,
Driven by the same requirements we also implemented the same polling
mechanism (in java) and found it a bit awkward and error prone having
to search through the returned response for occurrences of the terms
"failure" or "Rollback" etc.
Hello,
Driven by the same requirements we also implemented the same polling
mechanism (in java) and found it a bit awkward and error prone having
to search through the returned response for occurrences of the terms
"failure" or "Rollback" etc.
It would be *really* handy if the status command retur
thank you ALL for the great feedback - very much appreciated!
--
View this message in context:
http://lucene.472066.n3.nabble.com/possible-status-codes-from-solr-during-a-DIH-data-import-process-tp3987110p3987263.html
Sent from the Solr - User mailing list archive at Nabble.com.
there is at least one scenario where no error is reported when it should be,
if the host runs out of disk when optimizing, it is not reported.
There is a jira issue open I think
--
View this message in context:
http://lucene.472066.n3.nabble.com/possible-status-codes-from-solr-during-a-DIH-data-
Hi,
Thats correct.
For failure, you have to check for the text *"Indexing failed. Rolled back
changes"* under the tag.
One more thing to note here is that there may be a time during the indexing
process where the indexing is complete but the index is not committed and
optimized yet.
You would nee
You've got it right. Here's a summary:
- "status" = "busy" means its in-process.
- "status" = "idle" means its finished (success or failure).
- You can drill down further by looking at sub-elements under "statusMessages" :
> if there is , it means the last import was cancelled
> with "comma
