[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552117#comment-14552117
]
Toivo Adams commented on NIFI-259:
----------------------------------
What is the lifetime of such state?
Only temporary during processor is activate?
Or should state be available longer period?
Intent is to limit how much information processor can store?
(nr of items and String length)
So it should be small and very fast.
It's restrictive to allow only simple primitive values and String values, but
other object size is more difficult to keep under control.
State storage should be pluggable to allow different implementations?
First implementation can be simple in memory HashMap?
And other implementations may offer different performance / size / fault
tolerant characteristics.
Every processor instance has its own storage which can be accessed from this
processor only?
Thanks
Toivo
> Framework should offer Processors/extensions a way to manage simple state
> -------------------------------------------------------------------------
>
> Key: NIFI-259
> URL: https://issues.apache.org/jira/browse/NIFI-259
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Joseph Witt
>
> It is not uncommon for processors to need managed state which persists
> across restarts. One good example of this is the GetHTTP processor which
> needs to save state of the last cache/e-tag information it received from the
> server it interacts with so that it can avoid constantly pulling an unchanged
> resource.
> Rather than making processors roll their own persistant state management
> perhaps we can offer something to them via the ProcessContext which will
> allow them to save simple primitive values and limited length Strings which
> are local to that node and which are local to that processor only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
