Do we really need to customize naming in the first iteration? I suggest 
removing `CONCAT_FIELD_NAMES` and `KEEP_NESTED_NAME`, they have a 
[YAGNI](https://martinfowler.com/bliki/Yagni.html) smell. My opinion is that 
documentation of how naming behaves should be enough to start with, and then we 
could add policies later if needed. Or we could make the two behaviors a flag 
for now, e.g. `concatFieldNames()` vs `useLeafFieldName()`, I think it would be 
clearer to the users

[ Full content available at: https://github.com/apache/beam/pull/6316 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to