You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@doris.apache.org by 陈明雨 <mo...@163.com> on 2022/02/09 06:54:26 UTC
[Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Hi All:
Last month we try to release the doris flink/spakr connector 1.0.0[1]. But the VOTE has been cancelled because:
1. This release was not voted on dev@doris
2. The object of this release is the flink/spark connector, but the corresponding source code contains the main Doris code. This leads to unclear release output.
So I suggest to create a new repository for connectors. This way we can do a separate release for connector.
The only thing to note is that connectors relies on some thrift structures, and the main Doris code also relies on these structures.
So when these structures are updated, we need to synchronize the thrift files of both codebases.
But these files are usually rarely changed, so I think they are manageable.
Also, for Doris Manager, we still need a new repo for it.
the new repo name is :
1. github.com/apache/incubator-doris-connectors
2. github.com/apache/incubator-doris-manager
Please feel free to discuss. And you agree on it, please vote +1.
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
morningman@163.com;
morningman.cmy@gmail.com
Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by 王博 <wa...@gmail.com>.
+1
陈明雨 <mo...@163.com> 于2022年2月9日周三 14:54写道：
> Hi All:
>
>
> Last month we try to release the doris flink/spakr connector 1.0.0[1]. But
> the VOTE has been cancelled because:
> 1. This release was not voted on dev@doris
> 2. The object of this release is the flink/spark connector, but the
> corresponding source code contains the main Doris code. This leads to
> unclear release output.
>
>
> So I suggest to create a new repository for connectors. This way we can do
> a separate release for connector.
> The only thing to note is that connectors relies on some thrift
> structures, and the main Doris code also relies on these structures.
> So when these structures are updated, we need to synchronize the thrift
> files of both codebases.
> But these files are usually rarely changed, so I think they are manageable.
>
>
> Also, for Doris Manager, we still need a new repo for it.
>
>
> the new repo name is :
> 1. github.com/apache/incubator-doris-connectors
> 2. github.com/apache/incubator-doris-manager
>
>
> Please feel free to discuss. And you agree on it, please vote +1.
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> morningman@163.com;
> morningman.cmy@gmail.com
回复：[Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by 41108453 <41...@qq.com.INVALID>.
+1
It would indeed be better and clearer
------------------ 原始邮件 ------------------
发件人: "dev" <morningman@163.com>;
发送时间: 2022年2月9日(星期三) 下午2:54
收件人: "doris-dev"<dev@doris.apache.org>;
主题: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Hi All:
Last month we try to release the doris flink/spakr connector 1.0.0[1]. But the VOTE has been cancelled because:
1. This release was not voted on dev@doris
2. The object of this release is the flink/spark connector, but the corresponding source code contains the main Doris code. This leads to unclear release output.
So I suggest to create a new repository for connectors. This way we can do a separate release for connector.
The only thing to note is that connectors relies on some thrift structures, and the main Doris code also relies on these structures.
So when these structures are updated, we need to synchronize the thrift files of both codebases.
But these files are usually rarely changed, so I think they are manageable.
Also, for Doris Manager, we still need a new repo for it.
the new repo name is :
1. github.com/apache/incubator-doris-connectors
2. github.com/apache/incubator-doris-manager
Please feel free to discuss. And you agree on it, please vote +1.
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
morningman@163.com;
morningman.cmy@gmail.com
Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by Willem Jiang <wi...@gmail.com>.
If we just separate the code base which is already in the ASF repo, we
don't need to go through the IP clearance process[1]
Otherwise, we need to go through the IP clearance process.
The incubating project Doris can have multiple repos, we just need to
make sure the repo name starts with incubator-doris- .
[1]https://incubator.apache.org/guides/ip_clearance.html
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Feb 9, 2022 at 3:37 PM ling miao <li...@apache.org> wrote:
>
> As a project that has been incubated in the apache foundation,
> what process do we need to go through to open a new codebase for a new
> component?
>
> Secondly, if the connector and manager are going to be released,
> are they separate from Doris?
> If so, is the process the same as Doris?
>
> Ling Miao
>
> 蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
>
> > +1, That sounds more reasonable
> >
> > At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
> > >Hi All:
> > >
> > >
> > >Last month we try to release the doris flink/spakr connector 1.0.0[1].
> > But the VOTE has been cancelled because:
> > >1. This release was not voted on dev@doris
> > >2. The object of this release is the flink/spark connector, but the
> > corresponding source code contains the main Doris code. This leads to
> > unclear release output.
> > >
> > >
> > >So I suggest to create a new repository for connectors. This way we can
> > do a separate release for connector.
> > >The only thing to note is that connectors relies on some thrift
> > structures, and the main Doris code also relies on these structures.
> > >So when these structures are updated, we need to synchronize the thrift
> > files of both codebases.
> > >But these files are usually rarely changed, so I think they are
> > manageable.
> > >
> > >
> > >Also, for Doris Manager, we still need a new repo for it.
> > >
> > >
> > >the new repo name is :
> > >1. github.com/apache/incubator-doris-connectors
> > >2. github.com/apache/incubator-doris-manager
> > >
> > >
> > >Please feel free to discuss. And you agree on it, please vote +1.
> > >
> > >
> > >
> > >--
> > >
> > >此致！Best Regards
> > >陈明雨 Mingyu Chen
> > >
> > >Email:
> > >morningman@163.com;
> > >morningman.cmy@gmail.com
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
For additional commands, e-mail: dev-help@doris.apache.org
Re: Re: Re: Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by Lijia Liu <li...@gmail.com>.
+1
weizuo <we...@apache.org> 于2022年2月10日周四 11:23写道：
> +1
>
>
>
>
> Zuo Wei
>
>
>
>
>
>
>
>
>
>
>
> 在 2022-02-10 11:19:47，"Yun Tang" <ta...@apache.org> 写道：
> >+1 for creating external repos to hold ecosystem code.
> >
> >Best
> >Yun Tang
> >
> >On 2022/02/10 01:21:39 寒江雪 wrote:
> >> +1
> >>
> >> 陈明雨 <mo...@163.com> 于2022年2月9日周三 21:08写道：
> >>
> >> > >This sounds great, so can we do a separate release for Doris manager
> >> > >without Doris ?I think yes
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > 此致！Best Regards
> >> > 陈明雨 Mingyu Chen
> >> >
> >> > Email:
> >> > chenmingyu@apache.org
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > 在 2022-02-09 16:19:48，"ling miao" <li...@apache.org> 写道：
> >> > >> This is just a separate repo, not a separate project. A project
> can has
> >> > >many release output, but all need to follow the release process.
> >> > >This sounds great, so can we do a separate release for Doris manager
> >> > >without Doris ?
> >> > >
> >> > >Ling Miao
> >> > >
> >> > >陈明雨 <mo...@163.com> 于2022年2月9日周三 16:03写道：
> >> > >
> >> > >> >As a project that has been incubated in the apache foundation,
> >> > >> >what process do we need to go through to open a new codebase for
> a new
> >> > >> >component?
> >> > >>
> >> > >> The mentor has permission to create new repo. I will apply for it
> after
> >> > >> this vote.
> >> > >> >Secondly, if the connector and manager are going to be released,
> >> > >> >are they separate from Doris?
> >> > >> >If so, is the process the same as Doris?
> >> > >> This is just a separate repo, not a separate project. A project
> can has
> >> > >> many release output, but all need to follow the release process.
> >> > >>
> >> > >> --
> >> > >>
> >> > >> 此致！Best Regards
> >> > >> 陈明雨 Mingyu Chen
> >> > >>
> >> > >> Email:
> >> > >> chenmingyu@apache.org
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >> 在 2022-02-09 15:37:29，"ling miao" <li...@apache.org> 写道：
> >> > >> >As a project that has been incubated in the apache foundation,
> >> > >> >what process do we need to go through to open a new codebase for
> a new
> >> > >> >component?
> >> > >> >
> >> > >> >Secondly, if the connector and manager are going to be released,
> >> > >> >are they separate from Doris?
> >> > >> >If so, is the process the same as Doris?
> >> > >> >
> >> > >> >Ling Miao
> >> > >> >
> >> > >> >蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
> >> > >> >
> >> > >> >> +1, That sounds more reasonable
> >> > >> >>
> >> > >> >> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
> >> > >> >> >Hi All:
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >Last month we try to release the doris flink/spakr connector
> >> > 1.0.0[1].
> >> > >> >> But the VOTE has been cancelled because:
> >> > >> >> >1. This release was not voted on dev@doris
> >> > >> >> >2. The object of this release is the flink/spark connector,
> but the
> >> > >> >> corresponding source code contains the main Doris code. This
> leads to
> >> > >> >> unclear release output.
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >So I suggest to create a new repository for connectors. This
> way we
> >> > can
> >> > >> >> do a separate release for connector.
> >> > >> >> >The only thing to note is that connectors relies on some thrift
> >> > >> >> structures, and the main Doris code also relies on these
> structures.
> >> > >> >> >So when these structures are updated, we need to synchronize
> the
> >> > thrift
> >> > >> >> files of both codebases.
> >> > >> >> >But these files are usually rarely changed, so I think they are
> >> > >> >> manageable.
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >Also, for Doris Manager, we still need a new repo for it.
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >the new repo name is :
> >> > >> >> >1. github.com/apache/incubator-doris-connectors
> >> > >> >> >2. github.com/apache/incubator-doris-manager
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >Please feel free to discuss. And you agree on it, please vote
> +1.
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >--
> >> > >> >> >
> >> > >> >> >此致！Best Regards
> >> > >> >> >陈明雨 Mingyu Chen
> >> > >> >> >
> >> > >> >> >Email:
> >> > >> >> >morningman@163.com;
> >> > >> >> >morningman.cmy@gmail.com
> >> > >> >>
> >> > >>
> >> >
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
> >For additional commands, e-mail: dev-help@doris.apache.org
> >
>
Re:Re: Re: Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by weizuo <we...@apache.org>.
+1
Zuo Wei
在 2022-02-10 11:19:47，"Yun Tang" <ta...@apache.org> 写道：
>+1 for creating external repos to hold ecosystem code.
>
>Best
>Yun Tang
>
>On 2022/02/10 01:21:39 寒江雪 wrote:
>> +1
>>
>> 陈明雨 <mo...@163.com> 于2022年2月9日周三 21:08写道：
>>
>> > >This sounds great, so can we do a separate release for Doris manager
>> > >without Doris ?I think yes
>> >
>> >
>> >
>> > --
>> >
>> > 此致！Best Regards
>> > 陈明雨 Mingyu Chen
>> >
>> > Email:
>> > chenmingyu@apache.org
>> >
>> >
>> >
>> >
>> >
>> > 在 2022-02-09 16:19:48，"ling miao" <li...@apache.org> 写道：
>> > >> This is just a separate repo, not a separate project. A project can has
>> > >many release output, but all need to follow the release process.
>> > >This sounds great, so can we do a separate release for Doris manager
>> > >without Doris ?
>> > >
>> > >Ling Miao
>> > >
>> > >陈明雨 <mo...@163.com> 于2022年2月9日周三 16:03写道：
>> > >
>> > >> >As a project that has been incubated in the apache foundation,
>> > >> >what process do we need to go through to open a new codebase for a new
>> > >> >component?
>> > >>
>> > >> The mentor has permission to create new repo. I will apply for it after
>> > >> this vote.
>> > >> >Secondly, if the connector and manager are going to be released,
>> > >> >are they separate from Doris?
>> > >> >If so, is the process the same as Doris?
>> > >> This is just a separate repo, not a separate project. A project can has
>> > >> many release output, but all need to follow the release process.
>> > >>
>> > >> --
>> > >>
>> > >> 此致！Best Regards
>> > >> 陈明雨 Mingyu Chen
>> > >>
>> > >> Email:
>> > >> chenmingyu@apache.org
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> 在 2022-02-09 15:37:29，"ling miao" <li...@apache.org> 写道：
>> > >> >As a project that has been incubated in the apache foundation,
>> > >> >what process do we need to go through to open a new codebase for a new
>> > >> >component?
>> > >> >
>> > >> >Secondly, if the connector and manager are going to be released,
>> > >> >are they separate from Doris?
>> > >> >If so, is the process the same as Doris?
>> > >> >
>> > >> >Ling Miao
>> > >> >
>> > >> >蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
>> > >> >
>> > >> >> +1, That sounds more reasonable
>> > >> >>
>> > >> >> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
>> > >> >> >Hi All:
>> > >> >> >
>> > >> >> >
>> > >> >> >Last month we try to release the doris flink/spakr connector
>> > 1.0.0[1].
>> > >> >> But the VOTE has been cancelled because:
>> > >> >> >1. This release was not voted on dev@doris
>> > >> >> >2. The object of this release is the flink/spark connector, but the
>> > >> >> corresponding source code contains the main Doris code. This leads to
>> > >> >> unclear release output.
>> > >> >> >
>> > >> >> >
>> > >> >> >So I suggest to create a new repository for connectors. This way we
>> > can
>> > >> >> do a separate release for connector.
>> > >> >> >The only thing to note is that connectors relies on some thrift
>> > >> >> structures, and the main Doris code also relies on these structures.
>> > >> >> >So when these structures are updated, we need to synchronize the
>> > thrift
>> > >> >> files of both codebases.
>> > >> >> >But these files are usually rarely changed, so I think they are
>> > >> >> manageable.
>> > >> >> >
>> > >> >> >
>> > >> >> >Also, for Doris Manager, we still need a new repo for it.
>> > >> >> >
>> > >> >> >
>> > >> >> >the new repo name is :
>> > >> >> >1. github.com/apache/incubator-doris-connectors
>> > >> >> >2. github.com/apache/incubator-doris-manager
>> > >> >> >
>> > >> >> >
>> > >> >> >Please feel free to discuss. And you agree on it, please vote +1.
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> >--
>> > >> >> >
>> > >> >> >此致！Best Regards
>> > >> >> >陈明雨 Mingyu Chen
>> > >> >> >
>> > >> >> >Email:
>> > >> >> >morningman@163.com;
>> > >> >> >morningman.cmy@gmail.com
>> > >> >>
>> > >>
>> >
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
>For additional commands, e-mail: dev-help@doris.apache.org
>
Re: Re: Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by Yun Tang <ta...@apache.org>.
+1 for creating external repos to hold ecosystem code.
Best
Yun Tang
On 2022/02/10 01:21:39 寒江雪 wrote:
> +1
>
> 陈明雨 <mo...@163.com> 于2022年2月9日周三 21:08写道：
>
> > >This sounds great, so can we do a separate release for Doris manager
> > >without Doris ?I think yes
> >
> >
> >
> > --
> >
> > 此致！Best Regards
> > 陈明雨 Mingyu Chen
> >
> > Email:
> > chenmingyu@apache.org
> >
> >
> >
> >
> >
> > 在 2022-02-09 16:19:48，"ling miao" <li...@apache.org> 写道：
> > >> This is just a separate repo, not a separate project. A project can has
> > >many release output, but all need to follow the release process.
> > >This sounds great, so can we do a separate release for Doris manager
> > >without Doris ?
> > >
> > >Ling Miao
> > >
> > >陈明雨 <mo...@163.com> 于2022年2月9日周三 16:03写道：
> > >
> > >> >As a project that has been incubated in the apache foundation,
> > >> >what process do we need to go through to open a new codebase for a new
> > >> >component?
> > >>
> > >> The mentor has permission to create new repo. I will apply for it after
> > >> this vote.
> > >> >Secondly, if the connector and manager are going to be released,
> > >> >are they separate from Doris?
> > >> >If so, is the process the same as Doris?
> > >> This is just a separate repo, not a separate project. A project can has
> > >> many release output, but all need to follow the release process.
> > >>
> > >> --
> > >>
> > >> 此致！Best Regards
> > >> 陈明雨 Mingyu Chen
> > >>
> > >> Email:
> > >> chenmingyu@apache.org
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> 在 2022-02-09 15:37:29，"ling miao" <li...@apache.org> 写道：
> > >> >As a project that has been incubated in the apache foundation,
> > >> >what process do we need to go through to open a new codebase for a new
> > >> >component?
> > >> >
> > >> >Secondly, if the connector and manager are going to be released,
> > >> >are they separate from Doris?
> > >> >If so, is the process the same as Doris?
> > >> >
> > >> >Ling Miao
> > >> >
> > >> >蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
> > >> >
> > >> >> +1, That sounds more reasonable
> > >> >>
> > >> >> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
> > >> >> >Hi All:
> > >> >> >
> > >> >> >
> > >> >> >Last month we try to release the doris flink/spakr connector
> > 1.0.0[1].
> > >> >> But the VOTE has been cancelled because:
> > >> >> >1. This release was not voted on dev@doris
> > >> >> >2. The object of this release is the flink/spark connector, but the
> > >> >> corresponding source code contains the main Doris code. This leads to
> > >> >> unclear release output.
> > >> >> >
> > >> >> >
> > >> >> >So I suggest to create a new repository for connectors. This way we
> > can
> > >> >> do a separate release for connector.
> > >> >> >The only thing to note is that connectors relies on some thrift
> > >> >> structures, and the main Doris code also relies on these structures.
> > >> >> >So when these structures are updated, we need to synchronize the
> > thrift
> > >> >> files of both codebases.
> > >> >> >But these files are usually rarely changed, so I think they are
> > >> >> manageable.
> > >> >> >
> > >> >> >
> > >> >> >Also, for Doris Manager, we still need a new repo for it.
> > >> >> >
> > >> >> >
> > >> >> >the new repo name is :
> > >> >> >1. github.com/apache/incubator-doris-connectors
> > >> >> >2. github.com/apache/incubator-doris-manager
> > >> >> >
> > >> >> >
> > >> >> >Please feel free to discuss. And you agree on it, please vote +1.
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >--
> > >> >> >
> > >> >> >此致！Best Regards
> > >> >> >陈明雨 Mingyu Chen
> > >> >> >
> > >> >> >Email:
> > >> >> >morningman@163.com;
> > >> >> >morningman.cmy@gmail.com
> > >> >>
> > >>
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
For additional commands, e-mail: dev-help@doris.apache.org
Re: Re: Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by 寒江雪 <ya...@gmail.com>.
+1
陈明雨 <mo...@163.com> 于2022年2月9日周三 21:08写道：
> >This sounds great, so can we do a separate release for Doris manager
> >without Doris ?I think yes
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmingyu@apache.org
>
>
>
>
>
> 在 2022-02-09 16:19:48，"ling miao" <li...@apache.org> 写道：
> >> This is just a separate repo, not a separate project. A project can has
> >many release output, but all need to follow the release process.
> >This sounds great, so can we do a separate release for Doris manager
> >without Doris ?
> >
> >Ling Miao
> >
> >陈明雨 <mo...@163.com> 于2022年2月9日周三 16:03写道：
> >
> >> >As a project that has been incubated in the apache foundation,
> >> >what process do we need to go through to open a new codebase for a new
> >> >component?
> >>
> >> The mentor has permission to create new repo. I will apply for it after
> >> this vote.
> >> >Secondly, if the connector and manager are going to be released,
> >> >are they separate from Doris?
> >> >If so, is the process the same as Doris?
> >> This is just a separate repo, not a separate project. A project can has
> >> many release output, but all need to follow the release process.
> >>
> >> --
> >>
> >> 此致！Best Regards
> >> 陈明雨 Mingyu Chen
> >>
> >> Email:
> >> chenmingyu@apache.org
> >>
> >>
> >>
> >>
> >>
> >> 在 2022-02-09 15:37:29，"ling miao" <li...@apache.org> 写道：
> >> >As a project that has been incubated in the apache foundation,
> >> >what process do we need to go through to open a new codebase for a new
> >> >component?
> >> >
> >> >Secondly, if the connector and manager are going to be released,
> >> >are they separate from Doris?
> >> >If so, is the process the same as Doris?
> >> >
> >> >Ling Miao
> >> >
> >> >蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
> >> >
> >> >> +1, That sounds more reasonable
> >> >>
> >> >> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
> >> >> >Hi All:
> >> >> >
> >> >> >
> >> >> >Last month we try to release the doris flink/spakr connector
> 1.0.0[1].
> >> >> But the VOTE has been cancelled because:
> >> >> >1. This release was not voted on dev@doris
> >> >> >2. The object of this release is the flink/spark connector, but the
> >> >> corresponding source code contains the main Doris code. This leads to
> >> >> unclear release output.
> >> >> >
> >> >> >
> >> >> >So I suggest to create a new repository for connectors. This way we
> can
> >> >> do a separate release for connector.
> >> >> >The only thing to note is that connectors relies on some thrift
> >> >> structures, and the main Doris code also relies on these structures.
> >> >> >So when these structures are updated, we need to synchronize the
> thrift
> >> >> files of both codebases.
> >> >> >But these files are usually rarely changed, so I think they are
> >> >> manageable.
> >> >> >
> >> >> >
> >> >> >Also, for Doris Manager, we still need a new repo for it.
> >> >> >
> >> >> >
> >> >> >the new repo name is :
> >> >> >1. github.com/apache/incubator-doris-connectors
> >> >> >2. github.com/apache/incubator-doris-manager
> >> >> >
> >> >> >
> >> >> >Please feel free to discuss. And you agree on it, please vote +1.
> >> >> >
> >> >> >
> >> >> >
> >> >> >--
> >> >> >
> >> >> >此致！Best Regards
> >> >> >陈明雨 Mingyu Chen
> >> >> >
> >> >> >Email:
> >> >> >morningman@163.com;
> >> >> >morningman.cmy@gmail.com
> >> >>
> >>
>
Re:Re: Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by 陈明雨 <mo...@163.com>.
>This sounds great, so can we do a separate release for Doris manager
>without Doris ?I think yes
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
在 2022-02-09 16:19:48，"ling miao" <li...@apache.org> 写道：
>> This is just a separate repo, not a separate project. A project can has
>many release output, but all need to follow the release process.
>This sounds great, so can we do a separate release for Doris manager
>without Doris ?
>
>Ling Miao
>
>陈明雨 <mo...@163.com> 于2022年2月9日周三 16:03写道：
>
>> >As a project that has been incubated in the apache foundation,
>> >what process do we need to go through to open a new codebase for a new
>> >component?
>>
>> The mentor has permission to create new repo. I will apply for it after
>> this vote.
>> >Secondly, if the connector and manager are going to be released,
>> >are they separate from Doris?
>> >If so, is the process the same as Doris?
>> This is just a separate repo, not a separate project. A project can has
>> many release output, but all need to follow the release process.
>>
>> --
>>
>> 此致！Best Regards
>> 陈明雨 Mingyu Chen
>>
>> Email:
>> chenmingyu@apache.org
>>
>>
>>
>>
>>
>> 在 2022-02-09 15:37:29，"ling miao" <li...@apache.org> 写道：
>> >As a project that has been incubated in the apache foundation,
>> >what process do we need to go through to open a new codebase for a new
>> >component?
>> >
>> >Secondly, if the connector and manager are going to be released,
>> >are they separate from Doris?
>> >If so, is the process the same as Doris?
>> >
>> >Ling Miao
>> >
>> >蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
>> >
>> >> +1, That sounds more reasonable
>> >>
>> >> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
>> >> >Hi All:
>> >> >
>> >> >
>> >> >Last month we try to release the doris flink/spakr connector 1.0.0[1].
>> >> But the VOTE has been cancelled because:
>> >> >1. This release was not voted on dev@doris
>> >> >2. The object of this release is the flink/spark connector, but the
>> >> corresponding source code contains the main Doris code. This leads to
>> >> unclear release output.
>> >> >
>> >> >
>> >> >So I suggest to create a new repository for connectors. This way we can
>> >> do a separate release for connector.
>> >> >The only thing to note is that connectors relies on some thrift
>> >> structures, and the main Doris code also relies on these structures.
>> >> >So when these structures are updated, we need to synchronize the thrift
>> >> files of both codebases.
>> >> >But these files are usually rarely changed, so I think they are
>> >> manageable.
>> >> >
>> >> >
>> >> >Also, for Doris Manager, we still need a new repo for it.
>> >> >
>> >> >
>> >> >the new repo name is :
>> >> >1. github.com/apache/incubator-doris-connectors
>> >> >2. github.com/apache/incubator-doris-manager
>> >> >
>> >> >
>> >> >Please feel free to discuss. And you agree on it, please vote +1.
>> >> >
>> >> >
>> >> >
>> >> >--
>> >> >
>> >> >此致！Best Regards
>> >> >陈明雨 Mingyu Chen
>> >> >
>> >> >Email:
>> >> >morningman@163.com;
>> >> >morningman.cmy@gmail.com
>> >>
>>
Re: Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by ling miao <li...@apache.org>.
> This is just a separate repo, not a separate project. A project can has
many release output, but all need to follow the release process.
This sounds great, so can we do a separate release for Doris manager
without Doris ?
Ling Miao
陈明雨 <mo...@163.com> 于2022年2月9日周三 16:03写道：
> >As a project that has been incubated in the apache foundation,
> >what process do we need to go through to open a new codebase for a new
> >component?
>
> The mentor has permission to create new repo. I will apply for it after
> this vote.
> >Secondly, if the connector and manager are going to be released,
> >are they separate from Doris?
> >If so, is the process the same as Doris?
> This is just a separate repo, not a separate project. A project can has
> many release output, but all need to follow the release process.
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmingyu@apache.org
>
>
>
>
>
> 在 2022-02-09 15:37:29，"ling miao" <li...@apache.org> 写道：
> >As a project that has been incubated in the apache foundation,
> >what process do we need to go through to open a new codebase for a new
> >component?
> >
> >Secondly, if the connector and manager are going to be released,
> >are they separate from Doris?
> >If so, is the process the same as Doris?
> >
> >Ling Miao
> >
> >蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
> >
> >> +1, That sounds more reasonable
> >>
> >> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
> >> >Hi All:
> >> >
> >> >
> >> >Last month we try to release the doris flink/spakr connector 1.0.0[1].
> >> But the VOTE has been cancelled because:
> >> >1. This release was not voted on dev@doris
> >> >2. The object of this release is the flink/spark connector, but the
> >> corresponding source code contains the main Doris code. This leads to
> >> unclear release output.
> >> >
> >> >
> >> >So I suggest to create a new repository for connectors. This way we can
> >> do a separate release for connector.
> >> >The only thing to note is that connectors relies on some thrift
> >> structures, and the main Doris code also relies on these structures.
> >> >So when these structures are updated, we need to synchronize the thrift
> >> files of both codebases.
> >> >But these files are usually rarely changed, so I think they are
> >> manageable.
> >> >
> >> >
> >> >Also, for Doris Manager, we still need a new repo for it.
> >> >
> >> >
> >> >the new repo name is :
> >> >1. github.com/apache/incubator-doris-connectors
> >> >2. github.com/apache/incubator-doris-manager
> >> >
> >> >
> >> >Please feel free to discuss. And you agree on it, please vote +1.
> >> >
> >> >
> >> >
> >> >--
> >> >
> >> >此致！Best Regards
> >> >陈明雨 Mingyu Chen
> >> >
> >> >Email:
> >> >morningman@163.com;
> >> >morningman.cmy@gmail.com
> >>
>
Re:Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by 陈明雨 <mo...@163.com>.
>As a project that has been incubated in the apache foundation,
>what process do we need to go through to open a new codebase for a new
>component?
The mentor has permission to create new repo. I will apply for it after this vote.
>Secondly, if the connector and manager are going to be released,
>are they separate from Doris?
>If so, is the process the same as Doris?
This is just a separate repo, not a separate project. A project can has many release output, but all need to follow the release process.
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
在 2022-02-09 15:37:29，"ling miao" <li...@apache.org> 写道：
>As a project that has been incubated in the apache foundation,
>what process do we need to go through to open a new codebase for a new
>component?
>
>Secondly, if the connector and manager are going to be released,
>are they separate from Doris?
>If so, is the process the same as Doris?
>
>Ling Miao
>
>蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
>
>> +1, That sounds more reasonable
>>
>> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
>> >Hi All:
>> >
>> >
>> >Last month we try to release the doris flink/spakr connector 1.0.0[1].
>> But the VOTE has been cancelled because:
>> >1. This release was not voted on dev@doris
>> >2. The object of this release is the flink/spark connector, but the
>> corresponding source code contains the main Doris code. This leads to
>> unclear release output.
>> >
>> >
>> >So I suggest to create a new repository for connectors. This way we can
>> do a separate release for connector.
>> >The only thing to note is that connectors relies on some thrift
>> structures, and the main Doris code also relies on these structures.
>> >So when these structures are updated, we need to synchronize the thrift
>> files of both codebases.
>> >But these files are usually rarely changed, so I think they are
>> manageable.
>> >
>> >
>> >Also, for Doris Manager, we still need a new repo for it.
>> >
>> >
>> >the new repo name is :
>> >1. github.com/apache/incubator-doris-connectors
>> >2. github.com/apache/incubator-doris-manager
>> >
>> >
>> >Please feel free to discuss. And you agree on it, please vote +1.
>> >
>> >
>> >
>> >--
>> >
>> >此致！Best Regards
>> >陈明雨 Mingyu Chen
>> >
>> >Email:
>> >morningman@163.com;
>> >morningman.cmy@gmail.com
>>
Re: [Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by ling miao <li...@apache.org>.
As a project that has been incubated in the apache foundation,
what process do we need to go through to open a new codebase for a new
component?
Secondly, if the connector and manager are going to be released,
are they separate from Doris?
If so, is the process the same as Doris?
Ling Miao
蔡聪辉 <ca...@163.com> 于2022年2月9日周三 15:13写道：
> +1, That sounds more reasonable
>
> At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
> >Hi All:
> >
> >
> >Last month we try to release the doris flink/spakr connector 1.0.0[1].
> But the VOTE has been cancelled because:
> >1. This release was not voted on dev@doris
> >2. The object of this release is the flink/spark connector, but the
> corresponding source code contains the main Doris code. This leads to
> unclear release output.
> >
> >
> >So I suggest to create a new repository for connectors. This way we can
> do a separate release for connector.
> >The only thing to note is that connectors relies on some thrift
> structures, and the main Doris code also relies on these structures.
> >So when these structures are updated, we need to synchronize the thrift
> files of both codebases.
> >But these files are usually rarely changed, so I think they are
> manageable.
> >
> >
> >Also, for Doris Manager, we still need a new repo for it.
> >
> >
> >the new repo name is :
> >1. github.com/apache/incubator-doris-connectors
> >2. github.com/apache/incubator-doris-manager
> >
> >
> >Please feel free to discuss. And you agree on it, please vote +1.
> >
> >
> >
> >--
> >
> >此致！Best Regards
> >陈明雨 Mingyu Chen
> >
> >Email:
> >morningman@163.com;
> >morningman.cmy@gmail.com
>
Re:[Discuss & Vote] Create a new repo for Doris Flink/Spark Connector and Manager
Posted by 蔡聪辉 <ca...@163.com>.
+1, That sounds more reasonable
At 2022-02-09 14:54:26, "陈明雨" <mo...@163.com> wrote:
>Hi All:
>
>
>Last month we try to release the doris flink/spakr connector 1.0.0[1]. But the VOTE has been cancelled because:
>1. This release was not voted on dev@doris
>2. The object of this release is the flink/spark connector, but the corresponding source code contains the main Doris code. This leads to unclear release output.
>
>
>So I suggest to create a new repository for connectors. This way we can do a separate release for connector.
>The only thing to note is that connectors relies on some thrift structures, and the main Doris code also relies on these structures.
>So when these structures are updated, we need to synchronize the thrift files of both codebases.
>But these files are usually rarely changed, so I think they are manageable.
>
>
>Also, for Doris Manager, we still need a new repo for it.
>
>
>the new repo name is :
>1. github.com/apache/incubator-doris-connectors
>2. github.com/apache/incubator-doris-manager
>
>
>Please feel free to discuss. And you agree on it, please vote +1.
>
>
>
>--
>
>此致！Best Regards
>陈明雨 Mingyu Chen
>
>Email:
>morningman@163.com;
>morningman.cmy@gmail.com