[TS-4408] volume.config is ordering sensitive

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.0.0
• Component/s: Configuration
• Assignee: James Peach
• Reporter: James Peach
• Created: 02/May/16 17:36
• Updated: 07/Nov/16 23:27
• Resolved: 03/Jun/16 21:49

Description

volume.config is sensitive to the ordering of its fields. For example, this doesn't work:

volume=1 size=50% scheme=http

but this does:

volume=1 scheme=http size=50%

All the key=value configuration files are supposed to be ordering-insensitive.

Issue Links

• links to: GitHub Pull Request #618
• links to: GitHub Pull Request #618