Create a new repository for experimental Go Driver code

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 🔵 Done
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      We've had a number of APIs that we want to add to the Go Driver, but they need time for refinement before we're ready to commit to making them part of the stable API. For example:

      • The aggregation pipeline builder.
      • The module that allows using the official AWS SDK instead of the built-in AWS auth.

      We should create a repo for extensions like that, but without the guarantee of backward compatibility.

      The Go project uses a similar concept for the golang.org/x/exp project, which does not offer backward compatibility.

      Definition of done

      What must be done to consider the task complete?

      Pitfalls

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

            Assignee:
            Andreas Braun
            Reporter:
            Matt Dale
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: