[
https://issues.apache.org/jira/browse/PHOENIX-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002742#comment-15002742
]
Josh Elser commented on PHOENIX-2359:
-------------------------------------
bq. I'd be +1 on changing to your new protobuf serialization if you think it
has feature parity and unit tests.
It's definitely full-featured+tested at the Avatica level, but probably doesn't
have as much testing as JSON (although that might be from use than automated
testing).
Reminding myself why we wanted to do this in the first place (stability and
backwards-compatibility), I think you're right that it would be better to just
switch to protobuf now. Let me flip it over.
> Configuration for PQS to use Protobuf serialization instead of JSON
> -------------------------------------------------------------------
>
> Key: PHOENIX-2359
> URL: https://issues.apache.org/jira/browse/PHOENIX-2359
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Trivial
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2359.001.patch, PHOENIX-2359.002.patch,
> PHOENIX-2359.003.patch
>
>
> Calcite-1.5.0 is soon to drop. Included in that release is some work to use
> protocol buffers for the data transported over HTTP between client and server
> instead of JSON.
> I made some changes in Avatica which hopefully make Phoenix's use of the
> Avatica server easier, in addition to choosing the serialization.
> Let me stage the patch I've been using to test this. We can't apply it until
> we're confident that moving to the newer version of Calcite is safe to do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
