-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Python Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Context
Describe the background behind the problem.
alex.bevilacqua@mongodb.com writes "I just reached out to @Casey directly regarding https://github.com/feast-dev/feast/pull/6025, but at a high level do we have some sort of checklist we follow when adding MongoDB -backed capabilities to these frameworks (feature stores, memory stores, checkpointers, retrievers, etc). The reason I'm asking is we should always ensure we're adding metadata tracking, but I can see how it could be overlooked.
I'm working on a playbook with the Partners team that could include stuff like this so wanted to make sure I checked first with the team that's doing all this work if there are already best-practices or guidelines you're following, and if so where those might be."
This is somewhat of a placeholder for what our standard prompt for Auggie should be, assuming that it becomes our standard tool.
Definition of done
Pitfalls
What should the implementer watch out for? What are the risks?