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
oftentimes we struggle to explain the results combine from the ANN index. To improve the developer experience, what if Lance's nearest neighbor API supported an option to return debug information about how the result was achieved?
e.g., if you call dataset.to_table(..., nearest={..., debug=True}), then you'll get additional columns back in the results like:
the ivf partition id this vector came from
the raw score (if refine_factor was not none)
the list of pq sub vector id's
With this information, combined with the index information itself from #617 we can make it very easy to understand and debug where results come from.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
oftentimes we struggle to explain the results combine from the ANN index. To improve the developer experience, what if Lance's nearest neighbor API supported an option to return debug information about how the result was achieved?
e.g., if you call
dataset.to_table(..., nearest={..., debug=True})
, then you'll get additional columns back in the results like:With this information, combined with the index information itself from #617 we can make it very easy to understand and debug where results come from.
Beta Was this translation helpful? Give feedback.
All reactions