nifi git commit: NIFI-4116: Allow fields of Record returned from Lookup Service to be placed into record in the input, instead of requiring that the 'wrapper record' returned from Lookup be included

[jwing]

Repository: nifi
Updated Branches:
  refs/heads/master 20a6374bf -> bfd6c0aef


NIFI-4116: Allow fields of Record returned from Lookup Service to be placed 
into record in the input, instead of requiring that the 'wrapper record' 
returned from Lookup be included

Signed-off-by: James Wing 

This closes #2110.


Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/bfd6c0ae
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/bfd6c0ae
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/bfd6c0ae

Branch: refs/heads/master
Commit: bfd6c0aef768f53be8fdea62afdcd5404099e089
Parents: 20a6374
Author: Mark Payne 
Authored: Fri Aug 25 16:22:43 2017 -0400
Committer: James Wing 
Committed: Tue Sep 5 21:29:16 2017 -0700

--
 .../nifi/processors/standard/LookupRecord.java  |  56 +-
 .../processors/standard/TestLookupRecord.java   | 173 +++
 2 files changed, 224 insertions(+), 5 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/nifi/blob/bfd6c0ae/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/LookupRecord.java
--
diff --git 
a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/LookupRecord.java
 
b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/LookupRecord.java
index 10539bc..286f7ee 100644
--- 
a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/LookupRecord.java
+++ 
b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/LookupRecord.java
@@ -95,6 +95,11 @@ public class LookupRecord extends 
AbstractRouteRecord

[jira] [Resolved] (MINIFI-248) Create PostHTTP Processor

[Andrew Christianson (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFI-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Christianson resolved MINIFI-248.

Resolution: Implemented

Closed; all the functionality of PostHTTP is essentially provided by InvokeHTTP.

> Create PostHTTP Processor
> -
>
> Key: MINIFI-248
> URL: https://issues.apache.org/jira/browse/MINIFI-248
> Project: Apache NiFi MiNiFi
>  Issue Type: Task
>  Components: C++, Extensions
>Reporter: John Reynolds
>
> Create a PostHTTP processor of similar design/function to the PostHTTP in the 
> parent Apache NiFi project.
> Being a part of MiNiFi, the client should be very lightweight.  Intent is to 
> use Civet since that dependency is already a part of the MiNiFi footprint.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFI-339) Begin building controlling API to facilitate control of agents

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFI-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153988#comment-16153988
 ] 

ASF GitHub Bot commented on MINIFI-339:
---

GitHub user phrocker opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/134

MINIFI-339: Add C2 base allowing for 1 protocol and n heartbeat repor…

…ters

MINIFI-339: Add GetTCP Processor
MINIFI-339: Add listener server
MINIFI-339: Update to listener
MINIFI-339: Resolve Issue with stack based processor nodes losing scope

MINIFI-369: Update ListenHTTP processor to allow transfer encoding

MINIFI-339: Update rest receiver instantiation and fix issue found in 
GetFile

MINIFI-339: Rename content to operational arguments

MINIFI-371: remove virtual destructors when not needed

MINIFI-339: Fixing issues with GetTCP

MINIFI-378: Resolve issues with shutdown. Took the approach to call 
notifyStop at the destructor to avoid larger changes

MININFI-339: fix broken test

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
 in the commit message?

- [ ] Does your PR title start with MINIFI- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file?
- [ ] If applicable, have you updated the NOTICE file?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

$ git pull https://github.com/phrocker/nifi-minifi-cpp MINIFI-339

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

https://github.com/apache/nifi-minifi-cpp/pull/134.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 #134


commit 3ab73825efb19e8e5c3a2b8163971e8c0db4b192
Author: Marc Parisi 
Date:   2017-06-21T14:47:35Z

MINIFI-339: Add C2 base allowing for 1 protocol and n heartbeat reporters
MINIFI-339: Add GetTCP Processor
MINIFI-339: Add listener server
MINIFI-339: Update to listener
MINIFI-339: Resolve Issue with stack based processor nodes losing scope

MINIFI-369: Update ListenHTTP processor to allow transfer encoding

MINIFI-339: Update rest receiver instantiation and fix issue found in 
GetFile

MINIFI-339: Rename content to operational arguments

MINIFI-371: remove virtual destructors when not needed

MINIFI-339: Fixing issues with GetTCP

MINIFI-378: Resolve issues with shutdown. Took the approach to call 
notifyStop at the destructor to avoid larger changes

MININFI-339: fix broken test




> Begin building controlling API to facilitate control of agents
> --
>
> Key: MINIFI-339
> URL: https://issues.apache.org/jira/browse/MINIFI-339
> Project: Apache NiFi MiNiFi
>  Issue Type: New Feature
>  Components: C++
>Reporter: marco polo
>Assignee: marco polo
>Priority: Critical
>  Labels: Durability, Reliability, Statistics
>
> Begin building the controlling API in MiNiFi C++. This API will evolve and 
> likely have public and private elements. As development progresses we may 
> want more capabilities. 
> What I want to create as a straw man will be basic control and metrics 
> gathering
> -- Start
> -- Stop
> -- Pause
> -- Gather metrics
>** Throughput of of flow components
>** Execution time ( run time minus sleep time )
>** Memory consumption
> -- Drain repositories
> -- Switch repository types. 
> Better employ update listener within this controlling API



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFI-248) Create PostHTTP Processor

