KeyAuth plugin on a Cassandra DB


#1

I am curious about how the key-auth plugin works, specifically when used with a cassandra backing db.

it appears that the keys is set to unique but how is the uniqueness enforced?
I am asking because it seems that this uniqueness would force a full table scan in cassandra, how else would kong know if the key is unique or not.

If the contraint is forcing full table scans should the key field not be an index?


#2

The key field is indexed if that’s what you mean.


#3

I see that you pointed out that there is an index, but even with the index you cannot search (WHERE clause) based on the field. So how is the uniqueness enforced? could cassandra no need to run a search on the table to see if that key has been previously used?