[DISCUSS] How to reduce the size of the binary package?

[Goson zhang <go...@apache.org>]

Hi all:

This release of version 1.2.0 found that the expansion of the binary
package is relatively large, exceeding the maximum allowable range of 1G
after base64 encoding set by the system, at the same time, it is impossible
for us to always apply to increase this maximum limit, that is, each The
release package needs to be controlled within 800M, otherwise the version
release will be stuck.

I would like to invite everyone to take a look at this problem and see how
to solve it: whether the released binary package only contains the most
basic and core modules and processes, and for non-essential auxiliary
modules and branch processes, we set it as source code release, so that
Compile when users configure and use on-demand?

Looking forward to your opinion, thanks!

Re: [DISCUSS] How to reduce the size of the binary package?

[Heal Chow <he...@apache.org>]

Yes, in the future, the Manager module will gradually supplement support for various
connectors, which will increase the size of the manager's binary package.

We need to think about how to manage the build method of the Manager module in the next.

Best,
healchow

On 2022/06/16 01:52:53 Charles Zhang wrote:
> The increased size in binary packages is mainly caused by the introduction
> of a large number of data node connectors.
> The connector of Sort has been disassembled into an independent binary
> package. We could reduce the connector dependency in the Manager and see
> how to organize it.
> 
> Goson zhang <go...@apache.org> 于2022年6月15日周三 15:04写道：
> 
> > Hi all:
> >
> > This release of version 1.2.0 found that the expansion of the binary
> > package is relatively large, exceeding the maximum allowable range of 1G
> > after base64 encoding set by the system, at the same time, it is impossible
> > for us to always apply to increase this maximum limit, that is, each The
> > release package needs to be controlled within 800M, otherwise the version
> > release will be stuck.
> >
> > I would like to invite everyone to take a look at this problem and see how
> > to solve it: whether the released binary package only contains the most
> > basic and core modules and processes, and for non-essential auxiliary
> > modules and branch processes, we set it as source code release, so that
> > Compile when users configure and use on-demand?
> >
> > Looking forward to your opinion, thanks!
> >
> 
> 
> -- 
> Best wishes,
> Charles Zhang
> 

Re: [DISCUSS] How to reduce the size of the binary package?

[Charles Zhang <do...@apache.org>]

The increased size in binary packages is mainly caused by the introduction
of a large number of data node connectors.
The connector of Sort has been disassembled into an independent binary
package. We could reduce the connector dependency in the Manager and see
how to organize it.

Goson zhang <go...@apache.org> 于2022年6月15日周三 15:04写道：

> Hi all:
>
> This release of version 1.2.0 found that the expansion of the binary
> package is relatively large, exceeding the maximum allowable range of 1G
> after base64 encoding set by the system, at the same time, it is impossible
> for us to always apply to increase this maximum limit, that is, each The
> release package needs to be controlled within 800M, otherwise the version
> release will be stuck.
>
> I would like to invite everyone to take a look at this problem and see how
> to solve it: whether the released binary package only contains the most
> basic and core modules and processes, and for non-essential auxiliary
> modules and branch processes, we set it as source code release, so that
> Compile when users configure and use on-demand?
>
> Looking forward to your opinion, thanks!
>


-- 
Best wishes,
Charles Zhang