You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using go-redis with KVRocks.
Not sure if this is default behavior with the client or with KVRocks, but it always saves indexes alongside the regular keys. For example, whenever I save something like foo:bar it gets saved in the DB twice:
foo:bar
IDX_foo:bar
I'm wondering what's the best practice dealing with those IDX_ entries in the DB after deleting the original key (foo:bar) ?
Normally I'd only delete keys via SCAN and a pattern like foo:* so the IDX_foo:bar key/index is still saved forever.
Would be nice to be able to delete both in one go rather than sending multiple commands.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi there,
I'm using
go-redis
with KVRocks.Not sure if this is default behavior with the client or with KVRocks, but it always saves indexes alongside the regular keys. For example, whenever I save something like
foo:bar
it gets saved in the DB twice:foo:bar
IDX_foo:bar
I'm wondering what's the best practice dealing with those
IDX_
entries in the DB after deleting the original key (foo:bar
) ?Normally I'd only delete keys via SCAN and a pattern like
foo:*
so theIDX_foo:bar
key/index is still saved forever.Would be nice to be able to delete both in one go rather than sending multiple commands.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions