You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Alexey Romanenko (Jira)" <ji...@apache.org> on 2020/11/04 12:13:00 UTC

[jira] [Updated] (BEAM-11091) HadoopFormatIO should allow to specify coders

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

Alexey Romanenko updated BEAM-11091:
------------------------------------
    Status: Resolved  (was: Open)

> HadoopFormatIO should allow to specify coders
> ---------------------------------------------
>
>                 Key: BEAM-11091
>                 URL: https://issues.apache.org/jira/browse/BEAM-11091
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-hadoop-format
>    Affects Versions: 2.24.0
>            Reporter: Jozef Vilcek
>            Assignee: Jozef Vilcek
>            Priority: P3
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> HadoopFormatIO does allow only to pass in type descriptors for key and value and those are then resolved to Coder via CoderRegistry.
> We did find this restrictive after https://issues.apache.org/jira/browse/BEAM-9569
> which makes it impossible to emit Row out of the source.
> Easy solution I see can be to allow set Coder directly and bypass the resolution against registry in that case.



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