[
https://issues.apache.org/jira/browse/KUDU-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100184#comment-16100184
]
Acharki Mohammed commented on KUDU-2076:
----------------------------------------
Hi,
I'm the user who reported this problem, I confirm that the bug exist either
with a delete condition or no, and I face it in the both versions 1.3.0 and
1.4.0.
Here is more detail:
https://community.cloudera.com/t5/Interactive-Short-cycle-SQL/Error-in-delete-from-kudu-table-WARNINGS-Timed-out-Failed-to/m-p/57993
Hope we find a solution ASAP.
> Deleting/updating is slow on single numeric row key tables
> ----------------------------------------------------------
>
> Key: KUDU-2076
> URL: https://issues.apache.org/jira/browse/KUDU-2076
> Project: Kudu
> Issue Type: Bug
> Components: tablet
> Affects Versions: 1.4.0
> Reporter: Jean-Daniel Cryans
>
> A user reported that deleting 50M rows on the simplest of tables, (id INT,
> text STRING, PRIMARY KEY (id)), doesn't complete.
> It reproduces locally and I was able to see that we're deleting 1.4 rows / ms
> which is awful considering that everything is cached.
> Todd found that we're spending most of our time decoding big blocks of
> bit-shuffled keys. Intuitively he though that having a composite row key
> would perform better and indeed adding a column set to 0 in front makes it
> 10x faster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
