On Aliasing Collections with Same Names
TLDR Aljosa suggested allowing an alias to have the same name as a collection. Jason explained the technical limitations for such a feature and future plans on alias functionality.
1
1Feb 04, 2022 (19 months ago)
Aljosa
06:55 PMI think the behavior of allowing an alias with the same name as the collection to be created would be more intuitive perhaps. It would automatically point to the collection of the same name and make it easier to transition from collections to aliases if you hadn't done so from the start.
Perhaps there is a technical reason why it's not possible though 🙂
Jason
07:37 PM/collections/xyz/documents/searchwe can't tell if the intent was to use the alias
xyz or collection xyz if we allowed the same name to be used for both entities.Jason
07:38 PM1Feb 06, 2022 (19 months ago)
Aljosa
07:09 AM1
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Duplicating a Collection and Creating an Alias
Gabe wanted to duplicate a collection and create an alias. Jason suggested exporting old documents and importing them into a new collection.
1Scoped API Keys with Collection Alias Names
Daniel asked if they could use an alias name for collection in scoped API keys. Kishore Nallan explained that it's not supported to avoid accidental security risks. Daniel agreed and opted for using a unique prefix with a wildcard for users' collections.
Understanding Alias Usage in API Collections and Environment Security
gab sought clarity on when collection aliases would be used, if they are public and how they handle different environments. Kishore Nallan explained their purpose and suggested using distinct API keys for each environment for privacy and customization. They also directed gab on how to generate these keys per collection.