)]}'
{"swift/container/sharder.py":[{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"d9079484c568a4dbf11d84e29ba9016a2eeb1285","unresolved":false,"context_lines":[{"line_number":1627,"context_line":""},{"line_number":1628,"context_line":"    def _push_pivot_ranges_to_container(self, pivot, root_account,"},{"line_number":1629,"context_line":"                                        root_container, pivot_point,"},{"line_number":1630,"context_line":"                                        storage_policy_index):"},{"line_number":1631,"context_line":"        # Push the new distributed node to the container."},{"line_number":1632,"context_line":"        part, root_broker, node_id \u003d \\"},{"line_number":1633,"context_line":"            self._get_shard_broker(root_account, root_container,"}],"source_content_type":"text/x-python","patch_set":1,"id":"dfeb2761_dd7051a8","line":1630,"updated":"2017-04-04 07:11:02.000000000","message":"Note this method isn\u0027t actually used anymore. But left it here for now, because it uses replication to update changes to the pivot ranges table in the root.. which _may_ be smarter as it could bypass the .pending on the root container. \n\nAlthough it may need to be updated to work correctly, as it didn\u0027t get love in the last POC.","commit_id":"e82336065992e00661897f9da592752fb1797f1a"}]}
