You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Pritesh Maker (JIRA)" <ji...@apache.org> on 2018/10/15 17:23:00 UTC

[jira] [Commented] (DRILL-6642) Update protocol-buffers version

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

Pritesh Maker commented on DRILL-6642:
--------------------------------------

[~vitalii] are there any backward compatibility considerations with this upgrade? Anything specific from a testing/ QA perspective to watch out for?

> Update protocol-buffers version
> -------------------------------
>
>                 Key: DRILL-6642
>                 URL: https://issues.apache.org/jira/browse/DRILL-6642
>             Project: Apache Drill
>          Issue Type: Task
>          Components: Tools, Build &amp; Test
>    Affects Versions: 1.14.0
>            Reporter: Vitalii Diravka
>            Assignee: Vitalii Diravka
>            Priority: Major
>             Fix For: 1.15.0
>
>
> Currently Drill uses 2.5.0 {{protocol-buffers}} version.
>  The last version is 3.6.0 in maven repo: [https://mvnrepository.com/artifact/com.google.protobuf/protobuf-java]
> The new version has a lot of useful enhancements, which can be used in Drill.
>  One of them is using {{UNRECOGNIZED Enum NullValue}}, which can help to handle them in place of null values for {{ProtocolMessageEnum}} - DRILL-6639. 
>  Looks like the NullValue can be used instead of null returned from {{valueOf()}} (_or {{forNumber()}}, since {{valueOf()}} is deprecated in the newer protobuf version_):
>  [https://developers.google.com/protocol-buffers/docs/reference/java/com/google/protobuf/NullValue]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)