[
https://issues.apache.org/jira/browse/KUDU-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113647#comment-17113647
]
ASF subversion and git services commented on KUDU-2817:
-------------------------------------------------------
Commit 6ffac57ee0552880a4248329fc299dbfc61f844b in kudu's branch
refs/heads/master from Andrew Wong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=6ffac57 ]
Revert "KUDU-2817: Upgrade glog to 0.4.0"
This reverts commit 940f6d136286feef1e101e47f1d14e6ce5f95d61.
Reason for revert: it seems like some OSes aren't able to build with
this patch, e.g. CentOS 7.3 and Ubuntu 14.04.
I've seen build errors with errors like the following:
--insertions_out: protoc-gen-insertions: Plugin killed by signal 11.
Change-Id: Id5ecd66eaeae0db086986ce09612d0566052b3c6
Reviewed-on: http://gerrit.cloudera.org:8080/15975
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Tested-by: Andrew Wong <aw...@cloudera.com>
> C++ Upgrades for before Kudu 1.13 release
> -----------------------------------------
>
> Key: KUDU-2817
> URL: https://issues.apache.org/jira/browse/KUDU-2817
> Project: Kudu
> Issue Type: Improvement
> Affects Versions: 1.10.0
> Reporter: Grant Henke
> Priority: Major
>
> We should consider reviewing and upgrading our dependencies before the next
> release. Below is a list of current dependencies and their latest release.
> * gflags: 2.2.0 (Nov 2016) -> 2.2.2 (Nov 2018)
> * glog: 0.3.5 (May 2017) -> 0.4.0 (Mar 2019)
> * gmock: 1.8.0 -> 1.8.1
> * gperftools: 2.6.90 -> 2.7
> * protobuf: 3.4.1 -> 3.7.1 (3.8.0 soon)
> * cmake: 3.9.0 (Nov 2018) -> 3.14.3 (May 2019)
> * snappy: 1.1.4 (Jan 2017) -> 1.1.7 (Aug 2017)
> * lz4: r130 (patched, 2015) -> 1.9.1 (May 2019, expected perf gains)
> * bitshuffle: 55f9b4c (patched, 2016) -> 0.3.5 (Nov 2018)
> * zlib: 1.2.8 (Apr 2013) -> 1.2.11 (Jan 2017)
> * libev: 4.20 -> 4.22
> * rapidjson: 1.1.0 (current)
> * squeasel: current
> * mustache: 87a592e8aa04497764c533acd6e887618ca7b8a8 (Feb 2017) ->
> cf5c3dd499ea2bc9eb5c2072fb551dc7af75aa57 (Jun 2017)
> ** Consider using official mustach c++ support?
> * curl: 7.59.0 (Mar 2018) -> 7.64.1 (Mar 2019)
> * crcutil: current
> * libunwind: 1.3-rc1 (patched, Nov 2017) -> 1.3.1 (Jan 2019)
> * llvm: 6.0.0 (Mar 2018) -> 8.0.0 (Mar 2019)
> * iwyu: 0.9 -> 0.12 (May 2019)
> * nvml: 1.1 (2016) -> 1.6 (now called pmdk, Mar 2019)
> ** Patch to replace with memkind is posted
> * boost: 1.61.0 (patched, 2016) -> 1.70.0 (Apr 2019)
> * breakpad: 9eac2058b70615519b2c4d8c6bdbfca1bd079e39 (Apr 2013) ->
> 21b48a72aa50dde84149267f6b7402522b846b24 (Apr 2019)
> * sparsepp: 47a55825ca3b35eab1ca22b7ab82b9544e32a9af (Nov 2016) ->
> 5ca6de766db32b3fb08a040636423cd3988d2d4f (Jun 2018)
> * thrift: 0.11 (Dec 2017) -> 0.12 (Dec 2018)
> * bison: 3.0.4 (patched, 2015) -> 3.3 (Jan 2019)
> * hive: 498021fa15186aee8b282d3c032fbd2cede6bec4 (commit in Hive 2) -> 3.1.1
> (Oct 2018)
> * hadoop: 2.8.5 (Sept 2018) -> 3.1.2 (Feb 2019)
> * sentry: 505b42e81a9d85c4ebe8db3f48ad7a6e824a5db5 (commit in Master)
> * python: 2.7.13 -> (a lot of choices here)
> A quick risk/reward review should be done and we should upgrade the
> dependencies that are expected to be beneficial.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
