kudu git commit: [logging] fix logging init if linking kudu client library

Repository: kudu Updated Branches: refs/heads/master 825b964fa -> 2ff946030 [logging] fix logging init if linking kudu client library Don't call constructor-like InitializeBasicLogging() function in non-exported builds of the kudu_client library. The rationale is simple: the non-exported

kudu git commit: KUDU-2312: Scan predicate application ordering is non-deterministic

Repository: kudu Updated Branches: refs/heads/branch-1.6.x f0d95c27e -> f43c77bed KUDU-2312: Scan predicate application ordering is non-deterministic This changes the scan predicate evaluation ordering so that it primarily orders by selectivity (as before), but breaks ties by column index.

kudu git commit: KUDU-2447 Fix TS crashed with "NONE predicate can not be pushed into key"

Repository: kudu Updated Branches: refs/heads/branch-1.7.x a307f2a31 -> 2a8893e3e KUDU-2447 Fix TS crashed with "NONE predicate can not be pushed into key" tserver crashes on Scan when [lowerPrimaryKey, upperPrimary) and predicates of primary column do not overlap Change-Id: