Closed ruoqianfengshao closed 3 months ago
This could happen if the alias in Typesense was somehow pointing to the new collection, before the scraper was done.
Because the scraper at the end will look up what the old collection name was using the alias, then point the alias to the new collection and delete the collection
@jasonbosco Thanks for explaining. I delete all aliases and run scraper again, then it looks fine.
Description
The newest collection was deleted after scraper completed, the scraper log show![image](https://github.com/typesense/typesense-docsearch-scraper/assets/2928664/b6eb162c-c231-4b18-9562-710a8b5fa529)
Nb hits: 172054
when the scraper running, I can find collection with![image](https://github.com/typesense/typesense-docsearch-scraper/assets/2928664/9aabe9b3-3f9a-4624-a5f5-4efc38100381)
nb documents
increasingbut after scraper completed, the collection was disappeared.
Steps to reproduce
my config as below:
Expected Behavior
The correct collection work.
Actual Behavior
The correct collection was deleted.
Metadata
Typesense Version: 0.25.2 Typesense scraper Version: 0.9.1