Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Task]: Beam Flink pipeline engine page: Flink version, contradicting job id sections and Javadoc leftovers

Open Beginner friendly
  • Is something wrong?
#9,048 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Adalennis is already working on this.

Since Oct 21, 2026.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
86/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
apache, java
Domain
documentation

Research direction

Edit pipeline/pipeline-run-configurations/beam-flink-pipeline-engine.adoc. Read the Flink version and job ID statements against the Beam plugin and the compatibility table in getting-started-with-beam.adoc, then remove the outdated claim and fix the Javadoc leftovers in the options table. Done when the page consistently describes Flink 1.19, job ID behavior, and readable option descriptions.

Written by the indexing model from the issue text.

Description

Documentation P3
What needs to happen?

pipeline/pipeline-run-configurations/beam-flink-pipeline-engine.adoc has a few outdated or contradicting parts:

  • "This runner allows you to run Hop pipelines on Apache Flink version 1.13." The Beam plugin uses beam-runners-flink-1.19, and the compatibility table in pipeline/beam/getting-started-with-beam.adoc says Flink 1.19.x.
  • Two sections disagree about the Flink job id, and each is only right for some Flink masters. "Job id" (added with #8679) says Hop chooses the id before submitting and exposes it with getFlinkJobId() and the flink.job.id execution detail. "Flink job ID" at the end of the page (added with #8716) says "Hop does not show a Flink job ID after a Beam run". In BeamFlinkPipelineEngine, assignFlinkJobId() only fixes a job id when the Flink master is [local] or host:port. With [auto], which is the default, with an empty master, or with [collection], no id is assigned: with [auto] the environment comes from flink run or the Kubernetes operator. The two sections could be merged into one: Hop assigns and reports the id for a [local] or host:port master; with [auto] or [collection] there is no id, and the job can be found by its Beam job name.
  • The options table has Javadoc leftovers: "A value of {@code -1}" (Execution retry delay) and "Reference {@link org.apache.flink.api.common.ExecutionMode}" (Batch execution mode).
Issue Priority

Priority: 3

Issue Component

Component: Documentation

Dominant language
Java
Stars
1.5k
Forks
482
Avg merge
1d 9h
Merged PRs (30d)
312

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/hop

All issues in apache/hop

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.