Hey Mark, Good to see you. I'm specifically talking about GetSplunk Processor which we use to pull data previous 15 minutes data(earliest time: -15m@m and latest time: now()) from the Splunk Enterprise every 15 mins. The processor absolutely works fine. But it is Splunk with which we have issues of getting down so that we miss data when it is down. So trying to find a way of backfilling the data. Does this makes sense? Let me know if you have further questions.
On 2022/01/11 22:36:39 "Chirthani, Deepak Reddy" wrote: > Hello, > > Is Nifi good at Backfilling the data? Let's say that I have a dataflow which > is cron scheduled to run every 15 mins. Lets say that the source was down and > the dataflow did not pulled any data for a couple of runs and after some time > the source is up and running. If this happens frequently, how do you handle > backfilling in Nifi? Please let me know if there is any automated way of > doing this? > > Thanks > E-MAIL CONFIDENTIALITY NOTICE: > The contents of this e-mail message and any attachments are intended solely > for the addressee(s) and may contain confidential and/or legally privileged > information. If you are not the intended recipient of this message or if this > message has been addressed to you in error, please immediately alert the > sender by reply e-mail and then delete this message and any attachments. If > you are not the intended recipient, you are notified that any use, > dissemination, distribution, copying, or storage of this message or any > attachment is strictly prohibited. > E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.
