You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by "Durity, Sean R" <SE...@homedepot.com> on 2020/03/06 14:47:23 UTC

RE: [EXTERNAL] Re: Performance of Data Types used for Primary keys

I agree. Cassandra already hashes the partition key to a numeric token.

Sean Durity

From: Jon Haddad <jo...@jonhaddad.com>
Sent: Friday, March 6, 2020 9:29 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Performance of Data Types used for Primary keys

It's not going to matter at all.

On Fri, Mar 6, 2020, 2:15 AM Hanauer, Arnulf, Vodacom South Africa (External) <Ar...@vcontractor.co.za>> wrote:
Hi Cassandra folks,

Is there any difference in performance of general operations if using a TEXT based Primary key versus a BIGINT Primary key.

Our use-case requires low latency reads but currently the Primary key is TEXT based but the data could work on BIGINT. We are trying to optimise where possible.
Any experiences that could point to a winner?


Kind regards
Arnulf Hanauer









"This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link https://webmail.vodacom.co.za/tc/default.html [vodacom.co.za]<https://urldefense.com/v3/__https:/www.vodacom.co.za/vodacom/terms/email-acceptable-user-policy__;!!M-nmYVHPHQ!cQ0VYz-L_NF7utZ99Mz-BJGPsQOCWOykrGzBAiIo_lxJVyJVs-FnQN4b-lvC7Hxg4J_qi6M$> "

________________________________

The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.