Hi Shubham, I would recommend we hold on this change until we have fully understanding of the affects and the benefit we can get.
I can think about below items: - Require a lot of changes to development CI and Test cases. - Require changes of user defined scripts and cases. - Might affect the user who are using GPDB clients to access HAWQ. - Might affect other projects which are related to HAWQ, e.g. Madlib. - It's better to have such changes at a major release, like 3.0. So this is my opinion, welcome other comments. Thanks. Regards, Radar On Mon, Sep 4, 2017 at 8:45 AM, Shubham Sharma <[email protected]> wrote: > Hi, > > HAWQ-421 describes the confusion created by GPHOME and greenplum_path.sh, > which also seems out of place with the project name HAWQ. This issue is > marked as backlog for a while and I wanted to take the opportunity to > replace these references with something related to our project. > > Since these changes almost touch the entire project and the naming changes > will stick going on forward, wanted to bounce off some ideas with the > community, let me know which naming convention sounds better. > > 1 - Replace GPHOME with > > a - HAWQHOME > b - HAWQ_HOME > c - HAWQ_CONF_DIR > > 2 - Replace greenplum_path.sh with > > a - hawq_env.sh > b - hawq_path.sh > > I prefer 1-b and 2-a > > Please feel free to add other options. Appreciate your inputs. > > -- > Regards, > Shubham >
