Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/995
If we're going to the `docValues=false` + documentation route, we should
have the documentation be more generic than just the LatLon and Point (e.g.
custom types that may get used in more advanced use cases).
I'm also a little surprised that LatLon and Point are the only two types
that result in additional fields, given that there were more poly types listed
above. Do we know why Currency and other types don't result in additional
fields? Also, is there anything different under the hood about Points vs
LatLon?
General questions for people interested
* Are we okay with `docValues=false` and documenting (I personally am,
assuming we can provide relatively general guidance, not just something that
only works for a couple types).
* If LatLon and Point are the only two mainline fields that produce
subfields, should we also provide an example of suppressing the subfields of
Point, even though it's not in use right now?
---
