[
https://issues.apache.org/jira/browse/MINIFICPP-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698587#comment-16698587
]
ASF GitHub Bot commented on MINIFICPP-682:
------------------------------------------
Github user arpadboda commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/448#discussion_r236149200
--- Diff: nanofi/src/api/nanofi.cpp ---
@@ -223,13 +226,15 @@ void free_flowfile(flow_file_record *ff) {
return;
}
auto content_repo_ptr =
static_cast<std::shared_ptr<minifi::core::ContentRepository>*>(ff->crp);
- if (content_repo_ptr->get()) {
+ if (content_repo_ptr->get() && (ff->keepContent == 0)) {
--- End diff --
@phrocker : I don't link this, but I have no better idea yet. We provide a
flow_file_record to access content and attributes in the processor logic
callback. This means that the content cannot be deleted in case the flowfile is
transfered via a relationship.
> C API: provide functions to create custom processors
> ----------------------------------------------------
>
> Key: MINIFICPP-682
> URL: https://issues.apache.org/jira/browse/MINIFICPP-682
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Arpad Boda
> Assignee: Arpad Boda
> Priority: Major
> Labels: CAPI, nanofi
> Fix For: 0.6.0
>
>
> Extend C API to:
> -Provide functions that can be used used to implement custom processor.
> -Custom processor should be able to read/update both the content and the
> attributes of flowfile, route to "failure" and "success" relationships.
> -API should support adding these custom processors to flows and invoke them
> as standalones, too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
