Ok, thanks Viraj.
Hopefully you can place here like all other how it's maintained. Let me know
any help required on this. May be we can name it as bdp-select. Or (bgp-select)
https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
On 30/08/22, 5:26 AM, "Viraj Jasani" <vjas...@apache.org> wrote:
Masatake, Brahma,
Hopefully I should be able to create Jira and PR in Bigtop. Will let you
know once ready for review. Thanks
On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki
<iwasak...@oss.nttdata.com>
wrote:
> Please file a JIRA and submit a pull request if you want to show the code
> and get feedback.
> There is nothing I want to discuss off the record.
>
> On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> the final conclusion on this..?
> >
> > Please let me know your availability, Can have one call to discuss on
> this..
> >
> >
> > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
<bbatt...@visa.com.INVALID>
> wrote:
> >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is
> so small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> thread.
> >
> >
> > Sure, Viraj or me can show the code to you.
> >
> > Can we've call on this Friday/Thrusday if that works..?
> >
> >
> > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> iwasak...@oss.nttdata.com> wrote:
> >
> > > Sure, we can havemodule name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> >
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is
so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
> >
> > Masatake Iwasaki
> >
> > On 2022/07/11 8:23, Kengo Seki wrote:
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> > >
> > > Oh, I interpreted your words "conclude" and "finalize" as
you
> were
> > > going to make a final decision. Brainstorming is welcome, of
> course.
> > > (But I'm not so sure if all people concerned could join, due
> to time
> > > difference and their schedule, etc.)
> > >
> > >> Can you suggest, how the changes will be also.. like
folder,
> where you suggest to keep this...?
> > >
> > > Sure, here's my proposal:
> > >
> > > * Stack name: "BIGTOP"
> > >
> > > - The same name as the existing one [1]
> > > - Because it deploys the packages generated by Bigtop
> > > - The existing stack should be replaced with it, because
> that is
> > > based on Bigtop 0.8 and too old to use now
> > > - No concern about infringing others' trademark
> > >
> > > * Component/folder name: "bigtop-select"
> > >
> > > - Consistent naming convention with the existing tools
> such as
> > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > > might be an option, for example
"bigtop-ambari-stack-selector"
> > >
> > > * Script name: "bigtop-select"
> > >
> > > - Consistent with the stack name
> > > - No concern about infringing others' trademark
> > >
> > > [1]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sOGC38xRa2H2AYhpz1XxwyiBwwYUfEw87soznjX9fmI%3D&reserved=0
> > > [2]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CKqWD99nsiBrKv3IZtZXInadLmVzatK3zsSQxWkbLX4%3D&reserved=0
> > >
> > > Kengo Seki <sek...@apache.org>
> > >
> > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > <bbatt...@visa.com.invalid> wrote:
> > >>
> > >>> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >>> as described in the "Open Communications" section of [1]
> and [2].
> > >> > So we should conclude the discussion in this mailing
> list.
> > >> > (And with my poor English, I'm not so confident to
catch
> up with your
> > >> > fluent talk ;)
> > >>
> > >> I believe , I knew the apache way which you mentioned. We
> are not going conclude anything which comes to bigtop other than this
> mailing list.
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking
let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> > >>
> > >> I think, whiteboarding will help to catch up with you.
> > >>
> > >> You all the think "bigtop-select" will be best option
> right..? Can you suggest, how the changes will be also.. like folder,
where
> you suggest to keep this...?
> > >>
> > >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> > >>
> > >> @Viraj Jasani and others any thoughts..?
> > >>
> > >>
> > >> On 10/07/22, 11:03 AM, "Kengo Seki" <sek...@apache.org>
> wrote:
> > >>
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >>
> > >> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >> as described in the "Open Communications" section of
> [1] and [2].
> > >> So we should conclude the discussion in this mailing
> list.
> > >> (And with my poor English, I'm not so confident to
> catch up with your
> > >> fluent talk ;)
> > >>
> > >> > FYI. Even looks bigtop used some where also..
> > >>
> > >> Bigtop is ASF's trademark as you can see in the
"Apache
> Bigtop®
> > >> software" section of [3].
> > >> So it doesn't have the risk of trademark infringement.
> > >>
> > >> [1]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VnSOJv998y6BR%2B%2B3gEwt3gC4ajiqxR3yxv%2FMuym14OI%3D&reserved=0
> > >> [2]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z8lzba6TN%2FCgEXb%2FfBK6Fc6P%2FD74ICMmrGo8O8%2BvmsU%3D&reserved=0
> > >> [3]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CFeD4ngXC7I8E6v0GcV9LmD0KLlOfL3jsrWcwj%2BibWA%3D&reserved=0
> > >>
> > >> Kengo Seki <sek...@apache.org>
> > >>
> > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > >> <bbatt...@visa.com.invalid> wrote:
> > >> >
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >> >
> > >> > FYI. Even looks bigtop used some where[1] also..
> > >> > 1.
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F0Fa4qQC1DwyNDUqBamzb7eCZSphpuxQ%2FqWkE10w%2F3o%3D&reserved=0(Microsoft_product)
> > >> >
> > >> >
> > >> > On 08/07/22, 8:06 PM, "Kengo Seki"
<sek...@apache.org>
> wrote:
> > >> >
> > >> > Thank you for your explanation, Brahma.
> > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> [1]) is supposed to be a
> > >> > trademark of Redoop, so they can name the script
> crh-select without
> > >> > problem.
> > >> > But regarding BDP for example, I can easily find
> products that have
> > >> > the same name [2][3][4] as you already
mentioned,
> so I'd like to
> > >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> > >> > Or, a single and more general word just like
> conf-select may be less
> > >> > troublesome than bdp. How about "stack-select",
> for example?
> > >> >
> > >> > [1]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dy6I2wH2aSIkQKa9fJX7nDbbUWjQ07aTvcdSZXCGCYM%3D&reserved=0
> > >> > [2]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sE%2Fb5kum9UIOQQ1NonfA0ZZk04cghtU%2BYIpvLf1mofo%3D&reserved=0
> > >> > [3]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ey61twpiXZXBJ10YFWhmBWV4w8KyQ4NadpM5itom83Q%3D&reserved=0
> > >> > [4]:
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AzmiiA7TLiJmWR2M0iD%2BQJnS9XZrCU5t2K7KjipzvDg%3D&reserved=0
> > >> >
> > >> > Kengo Seki <sek...@apache.org>
> > >> >
> > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> Reddy <bbatt...@visa.com> wrote:
> > >> > >
> > >> > > >Do you mean that you're going to name the
> module (same as "component"
> > >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > >and still the script in question
> bdp-select? If so, is there any
> > >> > > >reason that the script must be that name?
> > >> > > >(No offence, I just want to understand
> your thoughts and its
> > >> > > >background, and avoid the conflict or
> user's confusion with existing
> > >> > > >trademarks or products)
> > >> > >
> > >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the
components
> hence planning to have like bdp,bds...and this only one file like
below[1]
> which has done redoop.
> > >> > >
> > >> > >
> > >> > >
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dNFPGfC2F9DUoKX3TPGwTiz4%2BQXacQ4FZzr3%2B6eHLRg%3D&reserved=0
> > >> > >
> > >> > >
> > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sek...@apache.org> wrote:
> > >> > >
> > >> > > The following concern Masatake mentioned
> before is an important point,
> > >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> > >> > > yesterday.
> > >> > >
> > >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> > >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> > >> > > > for addressing this.
> > >> > >
> > >> > > > I don't like to bring the awkward
package
> name convention to Bigtop
> > >> > > > at least by default.
> > >> > >
> > >> > > He's planning to adopt the same mitigation
> as HDP for now, but he
> > >> > > doesn't intend to change the default
> package naming convention of
> > >> > > Bigtop,
> > >> > > but just add a new functionality to
include
> an extra part into the
> > >> > > package name for avoiding conflict, which
> is disabled by default.
> > >> > >
> > >> > > And Brahma, let me confirm about the
> following reply:
> > >> > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > >
> > >> > > Do you mean that you're going to name the
> module (same as "component"
> > >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > and still the script in question
> bdp-select? If so, is there any
> > >> > > reason that the script must be that name?
> > >> > > (No offence, I just want to understand
your
> thoughts and its
> > >> > > background, and avoid the conflict or
> user's confusion with existing
> > >> > > trademarks or products)
> > >> > >
> > >> > > Kengo Seki <sek...@apache.org>
> > >> > >
> > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> Brahma Reddy
> > >> > > <bbatt...@visa.com.invalid> wrote:
> > >> > > >
> > >> > > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > > If you can not accept the name
like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > > > Initially we'll do this separate branch.
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki"
<
> iwasak...@oss.nttdata.co.jp> wrote:
> > >> > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > >
> > >> > > > projects and products.
> > >> > > >
> > >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > >
> > >> > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > >
> > >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> > >> > > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > > >
> > >> > > > >
> > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iwasak...@oss.nttdata.co.jp> wrote:
> > >> > > > >
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > >
> > >> > > > > Not fine.
> > >> > > > > We have a trademark policy.
> > >> > > > >
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XQM8jgnE0tJRSDpjDELPXw1%2B%2Fsq0forEMVS15aYgWbg%3D&reserved=0
> > >> > > > >
> > >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> > >> > > > > >> Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > >> ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >> > > > > >
> > >> > > > > > Finally thanks a bunch for
> long healthy discussions on this. Mostly we all same page now.
> > >> > > > > >
> > >> > > > > > 1.
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGtYy%2B6poKMJ62Cp9vrrjiou1YrciQ7ow0RFU1vTQRA%3D&reserved=0
> > >> > > > > >
> > >> > > > > > 2.
>
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ucOrDSTO2EiSbVb67pmT3d7w4OBv%2BPpckx5KDdc8%2FWU%3D&reserved=0
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On 06/07/22, 4:01 AM,
> "Masatake Iwasaki" <iwasak...@oss.nttdata.co.jp> wrote:
> > >> > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > >
> > >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > > ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > On 2022/06/29 13:52,
> Viraj Jasani wrote:
> > >> > > > > > > Hi Ambari/Bigtop
dev,
> > >> > > > > > >
> > >> > > > > > > As per the new
> roadmap of Apache Ambari, we would like to propose moving
> > >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> > >> > > > > > > so that their rpm
> installation could be managed independently.
> > >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> > >> > > > > > > installation of
> various Bigdata packages. The only major changes they would
> > >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> > >> > > > > > > usually do not
> receive updates. In the past, we used to get hdp-select rpm
> > >> > > > > > > downloaded and
> installed from HDP repositories.
> > >> > > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> ---------------------------------------------------------------------
> > >> > > > To unsubscribe, e-mail:
> dev-unsubscr...@ambari.apache.org
> > >> > > > For additional commands, e-mail:
> dev-h...@ambari.apache.org
> > >> > > >
> > >> > >
> > >> > >
> ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail:
> dev-unsubscr...@ambari.apache.org
> > >> > > For additional commands, e-mail:
> dev-h...@ambari.apache.org
> > >> > >
> > >> > >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail:
> dev-unsubscr...@ambari.apache.org
> > >> > For additional commands, e-mail:
> dev-h...@ambari.apache.org
> > >> >
> > >> >
> > >>
> > >>
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> dev-unsubscr...@ambari.apache.org
> > >> For additional commands, e-mail:
> dev-h...@ambari.apache.org
> > >>
> > >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org
> > For additional commands, e-mail: dev-h...@ambari.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org
For additional commands, e-mail: dev-h...@ambari.apache.org
