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

Support rename collection for sharded collections

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: planned but not scheduled
    • Component/s: Sharding
    • Labels:
      None

      Issue Links

        Activity

        Hide
        itsmejainh Himanshu Jain added a comment -

        Hi,

        Any updates on this jira ?
        I am stuck because of this. I have to backup collection (shared) with '/' in name which has billion of documents.

        Just can't think of dropping and re-inserting documents.

        Pls suggest. Thank you.

        Show
        itsmejainh Himanshu Jain added a comment - Hi, Any updates on this jira ? I am stuck because of this. I have to backup collection (shared) with '/' in name which has billion of documents. Just can't think of dropping and re-inserting documents. Pls suggest. Thank you.
        Hide
        ryanovas Ryan Ovas added a comment -

        In the same boat as Himanshu Jain. Any progress on this?

        Show
        ryanovas Ryan Ovas added a comment - In the same boat as Himanshu Jain. Any progress on this?
        Hide
        AndrewDoumaux Andrew Doumaux added a comment -

        My use case for this feature:

        I'm using Mongo as an analytic cache. Every period of time I get a fresh copy of an analytic and load that analytic into a "staging" collection and when the load is completed I rename the collection to the "active" collection name. I was hoping to shard those collections so I could use the horizontal scaling of Mongo to cache larger analytic output.

        This pattern is very similar to how mongo's $out aggregation operation works if an existing collection exists.

        Thanks

        Show
        AndrewDoumaux Andrew Doumaux added a comment - My use case for this feature: I'm using Mongo as an analytic cache. Every period of time I get a fresh copy of an analytic and load that analytic into a "staging" collection and when the load is completed I rename the collection to the "active" collection name. I was hoping to shard those collections so I could use the horizontal scaling of Mongo to cache larger analytic output. This pattern is very similar to how mongo's $out aggregation operation works if an existing collection exists. Thanks

          People

          • Votes:
            13 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

            • Created:
              Updated:
              Days since reply:
              10 weeks ago
              Date of 1st Reply: