nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-1816) HandleHTTPResponse Processor Provenance
Date Fri, 29 Apr 2016 07:07:12 GMT

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

ASF GitHub Bot commented on NIFI-1816:
--------------------------------------

Github user pvillard31 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/389#discussion_r61540826
  
    --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpResponse.java
---
    @@ -169,6 +174,7 @@ public void onTrigger(final ProcessContext context, final ProcessSession
session
                 return;
             }
     
    +        session.getProvenanceReporter().send(flowFile, flowFile.getAttribute(HTTP_REQUEST_URI),
stopWatch.getElapsed(TimeUnit.MILLISECONDS));
    --- End diff --
    
    @markap14 Would you agree with a URI as below?
    < http|https >://< ip client >@<ip server>:< port >/< target
>
    
    That would give something like:
    http://192.168.1.14@192.168.1.15:/test
    
    This way, the URI could be the same on both HandleHttpRequest and HandleHttpResponse.
What do you think?
    
    I can fix URI in both processors using this JIRA (with an update) or open a new one.


> HandleHTTPResponse Processor Provenance
> ---------------------------------------
>
>                 Key: NIFI-1816
>                 URL: https://issues.apache.org/jira/browse/NIFI-1816
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.6.1
>         Environment: Centos6
>            Reporter: Sam Hjelmfelt
>            Assignee: Pierre Villard
>            Priority: Minor
>
> The HandleHTTPResponse processor only creates provenance events for auto-terminated relationships
(i.e. drop events). It should also create send events.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message