You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Casey Stella (JIRA)" <ji...@apache.org> on 2017/06/27 09:13:01 UTC

[jira] [Updated] (METRON-965) In the case where we specify the syncpolicy in the HDFS Writer, we do not properly clone and end up syncing for every record

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

Casey Stella updated METRON-965:
--------------------------------
    Fix Version/s: 0.4.0

> In the case where we specify the syncpolicy in the HDFS Writer, we do not properly clone and end up syncing for every record
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: METRON-965
>                 URL: https://issues.apache.org/jira/browse/METRON-965
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Casey Stella
>            Assignee: Casey Stella
>             Fix For: 0.4.0
>
>
> Right now the SyncPolicy works as follows:
> * If you specify the sync policy in the flux file, it will use that policy to determine when to sync the HDFS Writer.
> * If you do not, then it will create a count sync policy based on the batch size.  
> In the first case, we are not creating the sync policy properly and end up sync'ing per record, which has performance impact and is incorrect.



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