-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recent breaking changes & Migration guidance #1590
Comments
Hey @tholor! Apologies for commenting on a pinned message. I have recently installed haystack on my local machine using the git+https method. Since I haven't used the repo too much yet, would it work to do a pip reinstall to get the newest version of Haystack working on my machine? I'm specifically using Haystack for building a retriever using DPR. Thanks a ton! |
Hey @pk1130, if you installed Haystack with:
then you should reinstall it with pip. Instead, if you installed it with:
then you should go in the root
There is no need to pip reinstall Haystack after that (given that you used the option Hope it helps! PS: next time please open a separate issue 😉 |
As we have now a migrating guide and this is becoming obsolete, I will close this issue. Please open a new one if you face migration issues 🙂 |
In preparation for Haystack 1.0, we conduct some major refactorings in the next weeks incl. several breaking changes.
We will keep a list of breaking changes here to help you migrate your own Haystack scripts and applications.
Refactoring of primitives (#1398)
We improved the basic datatypes. This might particularly break your code to
Documents
to the doc storeAnswers
from a pipeline / readerDocument
Document.text
->Document.content
Document.question
(was only used a while ago in FAQ search cases)text_field
->content_field
in ElasticsearchDocumentStore & Weaviate initfaq_question_field
in ElasticsearchDocumentStore & Weaviate initLabel
Label.question
->Label.query
Label.answer
anAnswer
obj rather than plain strLabel.document_id
(can now be accessed viaLabel.document.id
)Label.model_id
->Label.pipeline_id
Label.offset_start_in_doc
(can now be accessed via label.answer.offsets_in_document[0].start`Answer
The reader returns now an
Answer
object rather than a dict.It follows this new structure:
Particularly the handling of offsets has changed to be more explicit and allow for other multiple spans (e.g. TableQA):
The text was updated successfully, but these errors were encountered: