[
https://issues.apache.org/jira/browse/TS-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820918#comment-13820918
]
ASF subversion and git services commented on TS-2343:
-----------------------------------------------------
Commit 7d469d00efe3500ce826b427221007feca2144fb in branch refs/heads/master
from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=7d469d0 ]
Added TS-2343.
> Remove the --schema option from Traffic Manager
> -----------------------------------------------
>
> Key: TS-2343
> URL: https://issues.apache.org/jira/browse/TS-2343
> Project: Traffic Server
> Issue Type: Improvement
> Components: Management
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 4.2.0
>
>
> There's a "-schema" option for traffic_manager, which is only partially
> implemented (and we have no default scheme file to provide for it). From what
> I can surmise, the intent was to allow for a schema based validation of
> records.config.
> Now, I suspect this -schema option was done prior to RecordsConfig.cc
> refactoring. As such, I feel it's unnecessary, since RecordsConfig supports
> validation "rules" for each configuration.
> Finally, since this feature has no usable configurations or features, I
> suggest eliminating it for v4.2.0, but I could be convinced to move it out
> for v5.0.x.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
