You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:32 UTC

[jira] [Commented] (BEAM-4460) Investigate other encoding mechanism for SchemaCoder

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

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

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.


> Investigate other encoding mechanism for SchemaCoder
> ----------------------------------------------------
>
>                 Key: BEAM-4460
>                 URL: https://issues.apache.org/jira/browse/BEAM-4460
>             Project: Beam
>          Issue Type: Sub-task
>          Components: io-java-gcp
>            Reporter: Reuven Lax
>            Priority: P2
>              Labels: stale-P2
>
> Some possibilities: FlatBuffer or Arrow. If we made the FnApi aware of schemas, the FnApi might be able to use Arrow to encode bundles sent over the wire, and we could dispense with having a "tradtional" coder.



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