Size Limits for `accessible_to_user_ids` in Scoped API Keys
TLDR Navjot asked about the size limit of the accessible_to_user_ids field for scoped API keys. Jason said it can store 1000s of values without any issues.
1Apr 19, 2023 (5 months ago)
Navjot
06:51 PMI have a question about
Scoped API KeysIn the documentation example of Scoped API Keys
it mentions using a field like
accessible_to_user_ids to every document in the collectionand then creating a key with an embedded filter like:
filter_by: accessible_to_user_ids:=1my question is: How large can this
accessible_to_user_ids field be before impacting performance?As in how many users ids can you fit into that list before it’s a problem that impacts performance?
Doesn’t have to be an exact number but rough order of magnitude. 1000s, 10,000s, 100,000s, 1,000,000s?
Thanks!
1Apr 20, 2023 (5 months ago)
Jason
02:41 AM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Scoped Keys and Accessible_UserIds Performance
Tomas inquired about performance limitations for scoped keys with a large userbase. Jason directed to a similar question response and mentioned a JOIN feature in development.
Comparing Performance and Security of Different Data Collection Methods
bnfd asked about differences in performance and memory usage between a single, large data collection and multiple smaller collections. Kishore Nallan explained that the latter is faster, suggested 100 collections sharded by user_id, and informed about the use and security of scoped API keys.
1Limit on API Keys and User Scope
Peter asked if there is a limit on API keys. Kishore Nallan clarified that one parent key per user is enough because filters can be embedded into scoped keys.
1