[
https://issues.apache.org/jira/browse/KUDU-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3238:
--------------------------------
Description:
There was a bug in Kudu C++ client which might manifest itself upon change in a
table partitioning, e.g. adding or removing a range partition and the
continuing working with the same instance of Kudu client object (the latter is
the recommended way of using the Kudu client in applications).
The issue might manifest itself in unexpected behavior in client applications
using the Kudu C++ client library. Examples of such behavior are deadlocks,
silent data corruption, and unexpected crashes with SIGBUS, SIGSEGV or even
SIGABRT at some unrelated consistency check (the latter is very unlikely,
though). By my knowledge, there have been no registered reports about
manifestations of this bug.
was:
There was a bug in Kudu C++ client which might manifest itself upon change in a
table partitioning, e.g. adding or removing a range partition and the
continuing working with the same instance of Kudu client object (the latter is
the recommended way of using the Kudu client in applications).
The issue might manifest itself in unexpected crashes or silent data
corruption. There were no registered reports about this by my knowledge.
> Use-after-free condition in Kudu C++ client upon modifying a table's
> partitioning
> ---------------------------------------------------------------------------------
>
> Key: KUDU-3238
> URL: https://issues.apache.org/jira/browse/KUDU-3238
> Project: Kudu
> Issue Type: Bug
> Components: client
> Affects Versions: 0.10.0, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0,
> 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.11.1,
> 1.13.0
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
> Fix For: 1.14.0
>
>
> There was a bug in Kudu C++ client which might manifest itself upon change in
> a table partitioning, e.g. adding or removing a range partition and the
> continuing working with the same instance of Kudu client object (the latter
> is the recommended way of using the Kudu client in applications).
> The issue might manifest itself in unexpected behavior in client applications
> using the Kudu C++ client library. Examples of such behavior are deadlocks,
> silent data corruption, and unexpected crashes with SIGBUS, SIGSEGV or even
> SIGABRT at some unrelated consistency check (the latter is very unlikely,
> though). By my knowledge, there have been no registered reports about
> manifestations of this bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
