While large primary keys (within reason) should work, IMO anytime you're doing equality testing you are really better off minimizing the size of the key. Huge primary keys will also have very negative impacts on your key cache. I would err on the side of the digest, but I've never had a need for large keys so perhaps someone who has used them before would have a different perspective.
On Mon, Apr 11, 2016 at 2:43 PM, Robert Wille <rwi...@fold3.com> wrote: > I have a need to be able to use the text of a document as the primary key > in a table. These texts are usually less than 1K, but can sometimes be 10’s > of K’s in size. Would it be better to use a digest of the text as the key? > I have a background process that will occasionally need to do a full table > scan and retrieve all of the texts, so using the digest doesn’t eliminate > the need to store the text. Anyway, is it better to keep primary keys > small, or is C* okay with large primary keys? > > Robert > >
