Cheappie commented on issue #4517:
URL:
https://github.com/apache/arrow-datafusion/issues/4517#issuecomment-1351097017
I have a feeling that there is a `egg and chicken` problem in case of
`ConfigValue`, for example property name is necessary to get value from env,
but in order to get `name` it is necessary to have instance of `ConfigValue`
because `name` fn requires `&self`. I don't see a way to avoid having separate
definitions and values.
More strongly typed approach could be to define all properties as types,
```
struct TargetPartitionsDefinition { name: &'static str, description:
&'static str } impl { parse(...) -> ConfigValue }
enum ConfigValue { TargetPartitions(usize) }
```
--
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...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
