gt; 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"
> >>
> >> >> 发送时间: 2020年10月28日(星期三) 下午4:48
> >> 收件人: "dev" >>
>>"dev"
>>
>> > 发送时间: 2020年10月28日(星期三) 下午4:48
>> 收件人: "dev">
>> 主题: Re: [Proposal] Put some dependencies in our maintena
"dev"
>
> 发送时间: 2020年10月28日(星期三) 下午4:48
> 收件人: "dev"
> 主题: Re: [Proposal] Put some dependencies in our maintenance repo
>
>
>
> Hi Duo,
>
> I found another dependency package with similar func
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
-- 原始邮件 --
发件人:
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 u
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 reco
Could be a long term solution? Is there any other reason which prevents us
using Calcite?
ling miao 于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 t
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
张铎
I think this is used to generate the SQL parser? Is it possible to use
Calcite directly?
ling miao 于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.
> Thi
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 于2020年10月27日
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 wrote:
>
> Hi,
>
> Current
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
陈明雨 于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
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 variabl
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
15 matches
Mail list logo
