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
Describe the bug
Every join to sem_join_cascade creates the index for second series (l2) from scratch since it call sem_index on it. Also, it can potentially override an existing index.
Expected behavior
The index should be recreated only if the data has changed. Using time to differentiate the versions or creating it in ~/.cache might be better so that we don't override the user's existing indices.
The text was updated successfully, but these errors were encountered:
Describe the bug
Every join to sem_join_cascade creates the index for second series (l2) from scratch since it call
sem_index
on it. Also, it can potentially override an existing index.See:
lotus/lotus/sem_ops/sem_join.py
Line 287 in 9761855
Expected behavior
The index should be recreated only if the data has changed. Using time to differentiate the versions or creating it in ~/.cache might be better so that we don't override the user's existing indices.
The text was updated successfully, but these errors were encountered: