nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-259) Framework should offer Processors/extensions a way to manage simple state
Date Wed, 13 Jan 2016 22:20:39 GMT

    [ https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097134#comment-15097134
] 

ASF subversion and git services commented on NIFI-259:
------------------------------------------------------

Commit 1a7e6c735d0dc458fd99e825f6659483b148d418 in nifi's branch refs/heads/NIFI-259 from
[~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1a7e6c7 ]

NIFI-259:
- Exsuring the component state css file is included in aggregated builds.


> 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
>            Assignee: Mark Payne
>             Fix For: 0.5.0
>
>
> 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)

Mime
View raw message