Context

Haystack is a developer library for building AI applications, with support for various databases. Since it didn't have MongoDB support we wrote a Product Description (https://docs.google.com/document/d/1qivDdlmViCecQ-A1vtfKEeazpOC-yn5sSMCQeoSV4s8/edit) for a 3rd party contractor to build out the integration. The contractor working on it has completed their work (https://github.com/mtwomey/hm-01/tree/master). The next step is for our engineer to review and commit this code to the Haystack repo. We want our team to make the commit to the open-source project to ensure the confidence in the community that the plugin is high quality and is endorsed by MongoDB. We have been talking to the Haystack team and they have agreed to support this code moving ahead.

Definition of done

What must be done to consider the task complete?

* Take the code from https://github.com/mtwomey/hm-01/tree/master and open a PR to the main haystack repo in the format required by "Haystack-contributed integrations".

• Haystack-contributed: For those maintained by Haystack, there .md file in the haystack-integrations/integrations, a core code file in the haystack/haystack/document_stores, and a pip distribution
  • ex Pinecone - pinecone.py in haystack repo, Github documentation, pypi

* Work with the feedback provided by the haystack team on the PR and ensure the PR is merged.

Pitfalls

What should the implementer watch out for? What are the risks?

APPENDIX

Note from Haystack team:
"If your engineers need any support you can either reach us via our community discord, or I can schedule dedicated calls with our engineers directly."
 

Note from the contractor:

You'll find everything in the https://github.com/mtwomey/hm-01/tree/master repository.
I have a longer video which walks through everything: https://youtu.be/5F388wqPZ1k
In general all was successful.
- All features implemented
- 49 tests between unit and integration exercising all major functionality as well as Atlas vector search
- Demo app ("80 Days") complete and documented
- General documentation on the driver, local development, and testing in the main README.md
- DocumentStore "card" completed (this is the document Haystack uses to overview their document stores and it's in the docs folder)
- Document / Notes on contributing t

he driver to Haystack (detailing exactly what's needed)