hudi-bot opened a new issue, #15783: URL: https://github.com/apache/hudi/issues/15783
Nearly all configs are strings, but there are a few that use other classes or primitives. For example hoodie.schema.cache.enable is of type Boolean, while most boolean configs just take "true" or "false." Another example is hoodie.markers.timeline_server_based.batch.num_threads is of type Integer while most configs are again string ## JIRA info - Link: https://issues.apache.org/jira/browse/HUDI-5762 - Type: Improvement - Epic: https://issues.apache.org/jira/browse/HUDI-5738 - Fix version(s): - 1.1.0 --- ## Comments 27/Feb/24 07:14;geserdugarov;[~jonvex], [~guoyihua], [~pwason], [~shivnarayan], Do we really need to unify config types? It is not right as mentioned in the description that nearly all config are strings. I've looked at commit d0929341d0ad25b3ce587d7f229d2fcdf7796768, Feb 26, 2024. We have about 900 configuration parameters in Hudi, among them: * string - 580 parameters, * boolean - 139, * integer - 121, * long - 30, * double - 12, * float - 2, * other - 13 (HoodieTableType, KafkaResetOffsetStrategies, etc.) It looks that we should not transform parameters to string type.;;; -- 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]
