Issue: <https://github.com/typesense/typesense/is...
# community-help
t
Issue: https://github.com/typesense/typesense/issues/2680 Fix: https://github.com/typesense/typesense/pull/2682 Revert/fix performance regression: https://github.com/typesense/typesense/pull/2718 Where the revert/fix seems to cause original issue to return. Have at least experienced it and started to drop all collections on any change since. But would be nice it it would be improved to be reliable in future. As i imagine alias also will suffer?
h
Hey @Thomas Andersson is the issue still reproducible with the steps mentioned in your issue?
t
Honestly it wasnt, I think the scenario I have experienced after the regression fix, might be some kind of timing issue that it takes some time after dropping a referenced collection and re-creating it until all internal references is updated, as maybe the regression fix for performance was to do it async? But - the issue from @Grigoris Balaskas reproduces so aliases is a issue it seems. Added new issue for it: https://github.com/typesense/typesense/issues/2827 All non-alias drop/recreate scenarios work perfectly on 30.1, including: - Large datasets (500+ docs) - Dropping referenced (right side) collection - Dropping referencing (left side) collection - Seq_id space shrinking (100 → 3 docs) - Multiple async references (drop one, keep other) - String id references - Rapid drop+recreate with no sleep - Querying mid-import (partial resolution)