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
Even though Haystack supports Milvus2, right now all tutorials and utilities are somehow hardcoded to use Milvus1. Given the recent release of Milvus2, we should make sure they work properly with it, ensure the correct tests are run in the CI and default users on Milvus2.
The text was updated successfully, but these errors were encountered:
* Fist attempt at using setup.cfg for dependency management
* Trying the new package on the CI and in Docker too
* Add composite extras_require
* Add the safe_import function for document store imports and add some try-catch statements on rest_api and ui imports
* Fix bug on class import and rephrase error message
* Introduce typing for optional modules and add type: ignore in sparse.py
* Include importlib_metadata backport for py3.7
* Add colab group to extra_requires
* Fix pillow version
* Fix grpcio
* Separate out the crawler as another extra
* Make paths relative in rest_api and ui
* Update the test matrix in the CI
* Add try catch statements around the optional imports too to account for direct imports
* Never mix direct deps with self-references and add ES deps to the base install
* Refactor several paths in tests to make them insensitive to the execution path
* Include tstadel review and re-introduce Milvus1 in the tests suite, to fix
* Wrap pdf conversion utils into safe_import
* Update some tutorials and rever Milvus1 as default for now, see #2067
* Fix mypy config
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Even though Haystack supports Milvus2, right now all tutorials and utilities are somehow hardcoded to use Milvus1. Given the recent release of Milvus2, we should make sure they work properly with it, ensure the correct tests are run in the CI and default users on Milvus2.
The text was updated successfully, but these errors were encountered: