[GitHub] incubator-nifi pull request: NIFI - 121

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-nifi pull request: NIFI - 121

JPercivall
GitHub user ajaybhat opened a pull request:

    https://github.com/apache/incubator-nifi/pull/10

    NIFI - 121

    When MergeContent is configured to perform Binary Concatenation, if
    generating bundle of 1 FlowFile, should just Clone original FLowFile
    instead of copying data
   
    This is more efficient.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ajaybhat/incubator-nifi NIFI-121

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-nifi/pull/10.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #10
   
----
commit 196d60aed63b4853cfde7493879924c557a13a4d
Author: Ajay Bhat <[hidden email]>
Date:   2015-01-15T18:28:07Z

    NIFI - 121
   
    When MergeContent is configured to perform Binary Concatenation, if
    generating bundle of 1 FlowFile, should just Clone original FLowFile
    instead of copying data
   
    This is more efficient.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-nifi pull request: NIFI - 121

JPercivall
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-nifi/pull/10


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---