geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Swapnil Bawaskar <sbawas...@pivotal.io>
Subject Re: [DISCUSS] GEODE-3617 Replace gemfire prefix with geode
Date Tue, 19 Sep 2017 21:58:10 GMT
In the interest of keeping the re-branding tasks together, I took the
liberty to made GEODE-3617 a subtask of
https://issues.apache.org/jira/browse/GEODE-1466.

On Tue, Sep 19, 2017 at 2:05 PM Dave Barnes <dbarnes@pivotal.io> wrote:

> Here's an updated link to the properties spreadsheet that should have wider
> viewability:
>
>
> https://docs.google.com/spreadsheets/d/1C2D7cpcYMy5bd0aXXReJn6wWsBuLZrCegl7_cevvKo0/edit?usp=sharing
>
> On Tue, Sep 19, 2017 at 12:10 PM, Dave Barnes <dbarnes@pivotal.io> wrote:
>
> > There's no single list of "all properties". Here's one that Tech Pubs
> last
> > reviewed about 6 months ago...
> >
> > https://docs.google.com/spreadsheets/d/1C2D7cpcYMy5bd0aXXReJn6wWsBuLZ
> > rCegl7_cevvKo0/edit#gid=0
> >
> >
> > On Thu, Sep 14, 2017 at 12:06 PM, Bruce Schuchardt <
> bschuchardt@pivotal.io
> > > wrote:
> >
> >> There are plenty of places besides DistributionConfig that use "gemfire"
> >> prefixed system properties and there are now also places that use
> "geode"
> >> prefixed system properties.  I think the whole mess needs to be managed
> and
> >> allow either prefix, or even as someone suggested making it plug-able.
> >> There is also an HTML file that, now out of date, lists most of these
> >> system properties.
> >>
> >>
> >>
> >> On 9/14/17 10:14 AM, Darrel Schneider wrote:
> >>
> >>> +1 to having DistributionConfig look for both the "gemfire." and
> "geode."
> >>> prefixes.
> >>> +1 to having DistributionConfig look for both a "gemfire.properties"
> and
> >>> "geode.properties" file.
> >>> Since the geode flavors are newer it should look for them first and
> only
> >>> look for the old gemfire flavor if a geode one is not found.
> >>>
> >>> On Thu, Sep 14, 2017 at 9:35 AM, Kirk Lund <klund@apache.org> wrote:
> >>>
> >>> That's a bigger change and I'm not sure how you would handle backwards
> >>>> compatibility for users using gemfire.properties.
> >>>>
> >>>> On Thu, Sep 14, 2017 at 9:15 AM, Jacob Barrett <jbarrett@pivotal.io>
> >>>> wrote:
> >>>>
> >>>> Or better yet, we stop using properties files already.
> >>>>>
> >>>>> On Thu, Sep 14, 2017 at 8:55 AM Dave Barnes <dbarnes@pivotal.io>
> >>>>> wrote:
> >>>>>
> >>>>> Is there a possibility that the code might find its way into
> additional
> >>>>>> contexts with other names? If so, perhaps we should consider
a more
> >>>>>>
> >>>>> generic
> >>>>>
> >>>>>> identifier, such as PRODUCT_PREFIX.
> >>>>>>
> >>>>>> On Thu, Sep 14, 2017 at 4:42 AM, Dinesh Akhand <dineshak@amdocs.com
> >
> >>>>>> wrote:
> >>>>>>
> >>>>>> Hi,
> >>>>>>>
> >>>>>>> Why we are keeping gemfire in current geode 1.2 , Can we
replace
> this
> >>>>>>>
> >>>>>> with
> >>>>>>
> >>>>>>> GEODE
> >>>>>>> File : DistributionConfig.java
> >>>>>>>
> >>>>>>> Current code:
> >>>>>>>    String GEMFIRE_PREFIX = "gemfire.";
> >>>>>>>
> >>>>>>> Suggestion to change:
> >>>>>>>   String GEODE_PREFIX = "geode.";
> >>>>>>>
> >>>>>>> Why do you think ?
> >>>>>>> Can we go ahead  and change this ?
> >>>>>>> It will impact lots of files & all configuration will
be now using
> >>>>>>>
> >>>>>> with
> >>>>
> >>>>> geode.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Dinesh Akhand
> >>>>>>> This message and the information contained herein is proprietary
> and
> >>>>>>> confidential and subject to the Amdocs policy statement,
> >>>>>>>
> >>>>>>> you may review at https://www.amdocs.com/about/email-disclaimer
<
> >>>>>>> https://www.amdocs.com/about/email-disclaimer>
> >>>>>>>
> >>>>>>>
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message