You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2017/03/30 21:07:41 UTC
[jira] [Updated] (RATIS-60) Allow direct PB support for Message and
SMLogEntry
[ https://issues.apache.org/jira/browse/RATIS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated RATIS-60:
-------------------------------
Attachment: ratis-60-v0.patch
This v0 patch is what I have in the patch from the parent RATIS-40. However, it does not fix the problem, just allows us to have PB-based Message objects. Just attaching for illustrating the problem.
> Allow direct PB support for Message and SMLogEntry
> --------------------------------------------------
>
> Key: RATIS-60
> URL: https://issues.apache.org/jira/browse/RATIS-60
> Project: Ratis
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.1.0-alpha
>
> Attachments: ratis-60-v0.patch
>
>
> Right now, for flexibility, both Message and SMLogEntry are ByteStrings. This allows using custom serialization formats other than PB (or maybe use a different version of PB).
> However, this is very inefficient for the common case where both the messages and SM Log Entries are themselves PB objects. We unnecessarily serialize twice.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)