I've also created an issue (
https://github.com/apache/incubator-trafficcontrol/issues/1543) and
subsequent PR (https://github.com/apache/incubator-trafficcontrol/pull/1548)
to address the different requirements of each type of DS.
On Wed, Nov 15, 2017 at 3:10 PM, Jeremy Mitchell
I'm not a big fan of the ANY_MAP type DeliveryService. This is from
the documentation (basically the only information about this type):
"""
ANY_MAP is not known to Traffic Router. For this deliveryservice, the
“Raw remap text” field in the input form will be used as the remap
line on the cache.
If the field only applies to some DS types, it should be in its own table.
Then it can be NOT NULL in that table, ideally with a constraint requiring
the DS to be a type it applies to. You wanted to reduce the columns in the
`deliveryservice` table, right? Here's your chance :)
On Wed, Nov 15,
>From what I can tell, there are 4 flavors of delivery services:
1. DNS*
2. HTTP*
3. STEERING*
4. ANY_MAP
And the properties associated with each flavor vary so I put together a
spreadsheet to show which properties pertain to each flavor:
