[jira] [Commented] (NIFI-7934) FetchS3Object processor should support range requesting

2020-10-16 Thread Lucas Moten (Jira)


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

Lucas Moten commented on NIFI-7934:
---

Determined to be a duplicate of NIFI-7886

> FetchS3Object processor should support range requesting
> ---
>
> Key: NIFI-7934
> URL: https://issues.apache.org/jira/browse/NIFI-7934
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Lucas Moten
>Priority: Minor
>  Labels: AWS, pull-request-available
>   Original Estimate: 24h
>  Time Spent: 40m
>  Remaining Estimate: 23h 20m
>
> The existing FetchS3Object processor currently retrieves the entire content 
> of the object from S3.  This can be problematic for flows running on 
> constrained resources where limited storage space is available on the host.  
> To mitigate, and provide for more opportunity for parallel flowfile 
> processing, it would be helpful if the FetchS3Object processor exposed the 
> ability to range request the content.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (NIFI-7934) FetchS3Object processor should support range requesting

2020-10-16 Thread Lucas Moten (Jira)


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

Lucas Moten resolved NIFI-7934.
---
Resolution: Duplicate

> FetchS3Object processor should support range requesting
> ---
>
> Key: NIFI-7934
> URL: https://issues.apache.org/jira/browse/NIFI-7934
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Lucas Moten
>Priority: Minor
>  Labels: AWS, pull-request-available
>   Original Estimate: 24h
>  Time Spent: 40m
>  Remaining Estimate: 23h 20m
>
> The existing FetchS3Object processor currently retrieves the entire content 
> of the object from S3.  This can be problematic for flows running on 
> constrained resources where limited storage space is available on the host.  
> To mitigate, and provide for more opportunity for parallel flowfile 
> processing, it would be helpful if the FetchS3Object processor exposed the 
> ability to range request the content.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (NIFI-7934) FetchS3Object processor should support range requesting

2020-10-15 Thread Lucas Moten (Jira)


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

Lucas Moten commented on NIFI-7934:
---

A pull request has been opened here https://github.com/apache/nifi/pull/4607

> FetchS3Object processor should support range requesting
> ---
>
> Key: NIFI-7934
> URL: https://issues.apache.org/jira/browse/NIFI-7934
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Lucas Moten
>Priority: Minor
>  Labels: AWS, pull-request-available
>   Original Estimate: 24h
>  Time Spent: 10m
>  Remaining Estimate: 23h 50m
>
> The existing FetchS3Object processor currently retrieves the entire content 
> of the object from S3.  This can be problematic for flows running on 
> constrained resources where limited storage space is available on the host.  
> To mitigate, and provide for more opportunity for parallel flowfile 
> processing, it would be helpful if the FetchS3Object processor exposed the 
> ability to range request the content.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (NIFI-7934) FetchS3Object processor should support range requesting

2020-10-15 Thread Lucas Moten (Jira)
Lucas Moten created NIFI-7934:
-

 Summary: FetchS3Object processor should support range requesting
 Key: NIFI-7934
 URL: https://issues.apache.org/jira/browse/NIFI-7934
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Extensions
Reporter: Lucas Moten


The existing FetchS3Object processor currently retrieves the entire content of 
the object from S3.  This can be problematic for flows running on constrained 
resources where limited storage space is available on the host.  To mitigate, 
and provide for more opportunity for parallel flowfile processing, it would be 
helpful if the FetchS3Object processor exposed the ability to range request the 
content.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (NIFI-5595) Add filter to template endpoint

2020-06-29 Thread Lucas Moten (Jira)


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

Lucas Moten commented on NIFI-5595:
---

I may have encountered a bug on this, or else I'm misconfigured and could 
benefit from the outcomes of NIFI-6080.  But I have a feeling that the CORS 
check is not handling the port the call is made on when coming through a proxy. 
 My current workaround is to force the Origin header in Nginx to be 
[https://127.0.0.1|https://127.0.0.1/] without specifying the port that NiFi 
itself is listening on.

> Add filter to template endpoint
> ---
>
> Key: NIFI-5595
> URL: https://issues.apache.org/jira/browse/NIFI-5595
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.7.1
>Reporter: Nathan Gough
>Assignee: Nathan Gough
>Priority: Major
>  Labels: cors, security
> Fix For: 1.8.0
>
>
> The template endpoint needs a CORS filter applied.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)