zhuqi-lucas commented on issue #16903: URL: https://github.com/apache/datafusion/issues/16903#issuecomment-3118232799
I agree we need a better solution: 1. For high level, currently, we default to mapping sql level string/varchar/char/text to utf8view when we create table, we can use config to control this, but most function has hard coded to return or transform to utf8view. 2. For low level, we only have config to force reading to utf8view for parquet when we infer schema. I am wandering if we can investigate something like force reading to utf8 if we want to transform? 3. The unified solution for all level, i agree @alamb , we may need to have a feature flag, but it's very huge work. > and particularly in builtin functions where it is not feasible to access the SessionContext and make a return type by runtime configuration. Any other solutions? Is it possible for us to investigate the SessionContext to support runtime configuration? May be additional field or metadata store, i don't have some ideas about this until now. -- 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
