Page MenuHomePhabricator

incremental dumps: don't hardcode export-0.8.xsd
Open, LowPublic

Description

Allow xsd to be an option specified, with a reasonable default; for XML files being converted, read it from the XML and store it somewhere in the bindump format; for live dumps produced from the db think of something else. FIgure out what to do when applying incremental produced with newer xsd to full produced with older xsd.


Version: unspecified
Severity: normal

Details

Reference
bz54635

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:17 AM
bzimport set Reference to bz54635.

Also investigate what XML do incremental dumps produce when the input is in older format. If the output doesn't fir the older XSD, document the differences.

Svick: This issue has been assigned to you a while ago.
Could you please provide a status update and inform us whether you are still working (or still plan to work) on this issue?
Only in case you do not plan to work on this issue anymore, should the assignee be set back to default?

Nemo_bis lowered the priority of this task from Medium to Low.Apr 9 2015, 7:20 AM
Nemo_bis set Security to None.

Moving this to Dumps-Rewrite project; if we keep/reuse this code it won't be in the context of the current dumps.

Aklapper added a subscriber: Svick.

@Svick: I am resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!).
Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task.
Please claim this task again when you plan to work on it (via Add Action...Assign / Claim in the dropdown menu) - it would be welcome! Thanks for your understanding!