Handle "404 Not Found" gracefully

[searchisko]

Handle "404 Not Found" gracefully

[velias]

I'm not sure if I understand exactly which REST call returns 404. You use scenario where river gets list of id's from main indexer REST call, and then do separate REST call for each item to get details? And 404 is returned for some items there?

[Starefossen]

Well, this can occur for all APIs in those cases where the item is deleted shortly after the river is trying to index the item.

For our API we are listing deleted items so that other systems can delete them from their indices without doing a complete reindex. Four our case it would have been nice if the river could delete 404 items from Elasticsearch – but a graceful handle where the river just ignores 404 items will suffice :)

[velias]

OK, so I'll improve river to ignore 404 returned from calls to the URL configured in remote/urlGetDocumentDetails and continue in indexing, not to fail whole indexing in this case.

But 404 returned for calls to URL's defined in remote/urlGetDocuments or remote/urlGetSpaces wil be treated as indexing error still.

[Starefossen]

That would be perfect @velias. Thank you!

[velias]

OK, code is updated. I'll release new version of plugin in few days.

[velias]

released