Jackie-Jiang commented on PR #8600: URL: https://github.com/apache/pinot/pull/8600#issuecomment-1111554014
I don't think this is the correct fix. It is valid to have `fieldsToUnnest` as `null` when we don't want to unnest any field. I don't think this is a bug, but a user config error. When user puts the config, it means user wants to flatten the json field, but unnest is optional. I don't see a good way to prevent this. One option is to add a flag to enable the map flattening, but that is backward incompatible change, and IMO that should be implicit when user puts the complex config. cc @yupeng9 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
