You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Eli Reisman (JIRA)" <ji...@apache.org> on 2016/07/15 23:43:20 UTC

[jira] [Commented] (SAMZA-320) Add hadoop-hdfs jar for Hello Samza

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

Eli Reisman commented on SAMZA-320:
-----------------------------------

Sorry have been heads down but am still watching for more `samza-hdfs` activity on JIRA, will try to help out more. Thanks again for doing this!

> Add hadoop-hdfs jar for Hello Samza
> -----------------------------------
>
>                 Key: SAMZA-320
>                 URL: https://issues.apache.org/jira/browse/SAMZA-320
>             Project: Samza
>          Issue Type: Improvement
>          Components: hello-samza
>            Reporter: Yan Fang
>            Assignee: Yan Fang
>              Labels: newbie
>             Fix For: 0.8.0
>
>         Attachments: SAMZA-320.1.patch, SAMZA-320.patch
>
>
> Currently, if a user wants to deploy the hello-samza project to the YARN, he has to change the pom file in samza-job-package by adding the HDFS dependency. [see tutorial|https://samza.incubator.apache.org/learn/tutorials/0.7.0/deploy-samza-job-from-hdfs.html]
> I think we should provide the hdfs jar by default. Because 
> 1. the user can use the same package compiled in [Hello Samza|https://samza.incubator.apache.org/startup/hello-samza/0.7.0/] page when he first time uses the Samza for the YARN deploy 
> 2. the user only needs to upload the package and change the factory and file path in the job properties file, which makes the whole process smoother.



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