[jira] [Commented] (METRON-955) Make the default sync policy for HDFS Writer be based on the batch size

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on METRON-955:
---------------------------------------

GitHub user cestella opened a pull request:

    https://github.com/apache/metron/pull/589

    METRON-955: Make the default sync policy for HDFS Writer be based on the batch size

    ## Contributor Comments
    Right now, we do a sync per record written in HDFS. This has performance penalties as it requires a Namenode contact. We get around this by letting the user define the sync policy in Flux, but that's less convenient and more sensible defaults could be created. We should use the batch size as a sensible default for the sync policy (i.e. sync every batch).
    
    Testing plan pending
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). 
    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    
    ### For code changes:
    - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
    - [x] Have you included steps or a guide to how the change may be verified and tested manually?
    - [x] Have you ensured that the full suite of tests and checks have been executed in the root incubating-metron folder via:
      ```
      mvn -q clean integration-test install && build_utils/verify_licenses.sh 
      ```
    
    - [ ] Have you written or updated unit tests and or integration tests to verify your changes?
    - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`:
    
      ```
      cd site-book
      mvn site
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cestella/incubator-metron hdfs_index_sync

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/589.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #589
    
----
commit 3fcb332c50cac72b5322d8c006028311246a42b9
Author: cstella <ce...@gmail.com>
Date:   2017-05-15T18:29:17Z

    METRON-955: Make the default sync policy for HDFS Writer be based on the batch size

----


> Make the default sync policy for HDFS Writer be based on the batch size
> -----------------------------------------------------------------------
>
>                 Key: METRON-955
>                 URL: https://issues.apache.org/jira/browse/METRON-955
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Casey Stella
>
> Right now, we do a sync per record written in HDFS.  This has performance penalties as it requires a Namenode contact.  We get around this by letting the user define the sync policy in Flux, but that's less convenient and more sensible defaults could be created.  We should use the batch size as a sensible default for the sync policy (i.e. sync every batch).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)