alamb opened a new issue, #11650: URL: https://github.com/apache/datafusion/issues/11650
### Is your feature request related to a problem or challenge? on https://github.com/apache/datafusion/pull/11330#issuecomment-2246242461, @ozankabak says > We would like to have key-level control on what normalization means for config options, built-in and extension. ### Describe the solution you'd like Allow users of DataFusion to 1. Provide a new set of ConfigOptions (not in DataFusion) that have custom normalization rules 2. Avoid normalization on some of the built in configs? ### Describe alternatives you've considered The code from @berkaysynnada in https://github.com/synnada-ai/datafusion-upstream/commit/341b48458c09f25d2a5873fcee2fce18eb0e1097 I think seems to show a way to add an annotation to a built in config setting value that controls how it will be normalized. ### Additional context This is a follow on to https://github.com/apache/datafusion/pull/11330 where we implemented all-or-nothing value normalization -- 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]
