...
Build the project
To build the ozone /hdds subprojectsproject, use the pom.xml from the main repository of hadoop-of ozone.
Code Block | ||||
---|---|---|---|---|
| ||||
git clone https://github.com/apache/hadoop-ozone.git cd hadoop-ozone mvn clean install package -DskipShade -DskipRecon -DskipTests -Pdist -Dtar |
under the -ozone/dist project:
Code Block |
---|
cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT |
The easiest way to start a cluster is using docker and docker compose
Code Block |
---|
cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozone
docker-compose up -d
firefox http://localhost:9876 |
...
We prefer to use github pull requests instead of uploading patches to JIRA. The main contribution workflow is the following:
- Fork apache/hadoop-ozone github repository (first time)
- Create a new Jira in HDDS project (eg. HDDS-1234)
- Create a local branch for your contribution (eg. git checkout \-b HDDS-1234)
- Create your commits and push your branches to your personal fork.
- Create a pull request on github UI (please include the Jira ID in the summary)
- Set the Jira to "Patch Available" state
...
The easiest way to check your contribution is to use the simplified shell scripts under hadoop-ozone/dev-support/checks. The problems will be printed out the standard output:
For example:
Code Block |
---|
hadoop-ozone/dev-support/checks/rat.sh hadoop-ozone/dev-support/checks/checkstyle.sh hadoop-ozone/dev-support/checks/findbugs.sh |
...
It's always good practice (and fast) to test with the related docker-compose based pseudo clusters:
Code Block |
---|
cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozone
./test.sh |
...