Alexey Serbin has posted comments on this change. ( 
http://gerrit.cloudera.org:8080/16980 )

Change subject: Add release notes for 1.14.0
......................................................................


Patch Set 2:

(1 comment)

http://gerrit.cloudera.org:8080/#/c/16980/2/docs/release_notes.adoc
File docs/release_notes.adoc:

http://gerrit.cloudera.org:8080/#/c/16980/2/docs/release_notes.adoc@174
PS2, Line 174: * Fixed a heap-use-after-free bug in Kudu C++ client that might 
manifest itself when altering a
> is there a Jira for this or any information on how this bug might manifest
No, there isn't a JIRA for this, but I just filed this one a posteriori: 
KUDU-3238

The way how it would manifest itself varies, but bugs like this usually 
manifest themselves in silent data corruption and crashes with SIGSEGV, SIGBUS, 
or SIGABRT if hitting some sanity check down the road (the latter is reserved 
for lucky people with good karma :) ).

I didn't file the JIRA right away because I assumed the issue might surface in 
more or less the only user of the Kudu C++ client: impalad.  But the latter 
doesn't do any DDL: in Impala, DDLs are performed only by the impala-shell, and 
the latter uses Kudu Java client.



--
To view, visit http://gerrit.cloudera.org:8080/16980
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: kudu
Gerrit-Branch: branch-1.14.x
Gerrit-MessageType: comment
Gerrit-Change-Id: Ib8da030ce0f8797f8c366c56298fcda1020b00b6
Gerrit-Change-Number: 16980
Gerrit-PatchSet: 2
Gerrit-Owner: Grant Henke <[email protected]>
Gerrit-Reviewer: Alexey Serbin <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Attila Bukor <[email protected]>
Gerrit-Reviewer: Bankim Bhavsar <[email protected]>
Gerrit-Reviewer: Grant Henke <[email protected]>
Gerrit-Reviewer: Greg Solovyev <[email protected]>
Gerrit-Reviewer: Kudu Jenkins (120)
Gerrit-Reviewer: Mahesh Reddy <[email protected]>
Gerrit-Comment-Date: Tue, 26 Jan 2021 03:13:45 +0000
Gerrit-HasComments: Yes

Reply via email to