Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/995
For the integration test, adding the specific dynamic fields for the
underlying LatLon seems to take care of the problem for that type.
e.g. this makes the test you added pass:
```
<!-- Catch all, if we don't know about it, it gets dropped. -->
<dynamicField name="*_coordinate" type="pdouble" indexed="true"
stored="false" docValues="false"/>
<dynamicField name="*" type="ignored" multiValued="false"
docValues="true"/>
```
It appears docValues is not disabled for the subfields, because they get
caught by the "*" dynamic fields, so they end up being `docValues=true`.
My concern would be making sure we document what has to happen for LatLon,
and making sure that the other types you laid out can be managed in a similar
way (and document appropriately),
---
