[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker thanks for the help ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @minifirocks thanks! I'll merge to master at some point today ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker @apiri please take a look and see whether you can merge the PR to master. i tested the site2site as above. ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker test the site2site, NiFi receive the right header/footer/demarcator ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker let me test the NiFi site2site to double check ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker i tie the merge processor to a put file processor to save the content ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @minifirocks What did you use to open it? The procedure is the same, but the interpretation of that data is not. Seems that we need to at least verify that NiFi can interpret what we send it. ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker i did not send the file over site2site, i save to a file and i can open it for read OK. the sending of these flowfile is the same procedure that we use to send normal flow files. ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @minifirocks I did have a question that popped up after I hit approvewith the header and footer you're serializing the data directly. Did you have any issues when opening those merged content files in NiFi after it was sent via Site To Site? ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker @apiri please let me know whether it can be merged to master. ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker rebased ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @minifirocks Can you rebase against master? Your commits have unrelated content. ---
[GitHub] nifi-minifi-cpp issue #133: MINIFICPP-67: Merge Content processor
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/133 @phrocker @apiri please approve the same, i would like to merge that before i add the compression/tar support for merge content. ---
