Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-3251

LangChainGo MongoDB Integration

XMLWordPrintableJSON

    • Type: Icon: Epic Epic
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Go Drivers
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • To Do
    • LangChainGo MongoDB Integration
    • 6
    • 3
    • 6
    • 100
    • Hide

      Engineer(s): Preston Vasquez

      2024-11-08

      • What's the focus over the next two weeks?
        • Nothing scheduled in Q4 for the next two weeks. The final part of Q4 will close out the epic with GODRIVER-3334 to Include LangChainGo in AI/ML integration pipeline.
      • Impediments encountered over the last two weeks?
        • None

      2024-10-25

      • What was completed over the last two weeks?
        • No progress, bandwidth focused on QP CSOT work to prevent connection churn, DRIVERS-2884
      • What's the focus over the next two weeks?
        • Create an example and README.md for LangChainGo's mongovector
      • Impediments encountered over the last two weeks?
        • None

      2024-10-10

      • What was completed over the last two weeks?
        • All Q3 work is in review with the LangChainGo team.
        • Remaining work is scheduled to complete in Q4
      • What's the focus over the next two weeks?
        • NA
      • Impediments encountered over the last two weeks?
        • None
      Show
      Engineer(s): Preston Vasquez 2024-11-08 What was completed over the last two weeks? PR for README.md and example ( GODRIVER-3336 ) is in review: https://github.com/tmc/langchaingo/pull/1063 What's the focus over the next two weeks? Nothing scheduled in Q4 for the next two weeks. The final part of Q4 will close out the epic with GODRIVER-3334 to Include LangChainGo in AI/ML integration pipeline. Impediments encountered over the last two weeks? None 2024-10-25 What was completed over the last two weeks? No progress, bandwidth focused on QP CSOT work to prevent connection churn, DRIVERS-2884 What's the focus over the next two weeks? Create an example and README.md for LangChainGo's mongovector Impediments encountered over the last two weeks? None 2024-10-10 What was completed over the last two weeks? All Q3 work is in review with the LangChainGo team. Remaining work is scheduled to complete in Q4 What's the focus over the next two weeks? NA Impediments encountered over the last two weeks? None

      Summary

      We'd like to provide a MongoDB integration for LangChainGo for users wanting to use Go to write LLM apps.

      Motivation

      Who is the affected end user?

      Any developers wanting to write LLM apps in Go. This includes both established MongoDB customers that have used MongoDB in the past, but also, more importantly, developers wanting to use Go for their LLM apps but struggling with the lack of Go options and support in the ML/AI space.

      How does this affect the end user?

      Currently, MongoDB is not an available option for using LangChainGo, however, other competitor vector search databases are available.

      How likely is it that this problem or use case will occur?

      This is a main path scenario for LLM app Go developer wanting to use MongoDB. 

      If the problem does occur, what are the consequences and how severe are they?

      MongoDB is not an available option for LangChainGo.

      Is this issue urgent?

      There has been at least one large customer wanting to use LangChainGo with MongoDB.

      Is this ticket required by a downstream team?

      No.

      Is this ticket only for tests?

      No.

      Cast of Characters

      Engineering Lead:
      Document Author:
      POCers:
      Product Owner:
      Program Manager:
      Stakeholders:

      Channels & Docs

      Slack Channel

      [Scope Document|some.url]

      [Technical Design Document|some.url]

            Assignee:
            preston.vasquez@mongodb.com Preston Vasquez
            Reporter:
            julia.tazin@mongodb.com Julia Tazin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              13 weeks, 2 days