+1 to generally renaming the packages. Since this is about renaming for the purpose of making it user friendly, I am concerned if we make this as hudi-query-bundle, users might get confused with other modules like hudi-hive and hudi-spark. And inside packaging module, we further have bundles specific to spark, hive and presto.
Any suggestions on how to rename broadly to avoid these confusions? Let me also think and get back. Thanks, Sudha On Wed, Jan 15, 2020 at 9:56 PM vino yang <[email protected]> wrote: > Hi guys, > > I want to start a proposal about refactoring the naming of the > "hudi-hadoop-mr" module. > > IMHO, this module name is not user-friendly. It may make users confused. > Because it looks like that it's about integrating with MapReduce( although > I know it referenced parquet-mr[1] project). > > Based on the purpose of this module (contains InputFormat implementations > for ReadOptimized, Incremental, Realtime views). > > I suggest that we can rename it to "*hudi-query-common*". Then, we can also > rename "hudi-hadoop-mr-bundle" to "*hudi-query-bundle*". > > What do you think? > > Any thoughts and suggestions are welcome and appreciated. > > Best, > Vino > > [1]: > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_parquet-2Dmr&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=oyPDRKU5b-LuEWWyf8gacx4mFFydIGdyS50OKdxizX0&m=dmZJgDEuo5sZCNsoyMRQUpiJoBP7u4r2i8cdHDMmQic&s=4CnBhu54QxDqAWdCb3NXUdQg9beV2xEmgx-N0yhTr9Y&e= >
