You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2026/05/27 18:35:00 UTC
[jira] [Updated] (KUDU-3780) Add an option to build libkudu_client C++ library and its 3rd-party dependencies only
[ https://issues.apache.org/jira/browse/KUDU-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin updated KUDU-3780:
--------------------------------
Description:
At the time of writing, the regular build flow assumes building all the 3rd-party components to produce libkudu_client.so bits. For projects like Impala, libkudu_client.so is the only required artifact, and they need building it with a custom/specific toolchain, so sharing pre-built 3rd-party bits built a standard way it's done in Kudu isn't a viable option (i.e. Impala needs Kudu's 3rd-party components built with Impala-specific toolchain).
To reduce build times for libkudu_client as an artifact needed by Impala, it makes sense to provide a way building only 3rd-party components needed for libkudu_client (at least, for DEBUG and RELEASE build configurations). That might be implemented as a change in build scripts' behavior when a particular environment variable specified (e.g., {{KUDU_CLIENT_ONLY}}).
was:
At the time of writing, it's necessary to build all the 3rd-party components to produce libkudu_client.so bits. For projects like Impala, libkudu_client.so is the only required artifact, and they need building it with a custom/specific toolchain, so sharing pre-built 3rd-party bits built a standard way it's done in Kudu isn't a viable option (i.e. Impala needs Kudu's 3rd-party components built with Impala-specific toolchain).
To reduce build times for libkudu_client as an artifact needed by Impala, it makes sense to provide a way building only 3rd-party components needed for libkudu_client (at least, for DEBUG and RELEASE build configurations). That might be implemented as a change in build scripts' behavior when a particular environment variable specified (e.g., {{KUDU_CLIENT_ONLY}}).
> Add an option to build libkudu_client C++ library and its 3rd-party dependencies only
> -------------------------------------------------------------------------------------
>
> Key: KUDU-3780
> URL: https://issues.apache.org/jira/browse/KUDU-3780
> Project: Kudu
> Issue Type: Improvement
> Components: build
> Reporter: Alexey Serbin
> Priority: Major
>
> At the time of writing, the regular build flow assumes building all the 3rd-party components to produce libkudu_client.so bits. For projects like Impala, libkudu_client.so is the only required artifact, and they need building it with a custom/specific toolchain, so sharing pre-built 3rd-party bits built a standard way it's done in Kudu isn't a viable option (i.e. Impala needs Kudu's 3rd-party components built with Impala-specific toolchain).
> To reduce build times for libkudu_client as an artifact needed by Impala, it makes sense to provide a way building only 3rd-party components needed for libkudu_client (at least, for DEBUG and RELEASE build configurations). That might be implemented as a change in build scripts' behavior when a particular environment variable specified (e.g., {{KUDU_CLIENT_ONLY}}).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)