beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BEAM-1870) ByteKey / ByteKeyRangeTracker should not use ByteString on public API surface
Date Tue, 25 Apr 2017 15:53:04 GMT

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

Daniel Halperin resolved BEAM-1870.
-----------------------------------
    Resolution: Fixed

> ByteKey / ByteKeyRangeTracker should not use ByteString on public API surface
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-1870
>                 URL: https://issues.apache.org/jira/browse/BEAM-1870
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Daniel Halperin
>            Assignee: Daniel Halperin
>             Fix For: First stable release
>
>
> We don't want these Google Protocol Buffer dependencies on the public API. We should
replace the use of {{ByteString}} with something in the core Java libraries.
> What's the open source standard here? I guess Avro uses {{ByteBuffer}} for wrapping {{byte[]}}
?
> [~iemejia] -- tentatively assigned to you as you brought this up.



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

Mime
View raw message