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

Beam JIRA Bot commented on BEAM-8423:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it 
has been labeled "stale-P2". If this issue is still affecting you, we care! 
Please comment and remove the label. Otherwise, in 14 days the issue will be 
moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed 
explanation of what these priorities mean.


> Japanese characters encoding issue 
> -----------------------------------
>
>                 Key: BEAM-8423
>                 URL: https://issues.apache.org/jira/browse/BEAM-8423
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>    Affects Versions: 2.15.0
>         Environment: dataflow
>            Reporter: Jyoti Aditya
>            Priority: P2
>              Labels: stale-P2
>
> I am running apache beam job to parse japanese html pages. While running the 
> job, I see in stackdriver log it is showing japanese character properly. But 
> same data written to GCS bucket has encoding issue and it is getting 
> corrupted.
>  
> {noformat}
> //code
> Pipeline pipeline = Pipeline.create(options);
> CoderRegistry cr = pipeline.getCoderRegistry();
> cr.registerCoderForClass(String.class, StringUtf8Coder.of());
> cr.registerCoderForClass(Integer.class, BigEndianIntegerCoder.of());
> batchTuple = pipeline
>               .apply("Read from input files", 
> TextIO.read().from(options.getloadingBucketURL()).withCompression(Compression.GZIP)).setCoder(StringUtf8Coder.of())
>               .apply("Process input files",ParDo.of(new 
> ExtractDataFromHtmlPage(extractionConfig,beamConfig.getLoadingBucketURL())).withOutputTags(successRecord,
>  TupleTagList.of(errorRecord).and(deadLetterRecords)));{noformat}
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to