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
I'm in the same boat. I think we/you could just create a new table with the other distance metric, do a insert into new_table select * from old_table, and it's good? I'm going to try this.
I think that may work, as long as the old table isn't dropped and the new one renamed. I'm getting an SQL logic error in that case. Maybe renaming on virtual tables isn't supported?
The default
distance_metric
isl2_distance
which is not the one using for embedding. I need to change it todistance_metric=cosine
.How to migrate this change and minimize the impact? Can I save the existing vector data?
The text was updated successfully, but these errors were encountered: