[
https://issues.apache.org/jira/browse/HIVE-29591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated HIVE-29591:
--------------------------------
Description:
Given earlier thread:
https://lists.apache.org/thread/3z6f0srnts3n2m36yh5573lhyd5khyp2
The original suggestion was to move all hive-test-kube + hive-toolbox +
hive-dev-box to separate repositories. Looking at the code of these
repositories, they still contain amazing tools for hive development, but now I
consider it a heavyweight approach, given that Hive already has its Docker
image (for testing and maybe production), so what we really need is a precommit
specific image with a few requirements:
1. lightweight (alpine, java, minimal tools installed that can run precommit
unit tests)
2. Dockerfile to be stored in hive repository
3. Create a tag in the hive namespace: https://hub.docker.com/r/apache/hive/tags
4. Automatically push it when Dockerfile is changed (via Github actions)
5. Delete the leftover https://github.com/apache/hive-dev-box to avoid further
confusion
Similar migration has already been done downstream, turning a 3-4GB image to
7-800MB.
I believe that nowadays, a working minimal image from scratch is almost as easy
to achieve as rethinking the whole hive-dev-box / hive-toolbox.
was:
Given earlier thread:
https://lists.apache.org/thread/3z6f0srnts3n2m36yh5573lhyd5khyp2
The original suggestion was to move all hive-test-kube + hive-toolbox +
hive-dev-box to separate repositories. Looking at the code of these
repositories, they still contain amazing tools for hive development, but now I
consider it a heavyweight approach, given that Hive already has its Docker
image (for testing and maybe production), so what we really need is a precommit
specific image with a few requirements:
1. lightweight (alpine, java, minimal tools installed that can run precommit
unit tests)
2. Dockerfile to be stored in hive repository
3. Create a tag in the hive namespace: https://hub.docker.com/r/apache/hive/tags
4. Automatically push it when Dockerfile is changed (via Github actions)
Similar migration has already been done downstream, turning a 3-4GB image to
7-800MB.
I believe that nowadays, a working minimal image from scratch is almost as easy
to achieve as rethinking the whole hive-dev-box / hive-toolbox.
> Create Hive precommit image and move Dockerfile into the hive repository
> ------------------------------------------------------------------------
>
> Key: HIVE-29591
> URL: https://issues.apache.org/jira/browse/HIVE-29591
> Project: Hive
> Issue Type: Sub-task
> Components: Testing Infrastructure
> Reporter: László Bodor
> Priority: Major
>
> Given earlier thread:
> https://lists.apache.org/thread/3z6f0srnts3n2m36yh5573lhyd5khyp2
> The original suggestion was to move all hive-test-kube + hive-toolbox +
> hive-dev-box to separate repositories. Looking at the code of these
> repositories, they still contain amazing tools for hive development, but now
> I consider it a heavyweight approach, given that Hive already has its Docker
> image (for testing and maybe production), so what we really need is a
> precommit specific image with a few requirements:
> 1. lightweight (alpine, java, minimal tools installed that can run precommit
> unit tests)
> 2. Dockerfile to be stored in hive repository
> 3. Create a tag in the hive namespace:
> https://hub.docker.com/r/apache/hive/tags
> 4. Automatically push it when Dockerfile is changed (via Github actions)
> 5. Delete the leftover https://github.com/apache/hive-dev-box to avoid
> further confusion
> Similar migration has already been done downstream, turning a 3-4GB image to
> 7-800MB.
> I believe that nowadays, a working minimal image from scratch is almost as
> easy to achieve as rethinking the whole hive-dev-box / hive-toolbox.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
