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

patrick white edited comment on NIFI-4862 at 11/19/18 9:29 PM:
---------------------------------------------------------------

[~mattyb149] [~ijokarumawak]

Hi Folks, would like to request your opinion, we're seeing this issue running 
on 1.6.0, is pulling Matt's PR #2605 into 1.6.0 a good approach?

The patch looks pretty clean to cherry-pick, and we're still testing for move 
to 1.7.0, so thought this approach may be viable until we can update.


was (Author: patwhitey2007):
[~mattyb149] [~ijokarumawak]

Hi Folks, would like to request your opinion, we're seeing this issue running 
on 1.6.0, is pulling Matt's PR #2605 into 1.6.0 a good approach?

The patch looks pretty clean to cherry-pick, and we're still testing for move 
to 1.7.0, so thought this approach may be viable until update.

> Copy original FlowFile attributes to output FlowFiles at SelectHiveQL 
> processor
> -------------------------------------------------------------------------------
>
>                 Key: NIFI-4862
>                 URL: https://issues.apache.org/jira/browse/NIFI-4862
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.5.0
>            Reporter: Jakub Leś
>            Assignee: Matt Burgess
>            Priority: Minor
>             Fix For: 1.7.0
>
>         Attachments: 
> 0001-NIFI-4862-Add-Copy-original-attributtes-to-SelectHiv.patch
>
>
> Hi, 
> Please add "Copy original attributes" to processor SelectHiveQL. Thanks to 
> that we can use HttpRequest and HttpResponse to synchronize fetching query 
> result in webservice.
>  
> UPDATED:
> SelectHiveQL creates new FlowFiles from Hive query result sets. When it also 
> has incoming FlowFiles, it should create new FlowFiles from the input 
> FlowFile, so that it can copy original FlowFile attributes to output 
> FlowFiles.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to