kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jdcry...@apache.org
Subject [4/5] kudu git commit: [doc] updated release notes for Kudu C++ client
Date Wed, 09 Nov 2016 14:09:45 GMT
[doc] updated release notes for Kudu C++ client

Change-Id: If4667dc7bb90fdf910c06a9107ce41f1ac3d7037
Reviewed-on: http://gerrit.cloudera.org:8080/5006
Reviewed-by: Adar Dembo <adar@cloudera.com>
Tested-by: Kudu Jenkins

Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/1b30c601
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/1b30c601
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/1b30c601

Branch: refs/heads/master
Commit: 1b30c601aaac56f0393178a9799bd377fc8e33bc
Parents: ef30f1d
Author: Alexey Serbin <aserbin@cloudera.com>
Authored: Tue Nov 8 12:22:07 2016 -0800
Committer: Alexey Serbin <aserbin@cloudera.com>
Committed: Wed Nov 9 01:27:11 2016 +0000

 docs/release_notes.adoc | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/docs/release_notes.adoc b/docs/release_notes.adoc
index 37c5dc9..81bd64c 100644
--- a/docs/release_notes.adoc
+++ b/docs/release_notes.adoc
@@ -64,14 +64,21 @@ XXX
 === Client APIs ({cpp}/Java/Python)
-- The {cpp} client library no longer requires the
+* The {cpp} client no longer requires the
   link:https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html[old gcc5 ABI].
   Which ABI is actually used depends on the compiler configuration. Some new distros
   (e.g. Ubuntu 16.04) will use the new ABI. Your application must use the same ABI as is
   used by the client library; an easy way to guarantee this is to use the same compiler
   to build both.
-- The Java client's `OperationResponse.getWriteTimestamp` method was renamed to `getWriteTimestampRaw`
+* The {cpp} client's `KuduSession::CountBufferedOperations()` method is
+  deprecated. Its behavior is inconsistent unless the session runs in the
+  `MANUAL_FLUSH` mode. Instead, to get number of buffered operations, count
+  invocations of the `KuduSession::Apply()` method since last
+  `KuduSession::Flush()` call or, if using asynchronous flushing, since last
+  invocation of the callback passed into `KuduSession::FlushAsync()`.
+* The Java client's `OperationResponse.getWriteTimestamp` method was renamed to `getWriteTimestampRaw`
   to emphasize that it doesn't return milliseconds, unlike what its Javadoc indicated. The
   method was also hidden from the public APIs and should not be used.

View raw message