Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-54044

Investigation on removing the usage of command aliases

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      Currently, the Command class supports having aliases for command-names. For eg, the FindAndModify command could be invoked by specifying either findAndModify or findandmodify. Here findAndModify is the latest name for this command and findandmodify is the older name.

      API versioning by design does not support having aliases, ie. each command in the API version should have only one command. But to support backward compatibility, a ticket to support command aliases has been created: SERVER-54028

      Although the IDL generated classes will now have support for aliases, we should still get rid of aliases, to have a tighter design around API versioning. Developers might be tempted to add aliases in the near future if we continue to support and it will become more difficult to get rid of aliases.

      We could do the followings:

      1. Find how many customers are using aliases. It might be comparatively easy to find in the Atlas then on onPrem. And try to get rid of those aliases subsequently.
      2.  Prevent developers from adding aliases in the future.

       

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            rishab.joshi@mongodb.com Rishab Joshi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: