Ticket #1757 (closed enhancement: fixed)

Opened 5 years ago

Last modified 4 years ago

Allow full history changesets to be combined

Reported by: brett@… Owned by: brett@…
Priority: major Milestone: OSM 0.6
Component: osmosis Version:
Keywords: Cc:

Description

Osmosis has recently added the ability to generate full history changeset files. These files cannot be combined into larger files because the existing --merge-change task only allows a single change per entity and collapses multiple changes into a single change. A new task(s) needs to be created for merging full history changeset files. This may require enhancements to the existing --sort-change task.

Change History

comment:1 Changed 5 years ago by brett@…

Part 1

The new append task would be something along the lines of: --append-change - Would accept any number of input pipe change streams (default=2) and combine send them one after the other into the output pipe. This is similar to the existing --merge-change task but simpler with no merge logic. It wouldn't have the conflictResolutionMethod argument, it would have a inputCount argument defining the number of inputs to append together.

Part 2

There needs to be a task similar to the --read-change-interval task for downloading and merging multiple full history files into a single change stream. I'd call it --read-history-interval.

Part 3

Re-factor the --read-change-interval and --read-history-interval tasks to be able to work from a local file system rather than downloading files from a http server and then working from temporary files.

comment:2 Changed 4 years ago by brett@…

  • Status changed from new to closed
  • Resolution set to fixed

Part 1

The --append-change task was created a long time ago.

Part 2

The --read-replication-interval task was created a long time ago.

Part 3

No re-factoring is required. A " file:///" URL can be specified instead. This does still cause temp files to be created, but the overhead is not large.

Note: See TracTickets for help on using tickets.