[John Reynolds (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFI-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153948#comment-16153948
 ] 

John Reynolds commented on MINIFI-248:
--

[~achristianson],

I concur.

> Create PostHTTP Processor
> -
>
> Key: MINIFI-248
> URL: https://issues.apache.org/jira/browse/MINIFI-248
> Project: Apache NiFi MiNiFi
>  Issue Type: Task
>  Components: C++, Extensions
>Reporter: John Reynolds
>
> Create a PostHTTP processor of similar design/function to the PostHTTP in the 
> parent Apache NiFi project.
> Being a part of MiNiFi, the client should be very lightweight.  Intent is to 
> use Civet since that dependency is already a part of the MiNiFi footprint.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFI-248) Create PostHTTP Processor

[Andrew Christianson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFI-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153727#comment-16153727
 ] 

Andrew Christianson commented on MINIFI-248:


Suggesting we close this one as InvokeHTTP covers this functionality.

> Create PostHTTP Processor
> -
>
> Key: MINIFI-248
> URL: https://issues.apache.org/jira/browse/MINIFI-248
> Project: Apache NiFi MiNiFi
>  Issue Type: Task
>  Components: C++, Extensions
>Reporter: John Reynolds
>
> Create a PostHTTP processor of similar design/function to the PostHTTP in the 
> parent Apache NiFi project.
> Being a part of MiNiFi, the client should be very lightweight.  Intent is to 
> use Civet since that dependency is already a part of the MiNiFi footprint.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MINIFI-374) Create integration tests for HTTPS communication

[Andrew Christianson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFI-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153671#comment-16153671
 ] 

Andrew Christianson edited comment on MINIFI-374 at 9/5/17 1:53 PM:


The code for this is ready, but relies on 
MINIFI-350/https://github.com/apache/nifi-minifi-cpp/pull/126.


was (Author: achristianson):
This is done, but relies on 
MINIFI-350/https://github.com/apache/nifi-minifi-cpp/pull/126.

> Create integration tests for HTTPS communication
> 
>
> Key: MINIFI-374
> URL: https://issues.apache.org/jira/browse/MINIFI-374
> Project: Apache NiFi MiNiFi
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>
> Create automated tests to verify that HTTPS communications work as intended. 
> Tests will need to generate certificates.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFI-374) Create integration tests for HTTPS communication

[Andrew Christianson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFI-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153671#comment-16153671
 ] 

Andrew Christianson commented on MINIFI-374:


This is done, but relies on 
MINIFI-350/https://github.com/apache/nifi-minifi-cpp/pull/126.

> Create integration tests for HTTPS communication
> 
>
> Key: MINIFI-374
> URL: https://issues.apache.org/jira/browse/MINIFI-374
> Project: Apache NiFi MiNiFi
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>
> Create automated tests to verify that HTTPS communications work as intended. 
> Tests will need to generate certificates.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFI-350) Create integration tests for cpp docker image

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFI-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153662#comment-16153662
 ] 

ASF GitHub Bot commented on MINIFI-350:
---

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/126
  
Added docs to docker/test/integration/README.md.


> Create integration tests for cpp docker image
> -
>
> Key: MINIFI-350
> URL: https://issues.apache.org/jira/browse/MINIFI-350
> Project: Apache NiFi MiNiFi
>  Issue Type: Bug
>  Components: C++
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>
> Create a unit test suite which uses compose or docker commands to set up 
> minifi using the docker image and send data through test flows. Consider 
> looking into existing test frameworks/harnesses.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFI-350) Create integration tests for cpp docker image

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFI-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153659#comment-16153659
 ] 

ASF GitHub Bot commented on MINIFI-350:
---

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

https://github.com/apache/nifi-minifi-cpp/pull/126#discussion_r136992525
  
--- Diff: README.md ---
@@ -124,6 +133,8 @@ $ brew install cmake \
   doxygen
 $ brew install curl
 $ brew link curl --force
+$ # (Optional) for building docker image/running system integration tests
+$ # Install docker using instructions at 
https://docs.docker.com/docker-for-mac/install/
--- End diff --

Fixed. Added instruction to pip install virtualenv.


> Create integration tests for cpp docker image
> -
>
> Key: MINIFI-350
> URL: https://issues.apache.org/jira/browse/MINIFI-350
> Project: Apache NiFi MiNiFi
>  Issue Type: Bug
>  Components: C++
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>
> Create a unit test suite which uses compose or docker commands to set up 
> minifi using the docker image and send data through test flows. Consider 
> looking into existing test frameworks/harnesses.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)