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

Aldrin Piri commented on NIFI-259:
----------------------------------

[~markap14] Just as a heads up, I'm going to dig in and start working on 
resolving some of these items with the setup I have currently and will throw 
them on an associated branch for review/cherrypicking as appropriate.

Found the issue with the response above being a bad connect string (in that I 
was literally providing a quoted string).  Will look to bolster some of the 
property handling with this and see how it is used

> 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
>
>         Attachments: error-message.png
>
>
> 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)

Reply via email to