Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMjXoANgAWym=go7xstdbPJ4c2YPwhP=mWqEzgcozeB0Xk3BSQ@mail.gmail.com>
References: <FC70888C-B832-43E8-BEBD-FDCB4FE8BCF5@gmail.com>
 <CA+HpHOikskkxcm5-yF8dhGOkN6EkxF2f4QC57q1XJrf+2tyE0w@mail.gmail.com>
 <CA+ULb+t49QQ7vt70GP_wzrW=27nhaFo5ZDbJubTepK2GaaOvkg@mail.gmail.com>
 <CABQrizc=YOepXdFJouh_bZmN2CHtL2=Fiws-5dPMXneXdUF12A@mail.gmail.com>
 <CABRJdxtgqjoWVZptCW=j254+Ap0ehcDGpWEy2uHDGtTMAgonJg@mail.gmail.com>
 <CALkokyViz1i=o80JjUJzXpoA_Y__BGmgCiPTfX3Jt9wB3qELog@mail.gmail.com> <CAMjXoANgAWym=go7xstdbPJ4c2YPwhP=mWqEzgcozeB0Xk3BSQ@mail.gmail.com>
From: Lili Ma <lilima@apache.org>
Date: Wed, 13 Jul 2016 14:01:23 +0800
Message-ID: <CAB-r6_wDCCyHjboTcubcbocKoL8DJgYU7ZqiddF_M7nHTaqheQ@mail.gmail.com>
Subject: Re: Rename "greenplum" to "hawq"
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113df6ac87258a05377e1df6
archived-at: Wed, 13 Jul 2016 06:01:30 -0000

--001a113df6ac87258a05377e1df6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

For the command line tools name, what about we keep greenplum_path.sh and
add a hawq_env.sh and inside hawq_env.sh, we call greenplum_path.sh. So the
already user won't need to change their behavior, and new user can directly
use the new hawq named script?

For the environment variable, for example GPHOME=EF=BC=8Ccan we create a ne=
w
variable HAWQHOME, and set it the same value as GPHOME?


Thanks
Lili

2016-07-13 13:55 GMT+08:00 Yi Jin <yjin@pivotal.io>:

> I think it is a must-do, but some concerns of customer using convention a=
nd
> legacy applications, scripts etc.
>
> On Wed, Jul 13, 2016 at 1:44 PM, =E9=99=B6=E5=BE=81=E9=9C=96 <ztao1987@ap=
ache.org> wrote:
>
> > Good idea, but need quite a lot of effort and may also affect custormer
> > behavior. Should handle it carefully.
> >
> > 2016-07-13 9:54 GMT+08:00 Ivan Weng <iweng@pivotal.io>:
> >
> > > Agree with this good idea. But as Paul said, there are maybe already
> many
> > > users use greeenplum_path.sh or something else in their environment. =
So
> > we
> > > need to think about it.
> > >
> > >
> > > Regards,
> > > Ivan
> > >
> > > On Wed, Jul 13, 2016 at 9:31 AM, Paul Guo <paulguo@gmail.com> wrote:
> > >
> > > > I've asked this before. Seems that affects some old users. I'm not
> sure
> > > > about the details.
> > > > I agree that we should change it to a better name in a release.
> > > >
> > > > 2016-07-13 9:25 GMT+08:00 Roman Shaposhnik <roman@shaposhnik.org>:
> > > >
> > > > > On Tue, Jul 12, 2016 at 6:21 PM, Xiang Sheng <xsheng@pivotal.io>
> > > wrote:
> > > > > > Agree . @xunzhang.
> > > > > > However , some greenplum strings can be easily replaced , but
> there
> > > are
> > > > > too
> > > > > > many in the code or comments.  Changing all of them costs too
> much
> > > > > efforts.
> > > > > >
> > > > > > So changing the strings that users can see is enough.
> > > > >
> > > > > Huge +1 to this! Btw, is this something we may be able to tackle =
in
> > our
> > > > > next Apache release?
> > > > >
> > > > > Thanks,
> > > > > Roman.
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Thanks,
> > Zhenglin
> >
>

--001a113df6ac87258a05377e1df6--