berkaysynnada commented on PR #13576:
URL: https://github.com/apache/datafusion/pull/13576#issuecomment-2538929543

   > If the option has hard-coded normalization (eg lowercasing), it means 
there is no difference between certain values (eg those differing in case). Why 
would a user be concerned about that? It feels you didn't describe a use-case 
fully, or I didn't quite understand it.
   
   If an option accepts a file name and is coded to normalize the input to 
snake_case (which applies to most data file naming conventions), but for a 
specific file type snake_case normalization is not preferable, the user might 
want to retain the original naming style. Can that be a valid example?


-- 
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: github-unsubscr...@datafusion.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org

Reply via email to