[jira] [Commented] (NIFI-799) GetTwitter allows buffering of too much data

["Mark Payne (JIRA)" <ji...@apache.org>]

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

Mark Payne commented on NIFI-799:
---------------------------------

Both NIFI-831 and NIFI-799 were addressed in this patch, which was OK'd in NIFI-831. Both were addressed in a single patch because this ticket was a 1-line change that was also being changed in NIFI-831 anyway. Closing this ticket, as it is being pushed along with NIFI-831.

> GetTwitter allows buffering of too much data
> --------------------------------------------
>
>                 Key: NIFI-799
>                 URL: https://issues.apache.org/jira/browse/NIFI-799
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 0.3.0
>
>         Attachments: 0001-NIFI-831-NIFI-799-Fixed-a-NullPointerException-use-a.patch
>
>
> GetTwitter uses the hosebird client, which takes a BlockingQueue that it can use to put all tweets on. The BlockingQueue currently has a max capacity of 100,000, but on small heaps that can be problematic by causing OutOfMemoryError. We need to reduce that considerably, to about 10,000 or maybe even 1,000.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)