But "." seems to be the most common way of expressing nested fields (indeed even SQL uses it). So it seems to be the best default, even if it causes problems in some cases.
This is another argument IMO for keeping the fieldNameFunction. Any name format I choose will break some use case, and I don't want 100 options to customize the format (e.g. customizing the separator character, etc.). This allows for the user to pick a different separator character trivially. [ Full content available at: https://github.com/apache/beam/pull/6316 ] This message was relayed via gitbox.apache.org for [email protected]
