beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1856) HDFSFileSink class do not use the same configuration in master and slave
Date Thu, 06 Apr 2017 17:22:41 GMT

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

ASF GitHub Bot commented on BEAM-1856:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/beam/pull/2399


> HDFSFileSink class do not use the same configuration in master and slave
> ------------------------------------------------------------------------
>
>                 Key: BEAM-1856
>                 URL: https://issues.apache.org/jira/browse/BEAM-1856
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-extensions
>    Affects Versions: 0.6.0
>            Reporter: yangping wu
>            Assignee: yangping wu
>             Fix For: First stable release
>
>
> I have a code snippet as follow:
> {code}
> Read.Bounded<KV<LongWritable, Text>> from = Read.from(HDFSFileSource.from(options.getInputFile(),
TextInputFormat.class, LongWritable.class, Text.class));
> PCollection<KV<LongWritable, Text>> data = p.apply(from);
> data.apply(MapElements.via(new SimpleFunction<KV<LongWritable, Text>, String>()
{
>     @Override
>     public String apply(KV<LongWritable, Text> input) {
>         return input.getValue() + "\t" + input.getValue();
>     }
> })).apply(Write.to(HDFSFileSink.<String>toText(options.getOutputFile())));
> {code}
> and submit job like this:
> {code}
> spark-submit --class org.apache.beam.examples.WordCountHDFS --master yarn-client   \
>              ./target/word-count-beam-bundled-0.1.jar                              \
>              --runner=SparkRunner                                                  \
>              --inputFile=hdfs://master/tmp/input/                                  \
>              --outputFile=/tmp/output/
> {code}
> Then {{HDFSFileSink.validate}} function will check whether the local filesystem (not
HDFS) exists {{/tmp/output/}} directory.
> But the final result will store in {{hdfs://master/tmp/output/}} directory in HDFS filesystem.
> The reason is {{HDFSFileSink}} class do not use the same configuration in master thread
and slave thread.



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

Mime
View raw message