correctly set timestamp in config.collections

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.3
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Hide

      Create a new sharded collection.

      Show
      Create a new sharded collection.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a new collection is sharded, the config.collections.lastmod field (which here represents the sharding time of the collection) is not correctly being written - it's always something near zero.

            Assignee:
            Randolph Tan
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: