[
https://issues.apache.org/jira/browse/KUDU-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677887#comment-17677887
]
ASF subversion and git services commented on KUDU-1945:
-------------------------------------------------------
Commit fa74ae75244ad18060ebb07be97bd63c0f24c1e1 in kudu's branch
refs/heads/master from Abhishek Chennaka
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=fa74ae752 ]
KUDU-1945 Fix TSAN warnings in client-test.cc
This patch addresses the TSAN warnings seen due to race conditions
in the test ClientTestAutoIncrementingColumn.ConcurrentWrites in
client-test.cc.
Without any modification 5/1024 failed:
http://dist-test.cloudera.org/job?job_id=root.1673953260.499709
With the proposed changes: 0/1024 failed:
http://dist-test.cloudera.org/job?job_id=root.1673952868.476619
Thanks to Marton for helping out with the dist-test.
Change-Id: I24315c24ed7424e641837cf2d681262584f3e4d5
Reviewed-on: http://gerrit.cloudera.org:8080/19427
Reviewed-by: Marton Greber <[email protected]>
Reviewed-by: Attila Bukor <[email protected]>
Tested-by: Attila Bukor <[email protected]>
> Support generation of surrogate primary keys (or tables with no PK)
> -------------------------------------------------------------------
>
> Key: KUDU-1945
> URL: https://issues.apache.org/jira/browse/KUDU-1945
> Project: Kudu
> Issue Type: New Feature
> Components: client, master, tablet
> Reporter: Todd Lipcon
> Priority: Major
> Labels: roadmap-candidate
>
> Many use cases have data where there is no "natural" primary key. For
> example, a web log use case mostly cares about partitioning and not about
> precise sorting by timestamp, and timestamps themselves are not necessarily
> unique. Rather than forcing users to come up with their own surrogate primary
> keys, Kudu should support some kind of "auto_increment" equivalent which
> generates primary keys on insertion. Alternatively, Kudu could support tables
> which are partitioned but not internally sorted.
> The advantages would be:
> - Kudu can pick primary keys on insertion to guarantee that there is no
> compaction required on the table (eg always assign a new key higher than any
> existing key in the local tablet). This can improve write throughput
> substantially, especially compared to naive PK generation schemes that a user
> might pick such as UUID, which would generate a uniform random-insert
> workload (worst case for performance)
> - Make Kudu easier to use for such use cases (no extra client code necessary)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
