[
https://issues.apache.org/jira/browse/HDDS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559980#comment-16559980
]
Elek, Marton commented on HDDS-276:
-----------------------------------
I totally agree with you, but in fact this patch doesn't modify any behaviour
about using symbolic links. I just described the current behaviour in the text
of the jira (fortunately, as we got more feedback) but you can see in the patch
that it has not been changed. The symbolic link is there with our without this
patch. This patch would make the build more stable before HDDS-280 is
implemented.
But I am happy to wait until HDDS-280 will be merged (please always do a mvn
clean in hadoop-dist until that).
> Fix symbolic link creation during Ozone dist process
> ----------------------------------------------------
>
> Key: HDDS-276
> URL: https://issues.apache.org/jira/browse/HDDS-276
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Affects Versions: 0.2.1
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Minor
> Fix For: 0.2.1
>
> Attachments: HDDS-276.001.patch
>
>
> Ozone is creating a symlink during the dist process.
> Using the "ozone" directory as a destination name all the docker-based
> acceptance tests and docker-compose files are more simple as they don't need
> to have the version information in the path.
> But to keep the version specific folder name in the tar file we create a
> symbolic link during the tar creation. With the symbolic link and the
> '–dereference' tar argument we can create the tar file which includes a
> versioned directory (ozone-0.2.1) but we can use the a dist directory without
> the version in the name (hadoop-dist/target/ozone).
> Currently this symlink creation has an issue. It couldn't be run twice. You
> need to do a 'mvn clean' before you can create a new dist.
> But fortunately this could be fixed easily by checking if the destination
> symlink exists.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
