[
https://issues.apache.org/jira/browse/QUARKS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315101#comment-15315101
]
Victor Dogaru commented on QUARKS-192:
--------------------------------------
Have you looked at Apache NiFi? It seems to provide persistence for its
dataflows (see the ContentRepository in
http://nifi.apache.org/docs/nifi-docs/html/overview.html#nifi-architecture), so
maybe it could be integrated with Quarks to provide flow storage for long term
disconnections.
> event resiliency
> ----------------
>
> Key: QUARKS-192
> URL: https://issues.apache.org/jira/browse/QUARKS-192
> Project: Quarks
> Issue Type: Improvement
> Reporter: Jerome Chailloux
>
> Assuming that I have a Raspberry Pi that ingest data and doing some aggregate.
> I have to send information to Watson IoT.
> What if if I lost the network ?
> Could we have a mechanism that send data at all time and if network is not
> available store all events in a file ?
> As soon as the network is available again play back the file and send new
> events.
> We have to be sure that all events are sent in the correct order from file to
> "real time".
> The computation engine (IBM Streams in this case) will then apply some
> policies to deal with or not with out of order events for the real time
> computation but at least able to store data received from sensors.
> Any idea about how to achieve this ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
