I am using the ScrollElasticsearchHttp NiFi processor to read all messages for a particular set of ElasticSearch indexes which I am then writing into a data warehouse after some processing. I know that there are about 25 mil records in total in the ElasticSearch indexes. After reading about 100 000 messages for example, the processor fails with: ScrollElasticsearchHttp[id=0b7cc9a1-0171-1000-ffff-ffffd34fb1b4] Elasticsearch returned code 404 with message Not Found I know that this 404 error is temporary/transient because when I query ElasticSearch directly through a browser, it returns content just fine. e.g. https://10.61.5.38:9200/my-index-name-*/_search?pretty How do I set the ScrollElasticsearchHttp processor to continue from the scrollid where the failure occurred, rather than clearing the state and starting reading from scratch again? When I view the state of the ScrollElasticsearchHttp processor, it shows me that it has stopped at a scrollid with a value of: DnF1ZXJ5VGhlbkZldGNoDAAAAAACYcPvFjhDa3VKV05lUUFXN2NGa2U1b1BQcncAAAAAAmHD7hY4Q2t1SldOZVFBVzdjRmtlNW9QUHJ3AAAAAAFmF00WS0NHRHhVNmZRM0NsLWN2a25tVUxCZwAAAAACkT4ZFmtWSTVoYlFTUzRhczl4R0VNN0RPd2cAAAAAAoSQgBZONWYtLTRjZVI2U0Y2bDUtUk1jbXlBAAAAAAKEkIEWTjVmLS00Y2VSNlNGNmw1LVJNY215QQAAAAABJZsGFjloWnN3VklXUlZxRnhrcUM1MS1USncAAAAAAk400RZWN0V6UFVKY1J6dXdGWHo5WURwSDJ3AAAAAAJONNIWVjdFelBVSmNSenV3Rlh6OVlEcEgydwAAAAABZhdOFktDR0R4VTZmUTNDbC1jdmtubVVMQmcAAAAAApE-GhZrVkk1aGJRU1M0YXM5eEdFTTdET3dnAAAAAABpJsMWaDJMbDZ6YmJSNEdLc3FiX09jMDNlQQ==">DnF1ZXJ5VGhlbkZldGNoDAAAAAACYcPvFjhDa3VKV05lUUFXN2NGa2U1b1BQcncAAAAAAmHD7hY4Q2t1SldOZVFBVzdjRmtlNW9QUHJ3AAAAAAFmF00WS0NHRHhVNmZRM0NsLWN2a25tVUxCZwAAAAACkT4ZFmtWSTVoYlFTUzRhczl4R0VNN0RPd2cAAAAAAoSQgBZONWYtLTRjZVI2U0Y2bDUtUk1jbXlBAAAAAAKEkIEWTjVmLS00Y2VSNlNGNmw1LVJNY215QQAAAAABJZsGFjloWnN3VklXUlZxRnhrcUM1MS1USncAAAAAAk400RZWN0V6UFVKY1J6dXdGWHo5WURwSDJ3AAAAAAJONNIWVjdFelBVSmNSenV3Rlh6OVlEcEgydwAAAAABZhdOFktDR0R4VTZmUTNDbC1jdmtubVVMQmcAAAAAApE-GhZrVkk1aGJRU1M0YXM5eEdFTTdET3dnAAAAAABpJsMWaDJMbDZ6YmJSNEdLc3FiX09jMDNlQQ==
... View more
