Shulou(Shulou.com)06/01 Report--

This article introduces the knowledge of "how to develop an issue with apache flink". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Fork code

First of all, we need to have our own github account, we need to fork the flink code to our account, open https://github.com/apache/flink, click the fork button, and then we will see the corresponding project under our own account.

Download to local

Then we can download the flink code of fork to our local area, using the following command:

Cd my_workspace

Git clone https://github.com/zhangjun0x01/flink.git

Add remote warehouse

Next we add a remote repository of apache, mainly to update the code later.

Git remote add apache https://github.com/apache/flink.git

After that, execute the query remote warehouse command git remote-v, and you can see that there are two remote warehouses.

Origin https://github.com/zhangjun0x01/flink.git (fetch)

Origin https://github.com/zhangjun0x01/flink.git (push)

Apache https://github.com/apache/flink.git (fetch)

Apache https://github.com/apache/flink.git (push)

Add a new branch

Next, add a new branch to develop our code. The name of the branch can be chosen freely. For example, in order to make it easier to distinguish and query, we can choose a branch name with the same name as the issue, or a branch name that we can identify according to the function.

I have a branch name related to this function.

Https://github.com/zhangjun0x01/flink/tree/flink-orc-input

Then we can now develop our own code on this branch, and after we have developed the code, we need to check the specification of the code, which is checkstyle

Write test code

Finally, after you have developed the relevant code, you need to add the corresponding test code to the relevant test class, and if you add a new feature, you also need to add the corresponding documentation.

Submit code

After we have finished developing the code, we may have updated the code in the main branch of flink during this time, so we need to update the latest code in order to avoid conflicts. First switch to the main branch

Git checkout master

Git pull apache master

After that, we switch to our branch:

# switch to your own branch

Git checkout flink-orc-input

# add the code just changed. If you are not sure what has been changed, you can take a look at it by git status

Git add your_code

Git commit-m 'comment'

# add the changed code to our branch

Git rebase

# submit the branch to your own warehouse

Git push origin flink-orc-input submitted to the community

After we submit the branch, we can submit the corresponding PR (Pull Request), such as my PR: https://github.com/apache/flink/pull/11434. When submitting, note that the title should be written in the form of [ISSUE] + title, such as [FLINK-16646] [orc] Flink read orc file. In this way, you can automatically associate your pr with issue.

Then we can see the associated PR on the corresponding issue page

Merge PR

After your code is submitted, there will be relevant committer or other people to help you review the code, and of course you can also help others review the code, which is also a way for you to contribute to the community.

If committer agrees with your changes, then he will merge your changes into the master branch, or other corresponding branch.

For example, mine has not only changed the master, but also changed the 1.10 branches, so here are two related PR.

"how to use apache flink to develop an issue" content is introduced here, thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.