You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@doris.apache.org by ling miao <li...@apache.org> on 2020/10/26 11:38:29 UTC
[Proposal] Put some dependencies in our maintenance repo
Hi,
Currently, some fe dependencies that we rely on are not in the maven repo.
For example, cup-maven-plugin and java-cup are located at the Cloudera
3rd-P.
This will lead to the risk that our code will not be compiled when the
third-party repo changes.
I have also tried whether it is possible to replace these dependencies with
other packages or versions, but unfortunately the only thing we can use at
the moment is this.
So I propose whether we can maintain these jar packages in our own repo to
ensure that they can be found every time we compile?
Or do you have any better solutions?
Ling Miao
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by ling miao <em...@gmail.com>.
Hi Willem,
We rely on a plug-in called cup-maven-plugin.
This plugin is indeed maintained by Cloudera.
He did not put this plug-in in the mvn repo.
And Cloudera's repo often changes its address, which leads to this problem.
Or do we have any other solutions?
Ling Miao
Willem Jiang <wi...@gmail.com> 于2020年10月27日周二 下午2:48写道：
> Could you explain why we have these third party dependencies?
> Are they introduced by Cloudera's plugin?
>
> I don't think hosting these jars in our own repo is a good way to go :(
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Oct 26, 2020 at 7:38 PM ling miao <li...@apache.org> wrote:
> >
> > Hi,
> >
> > Currently, some fe dependencies that we rely on are not in the maven
> repo.
> > For example, cup-maven-plugin and java-cup are located at the Cloudera
> > 3rd-P.
> > This will lead to the risk that our code will not be compiled when the
> > third-party repo changes.
> >
> > I have also tried whether it is possible to replace these dependencies
> with
> > other packages or versions, but unfortunately the only thing we can use
> at
> > the moment is this.
> >
> > So I propose whether we can maintain these jar packages in our own repo
> to
> > ensure that they can be found every time we compile?
> >
> > Or do you have any better solutions?
> >
> > Ling Miao
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
> For additional commands, e-mail: dev-help@doris.apache.org
>
>
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by Willem Jiang <wi...@gmail.com>.
Could you explain why we have these third party dependencies?
Are they introduced by Cloudera's plugin?
I don't think hosting these jars in our own repo is a good way to go :(
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Oct 26, 2020 at 7:38 PM ling miao <li...@apache.org> wrote:
>
> Hi,
>
> Currently, some fe dependencies that we rely on are not in the maven repo.
> For example, cup-maven-plugin and java-cup are located at the Cloudera
> 3rd-P.
> This will lead to the risk that our code will not be compiled when the
> third-party repo changes.
>
> I have also tried whether it is possible to replace these dependencies with
> other packages or versions, but unfortunately the only thing we can use at
> the moment is this.
>
> So I propose whether we can maintain these jar packages in our own repo to
> ensure that they can be found every time we compile?
>
> Or do you have any better solutions?
>
> Ling Miao
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
For additional commands, e-mail: dev-help@doris.apache.org
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by ling miao <li...@apache.org>.
Putting the non-main repo addresses into env variables is OK.
But does this mean that users need to quote parameters when compiling?
Ling Miao
陈明雨 <mo...@163.com> 于2020年10月27日周二 上午11:24写道：
> Maintaining the jar ourselves may not be sustainable.
> I think we can solve the problem case by case.
> For example, we are currently encountering the problem of cloudera repo
> address changes.
> Can we consider turning all non-main repo addresses(such as Oracle,
> Cloudera repo) into environment variables?
> In this way, if the address changes, we can adapt by setting environment
> variables without modifying the code.
>
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmingyu@apache.org
>
>
>
>
>
> At 2020-10-26 19:38:29, "ling miao" <li...@apache.org> wrote:
> >Hi,
> >
> >Currently, some fe dependencies that we rely on are not in the maven repo.
> >For example, cup-maven-plugin and java-cup are located at the Cloudera
> >3rd-P.
> >This will lead to the risk that our code will not be compiled when the
> >third-party repo changes.
> >
> >I have also tried whether it is possible to replace these dependencies
> with
> >other packages or versions, but unfortunately the only thing we can use at
> >the moment is this.
> >
> >So I propose whether we can maintain these jar packages in our own repo to
> >ensure that they can be found every time we compile?
> >
> >Or do you have any better solutions?
> >
> >Ling Miao
>
Re:[Proposal] Put some dependencies in our maintenance repo
Posted by 陈明雨 <mo...@163.com>.
Maintaining the jar ourselves may not be sustainable.
I think we can solve the problem case by case.
For example, we are currently encountering the problem of cloudera repo address changes.
Can we consider turning all non-main repo addresses(such as Oracle, Cloudera repo) into environment variables?
In this way, if the address changes, we can adapt by setting environment variables without modifying the code.
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
At 2020-10-26 19:38:29, "ling miao" <li...@apache.org> wrote:
>Hi,
>
>Currently, some fe dependencies that we rely on are not in the maven repo.
>For example, cup-maven-plugin and java-cup are located at the Cloudera
>3rd-P.
>This will lead to the risk that our code will not be compiled when the
>third-party repo changes.
>
>I have also tried whether it is possible to replace these dependencies with
>other packages or versions, but unfortunately the only thing we can use at
>the moment is this.
>
>So I propose whether we can maintain these jar packages in our own repo to
>ensure that they can be found every time we compile?
>
>Or do you have any better solutions?
>
>Ling Miao
Re:Re: Re: [Proposal] Put some dependencies in our maintenance repo
Posted by 陈明雨 <mo...@163.com>.
>Please let us know if there is any news about it :)
Of course~
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
在 2020-11-05 16:22:23，"Willem Jiang" <wi...@gmail.com> 写道：
>Please let us know if there is any news about it :)
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willem
>
>On Wed, Nov 4, 2020 at 9:21 PM 陈明雨 <mo...@163.com> wrote:
>>
>> > Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
>>
>> That is a good idea!
>>
>>
>>
>> --
>>
>> 此致！Best Regards
>> 陈明雨 Mingyu Chen
>>
>> Email:
>> chenmingyu@apache.org
>>
>>
>>
>>
>>
>> 在 2020-11-03 17:13:09，"Willem Jiang" <wi...@gmail.com> 写道：
>> >+1 for it.
>> >It could save us lots of time by working with the upstream :)
>> >
>> >Willem Jiang
>> >
>> >Twitter: willemjiang
>> >Weibo: 姜宁willem
>> >
>> >On Tue, Nov 3, 2020 at 3:49 PM 41108453 <41...@qq.com> wrote:
>> >>
>> >> Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
>> >>
>> >>
>> >>
>> >>
>> >> ------------------ 原始邮件 ------------------
>> >> 发件人: "dev" <lingmiao@apache.org>;
>> >> 发送时间: 2020年10月28日(星期三) 下午4:48
>> >> 收件人: "dev"<dev@doris.apache.org>;
>> >>
>> >> 主题: Re: [Proposal] Put some dependencies in our maintenance repo
>> >>
>> >>
>> >>
>> >> Hi Duo,
>> >>
>> >> I found another dependency package with similar functions, let's see if I
>> >> can replace it.
>> >>
>> >> Regarding the question of Calcite, we have previously investigated Calcite
>> >> for Doris to optimize the query framework.
>> >> After the evaluation, it is found that the access cost may be similar to
>> >> the reconstruction of the entire query framework , so it is a long-term
>> >> work in the future.
>> >>
>> >> Ling Miao
>> >>
>> >>
>> >> 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午9:53写道：
>> >>
>> >> > Could be a long term solution? Is there any other reason which prevents us
>> >> > using Calcite?
>> >> >
>> >> > ling miao <lingmiao@apache.org> 于2020年10月27日周二 下午8:02写道：
>> >> >
>> >> > > Hi Duo,
>> >> > >
>> >> > > Using calcite directly will definitely not work, which means that the
>> >> > query
>> >> > > analysis + planning are rewritten.
>> >> > > But maybe we can use other parser tools to replace it, or something
>> >> > > similar.
>> >> > > However, it is estimated that the amount of change for this solution.
>> >> > > ...(｡•ˇ‸ˇ•｡)
>> >> > > ...
>> >> > >
>> >> > > Ling Miao
>> >> > >
>> >> > > 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午6:34写道：
>> >> > >
>> >> > > > I think this is used to generate the SQL parser? Is it possible to use
>> >> > > > Calcite directly?
>> >> > > >
>> >> > > > ling miao <lingmiao@apache.org> 于2020年10月26日周一 下午7:38写道：
>> >> > > >
>> >> > > > > Hi,
>> >> > > > >
>> >> > > > > Currently, some fe dependencies that we rely on are not in the maven
>> >> > > > repo.
>> >> > > > > For example, cup-maven-plugin and java-cup are located at the
>> >> > Cloudera
>> >> > > > > 3rd-P.
>> >> > > > > This will lead to the risk that our code will not be compiled when
>> >> > the
>> >> > > > > third-party repo changes.
>> >> > > > >
>> >> > > > > I have also tried whether it is possible to replace these
>> >> > dependencies
>> >> > > > > with other packages or versions, but unfortunately the only thing we
>> >> > > can
>> >> > > > > use at the moment is this.
>> >> > > > >
>> >> > > > > So I propose whether we can maintain these jar packages in our own
>> >> > repo
>> >> > > > to
>> >> > > > > ensure that they can be found every time we compile?
>> >> > > > >
>> >> > > > > Or do you have any better solutions?
>> >> > > > >
>> >> > > > > Ling Miao
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
>> >For additional commands, e-mail: dev-help@doris.apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
>For additional commands, e-mail: dev-help@doris.apache.org
Re: Re: [Proposal] Put some dependencies in our maintenance repo
Posted by Willem Jiang <wi...@gmail.com>.
Please let us know if there is any news about it :)
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Nov 4, 2020 at 9:21 PM 陈明雨 <mo...@163.com> wrote:
>
> > Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
>
> That is a good idea!
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmingyu@apache.org
>
>
>
>
>
> 在 2020-11-03 17:13:09，"Willem Jiang" <wi...@gmail.com> 写道：
> >+1 for it.
> >It could save us lots of time by working with the upstream :)
> >
> >Willem Jiang
> >
> >Twitter: willemjiang
> >Weibo: 姜宁willem
> >
> >On Tue, Nov 3, 2020 at 3:49 PM 41108453 <41...@qq.com> wrote:
> >>
> >> Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
> >>
> >>
> >>
> >>
> >> ------------------ 原始邮件 ------------------
> >> 发件人: "dev" <lingmiao@apache.org>;
> >> 发送时间: 2020年10月28日(星期三) 下午4:48
> >> 收件人: "dev"<dev@doris.apache.org>;
> >>
> >> 主题: Re: [Proposal] Put some dependencies in our maintenance repo
> >>
> >>
> >>
> >> Hi Duo,
> >>
> >> I found another dependency package with similar functions, let's see if I
> >> can replace it.
> >>
> >> Regarding the question of Calcite, we have previously investigated Calcite
> >> for Doris to optimize the query framework.
> >> After the evaluation, it is found that the access cost may be similar to
> >> the reconstruction of the entire query framework , so it is a long-term
> >> work in the future.
> >>
> >> Ling Miao
> >>
> >>
> >> 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午9:53写道：
> >>
> >> > Could be a long term solution? Is there any other reason which prevents us
> >> > using Calcite?
> >> >
> >> > ling miao <lingmiao@apache.org> 于2020年10月27日周二 下午8:02写道：
> >> >
> >> > > Hi Duo,
> >> > >
> >> > > Using calcite directly will definitely not work, which means that the
> >> > query
> >> > > analysis + planning are rewritten.
> >> > > But maybe we can use other parser tools to replace it, or something
> >> > > similar.
> >> > > However, it is estimated that the amount of change for this solution.
> >> > > ...(｡•ˇ‸ˇ•｡)
> >> > > ...
> >> > >
> >> > > Ling Miao
> >> > >
> >> > > 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午6:34写道：
> >> > >
> >> > > > I think this is used to generate the SQL parser? Is it possible to use
> >> > > > Calcite directly?
> >> > > >
> >> > > > ling miao <lingmiao@apache.org> 于2020年10月26日周一 下午7:38写道：
> >> > > >
> >> > > > > Hi,
> >> > > > >
> >> > > > > Currently, some fe dependencies that we rely on are not in the maven
> >> > > > repo.
> >> > > > > For example, cup-maven-plugin and java-cup are located at the
> >> > Cloudera
> >> > > > > 3rd-P.
> >> > > > > This will lead to the risk that our code will not be compiled when
> >> > the
> >> > > > > third-party repo changes.
> >> > > > >
> >> > > > > I have also tried whether it is possible to replace these
> >> > dependencies
> >> > > > > with other packages or versions, but unfortunately the only thing we
> >> > > can
> >> > > > > use at the moment is this.
> >> > > > >
> >> > > > > So I propose whether we can maintain these jar packages in our own
> >> > repo
> >> > > > to
> >> > > > > ensure that they can be found every time we compile?
> >> > > > >
> >> > > > > Or do you have any better solutions?
> >> > > > >
> >> > > > > Ling Miao
> >> > > > >
> >> > > >
> >> > >
> >> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
> >For additional commands, e-mail: dev-help@doris.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
For additional commands, e-mail: dev-help@doris.apache.org
Re:Re: [Proposal] Put some dependencies in our maintenance repo
Posted by 陈明雨 <mo...@163.com>.
> Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
That is a good idea!
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
在 2020-11-03 17:13:09，"Willem Jiang" <wi...@gmail.com> 写道：
>+1 for it.
>It could save us lots of time by working with the upstream :)
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willem
>
>On Tue, Nov 3, 2020 at 3:49 PM 41108453 <41...@qq.com> wrote:
>>
>> Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
>>
>>
>>
>>
>> ------------------ 原始邮件 ------------------
>> 发件人: "dev" <lingmiao@apache.org>;
>> 发送时间: 2020年10月28日(星期三) 下午4:48
>> 收件人: "dev"<dev@doris.apache.org>;
>>
>> 主题: Re: [Proposal] Put some dependencies in our maintenance repo
>>
>>
>>
>> Hi Duo,
>>
>> I found another dependency package with similar functions, let's see if I
>> can replace it.
>>
>> Regarding the question of Calcite, we have previously investigated Calcite
>> for Doris to optimize the query framework.
>> After the evaluation, it is found that the access cost may be similar to
>> the reconstruction of the entire query framework , so it is a long-term
>> work in the future.
>>
>> Ling Miao
>>
>>
>> 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午9:53写道：
>>
>> > Could be a long term solution? Is there any other reason which prevents us
>> > using Calcite?
>> >
>> > ling miao <lingmiao@apache.org> 于2020年10月27日周二 下午8:02写道：
>> >
>> > > Hi Duo,
>> > >
>> > > Using calcite directly will definitely not work, which means that the
>> > query
>> > > analysis + planning are rewritten.
>> > > But maybe we can use other parser tools to replace it, or something
>> > > similar.
>> > > However, it is estimated that the amount of change for this solution.
>> > > ...(｡•ˇ‸ˇ•｡)
>> > > ...
>> > >
>> > > Ling Miao
>> > >
>> > > 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午6:34写道：
>> > >
>> > > > I think this is used to generate the SQL parser? Is it possible to use
>> > > > Calcite directly?
>> > > >
>> > > > ling miao <lingmiao@apache.org> 于2020年10月26日周一 下午7:38写道：
>> > > >
>> > > > > Hi,
>> > > > >
>> > > > > Currently, some fe dependencies that we rely on are not in the maven
>> > > > repo.
>> > > > > For example, cup-maven-plugin and java-cup are located at the
>> > Cloudera
>> > > > > 3rd-P.
>> > > > > This will lead to the risk that our code will not be compiled when
>> > the
>> > > > > third-party repo changes.
>> > > > >
>> > > > > I have also tried whether it is possible to replace these
>> > dependencies
>> > > > > with other packages or versions, but unfortunately the only thing we
>> > > can
>> > > > > use at the moment is this.
>> > > > >
>> > > > > So I propose whether we can maintain these jar packages in our own
>> > repo
>> > > > to
>> > > > > ensure that they can be found every time we compile?
>> > > > >
>> > > > > Or do you have any better solutions?
>> > > > >
>> > > > > Ling Miao
>> > > > >
>> > > >
>> > >
>> >
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
>For additional commands, e-mail: dev-help@doris.apache.org
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by Willem Jiang <wi...@gmail.com>.
+1 for it.
It could save us lots of time by working with the upstream :)
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Tue, Nov 3, 2020 at 3:49 PM 41108453 <41...@qq.com> wrote:
>
> Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "dev" <lingmiao@apache.org>;
> 发送时间: 2020年10月28日(星期三) 下午4:48
> 收件人: "dev"<dev@doris.apache.org>;
>
> 主题: Re: [Proposal] Put some dependencies in our maintenance repo
>
>
>
> Hi Duo,
>
> I found another dependency package with similar functions, let's see if I
> can replace it.
>
> Regarding the question of Calcite, we have previously investigated Calcite
> for Doris to optimize the query framework.
> After the evaluation, it is found that the access cost may be similar to
> the reconstruction of the entire query framework , so it is a long-term
> work in the future.
>
> Ling Miao
>
>
> 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午9:53写道：
>
> > Could be a long term solution? Is there any other reason which prevents us
> > using Calcite?
> >
> > ling miao <lingmiao@apache.org> 于2020年10月27日周二 下午8:02写道：
> >
> > > Hi Duo,
> > >
> > > Using calcite directly will definitely not work, which means that the
> > query
> > > analysis + planning are rewritten.
> > > But maybe we can use other parser tools to replace it, or something
> > > similar.
> > > However, it is estimated that the amount of change for this solution.
> > > ...(｡•ˇ‸ˇ•｡)
> > > ...
> > >
> > > Ling Miao
> > >
> > > 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午6:34写道：
> > >
> > > > I think this is used to generate the SQL parser? Is it possible to use
> > > > Calcite directly?
> > > >
> > > > ling miao <lingmiao@apache.org> 于2020年10月26日周一 下午7:38写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > Currently, some fe dependencies that we rely on are not in the maven
> > > > repo.
> > > > > For example, cup-maven-plugin and java-cup are located at the
> > Cloudera
> > > > > 3rd-P.
> > > > > This will lead to the risk that our code will not be compiled when
> > the
> > > > > third-party repo changes.
> > > > >
> > > > > I have also tried whether it is possible to replace these
> > dependencies
> > > > > with other packages or versions, but unfortunately the only thing we
> > > can
> > > > > use at the moment is this.
> > > > >
> > > > > So I propose whether we can maintain these jar packages in our own
> > repo
> > > > to
> > > > > ensure that they can be found every time we compile?
> > > > >
> > > > > Or do you have any better solutions?
> > > > >
> > > > > Ling Miao
> > > > >
> > > >
> > >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@doris.apache.org
For additional commands, e-mail: dev-help@doris.apache.org
回复： [Proposal] Put some dependencies in our maintenance repo
Posted by 41108453 <41...@qq.com>.
Can you send an email to the cloudera maintenance team to explain this situation, and hope they will submit this to the central warehouse of maven
------------------ 原始邮件 ------------------
发件人: "dev" <lingmiao@apache.org>;
发送时间: 2020年10月28日(星期三) 下午4:48
收件人: "dev"<dev@doris.apache.org>;
主题: Re: [Proposal] Put some dependencies in our maintenance repo
Hi Duo,
I found another dependency package with similar functions, let's see if I
can replace it.
Regarding the question of Calcite, we have previously investigated Calcite
for Doris to optimize the query framework.
After the evaluation, it is found that the access cost may be similar to
the reconstruction of the entire query framework , so it is a long-term
work in the future.
Ling Miao
张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午9:53写道：
> Could be a long term solution? Is there any other reason which prevents us
> using Calcite?
>
> ling miao <lingmiao@apache.org> 于2020年10月27日周二 下午8:02写道：
>
> > Hi Duo,
> >
> > Using calcite directly will definitely not work, which means that the
> query
> > analysis + planning are rewritten.
> > But maybe we can use other parser tools to replace it, or something
> > similar.
> > However, it is estimated that the amount of change for this solution.
> > ...(｡•ˇ‸ˇ•｡)
> > ...
> >
> > Ling Miao
> >
> > 张铎(Duo Zhang) <palomino219@gmail.com> 于2020年10月27日周二 下午6:34写道：
> >
> > > I think this is used to generate the SQL parser? Is it possible to use
> > > Calcite directly?
> > >
> > > ling miao <lingmiao@apache.org> 于2020年10月26日周一 下午7:38写道：
> > >
> > > > Hi,
> > > >
> > > > Currently, some fe dependencies that we rely on are not in the maven
> > > repo.
> > > > For example, cup-maven-plugin and java-cup are located at the
> Cloudera
> > > > 3rd-P.
> > > > This will lead to the risk that our code will not be compiled when
> the
> > > > third-party repo changes.
> > > >
> > > > I have also tried whether it is possible to replace these
> dependencies
> > > > with other packages or versions, but unfortunately the only thing we
> > can
> > > > use at the moment is this.
> > > >
> > > > So I propose whether we can maintain these jar packages in our own
> repo
> > > to
> > > > ensure that they can be found every time we compile?
> > > >
> > > > Or do you have any better solutions?
> > > >
> > > > Ling Miao
> > > >
> > >
> >
>
Re:Re: [Proposal] Put some dependencies in our maintenance repo
Posted by 陈明雨 <mo...@163.com>.
Replacing the query optimizer is a long-term work, I think it is not within the scope of this discuss.
Our main concern here is how to ensure normal compilation when the address of the maven repo is changed.
Here I still suggest to turn this variable address into an environment variable, and update our compilation and deployment guide after the address changes,
so that users can solve the problem by adjusting the compilation parameters without modifying the code.
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
在 2020-10-28 16:48:36，"ling miao" <li...@apache.org> 写道：
>Hi Duo,
>
>I found another dependency package with similar functions, let's see if I
>can replace it.
>
>Regarding the question of Calcite, we have previously investigated Calcite
>for Doris to optimize the query framework.
>After the evaluation, it is found that the access cost may be similar to
>the reconstruction of the entire query framework , so it is a long-term
>work in the future.
>
>Ling Miao
>
>
>张铎(Duo Zhang) <pa...@gmail.com> 于2020年10月27日周二 下午9:53写道：
>
>> Could be a long term solution? Is there any other reason which prevents us
>> using Calcite?
>>
>> ling miao <li...@apache.org> 于2020年10月27日周二 下午8:02写道：
>>
>> > Hi Duo,
>> >
>> > Using calcite directly will definitely not work, which means that the
>> query
>> > analysis + planning are rewritten.
>> > But maybe we can use other parser tools to replace it, or something
>> > similar.
>> > However, it is estimated that the amount of change for this solution.
>> > ...(｡•ˇ‸ˇ•｡)
>> > ...
>> >
>> > Ling Miao
>> >
>> > 张铎(Duo Zhang) <pa...@gmail.com> 于2020年10月27日周二 下午6:34写道：
>> >
>> > > I think this is used to generate the SQL parser? Is it possible to use
>> > > Calcite directly?
>> > >
>> > > ling miao <li...@apache.org> 于2020年10月26日周一 下午7:38写道：
>> > >
>> > > > Hi,
>> > > >
>> > > > Currently, some fe dependencies that we rely on are not in the maven
>> > > repo.
>> > > > For example, cup-maven-plugin and java-cup are located at the
>> Cloudera
>> > > > 3rd-P.
>> > > > This will lead to the risk that our code will not be compiled when
>> the
>> > > > third-party repo changes.
>> > > >
>> > > > I have also tried whether it is possible to replace these
>> dependencies
>> > > > with other packages or versions, but unfortunately the only thing we
>> > can
>> > > > use at the moment is this.
>> > > >
>> > > > So I propose whether we can maintain these jar packages in our own
>> repo
>> > > to
>> > > > ensure that they can be found every time we compile?
>> > > >
>> > > > Or do you have any better solutions?
>> > > >
>> > > > Ling Miao
>> > > >
>> > >
>> >
>>
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by ling miao <li...@apache.org>.
Hi Duo,
I found another dependency package with similar functions, let's see if I
can replace it.
Regarding the question of Calcite, we have previously investigated Calcite
for Doris to optimize the query framework.
After the evaluation, it is found that the access cost may be similar to
the reconstruction of the entire query framework , so it is a long-term
work in the future.
Ling Miao
张铎(Duo Zhang) <pa...@gmail.com> 于2020年10月27日周二 下午9:53写道：
> Could be a long term solution? Is there any other reason which prevents us
> using Calcite?
>
> ling miao <li...@apache.org> 于2020年10月27日周二 下午8:02写道：
>
> > Hi Duo,
> >
> > Using calcite directly will definitely not work, which means that the
> query
> > analysis + planning are rewritten.
> > But maybe we can use other parser tools to replace it, or something
> > similar.
> > However, it is estimated that the amount of change for this solution.
> > ...(｡•ˇ‸ˇ•｡)
> > ...
> >
> > Ling Miao
> >
> > 张铎(Duo Zhang) <pa...@gmail.com> 于2020年10月27日周二 下午6:34写道：
> >
> > > I think this is used to generate the SQL parser? Is it possible to use
> > > Calcite directly?
> > >
> > > ling miao <li...@apache.org> 于2020年10月26日周一 下午7:38写道：
> > >
> > > > Hi,
> > > >
> > > > Currently, some fe dependencies that we rely on are not in the maven
> > > repo.
> > > > For example, cup-maven-plugin and java-cup are located at the
> Cloudera
> > > > 3rd-P.
> > > > This will lead to the risk that our code will not be compiled when
> the
> > > > third-party repo changes.
> > > >
> > > > I have also tried whether it is possible to replace these
> dependencies
> > > > with other packages or versions, but unfortunately the only thing we
> > can
> > > > use at the moment is this.
> > > >
> > > > So I propose whether we can maintain these jar packages in our own
> repo
> > > to
> > > > ensure that they can be found every time we compile?
> > > >
> > > > Or do you have any better solutions?
> > > >
> > > > Ling Miao
> > > >
> > >
> >
>
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
Could be a long term solution? Is there any other reason which prevents us
using Calcite?
ling miao <li...@apache.org> 于2020年10月27日周二 下午8:02写道：
> Hi Duo,
>
> Using calcite directly will definitely not work, which means that the query
> analysis + planning are rewritten.
> But maybe we can use other parser tools to replace it, or something
> similar.
> However, it is estimated that the amount of change for this solution.
> ...(｡•ˇ‸ˇ•｡)
> ...
>
> Ling Miao
>
> 张铎(Duo Zhang) <pa...@gmail.com> 于2020年10月27日周二 下午6:34写道：
>
> > I think this is used to generate the SQL parser? Is it possible to use
> > Calcite directly?
> >
> > ling miao <li...@apache.org> 于2020年10月26日周一 下午7:38写道：
> >
> > > Hi,
> > >
> > > Currently, some fe dependencies that we rely on are not in the maven
> > repo.
> > > For example, cup-maven-plugin and java-cup are located at the Cloudera
> > > 3rd-P.
> > > This will lead to the risk that our code will not be compiled when the
> > > third-party repo changes.
> > >
> > > I have also tried whether it is possible to replace these dependencies
> > > with other packages or versions, but unfortunately the only thing we
> can
> > > use at the moment is this.
> > >
> > > So I propose whether we can maintain these jar packages in our own repo
> > to
> > > ensure that they can be found every time we compile?
> > >
> > > Or do you have any better solutions?
> > >
> > > Ling Miao
> > >
> >
>
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by ling miao <li...@apache.org>.
Hi Duo,
Using calcite directly will definitely not work, which means that the query
analysis + planning are rewritten.
But maybe we can use other parser tools to replace it, or something
similar.
However, it is estimated that the amount of change for this solution.
...(｡•ˇ‸ˇ•｡)
...
Ling Miao
张铎(Duo Zhang) <pa...@gmail.com> 于2020年10月27日周二 下午6:34写道：
> I think this is used to generate the SQL parser? Is it possible to use
> Calcite directly?
>
> ling miao <li...@apache.org> 于2020年10月26日周一 下午7:38写道：
>
> > Hi,
> >
> > Currently, some fe dependencies that we rely on are not in the maven
> repo.
> > For example, cup-maven-plugin and java-cup are located at the Cloudera
> > 3rd-P.
> > This will lead to the risk that our code will not be compiled when the
> > third-party repo changes.
> >
> > I have also tried whether it is possible to replace these dependencies
> > with other packages or versions, but unfortunately the only thing we can
> > use at the moment is this.
> >
> > So I propose whether we can maintain these jar packages in our own repo
> to
> > ensure that they can be found every time we compile?
> >
> > Or do you have any better solutions?
> >
> > Ling Miao
> >
>
Re: [Proposal] Put some dependencies in our maintenance repo
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
I think this is used to generate the SQL parser? Is it possible to use
Calcite directly?
ling miao <li...@apache.org> 于2020年10月26日周一 下午7:38写道：
> Hi,
>
> Currently, some fe dependencies that we rely on are not in the maven repo.
> For example, cup-maven-plugin and java-cup are located at the Cloudera
> 3rd-P.
> This will lead to the risk that our code will not be compiled when the
> third-party repo changes.
>
> I have also tried whether it is possible to replace these dependencies
> with other packages or versions, but unfortunately the only thing we can
> use at the moment is this.
>
> So I propose whether we can maintain these jar packages in our own repo to
> ensure that they can be found every time we compile?
>
> Or do you have any better solutions?
>
> Ling Miao
>