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
Why do you want to initialize with an empty corpus? An error seems like a good thing to do here in my opinion, but I'm curious to hear about your use case.
iirc, developing a RAG pipeline that used hybrid search. rank-bm25 was buried under a few frameworks, app -> framework+ -> rank-bm25, making the error difficult to interpret and patch.
In this case I think it might be best for me to implement a custom exception (ie EmptyCorpusError), and then it would be easier to catch with a try/except. Then your stack can address what to do with that exception. Does that sound useful?
Within the scope of this project I don't see any functional use cases for empty corpuses currently.
rank-bm25==0.2.2
The text was updated successfully, but these errors were encountered: