Activate include-sql-reporting profile so NiFi images ship QueryNiFiReportingTask

Open Beginner friendly
#1,608 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
docker
Domain
build-system

Research direction

Open nifi/Dockerfile and find the nifi-assembly profile configuration. Activate the include-sql-reporting profile, then build a stock SDP NiFi image and verify that nifi-sql-reporting-nar appears under lib/ and QueryNiFiReportingTask is selectable as a Reporting Task.

Written by the indexing model from the issue text.

Description

customer-request

Summary

QueryNiFiReportingTask is missing from the NiFi images we ship. Upstream keeps nifi-sql-reporting-nar behind the non-default nifi-assembly profile include-sql-reporting, and our build does not activate it. The module itself is already compiled by our build, only the assembly inclusion is missing, so the fix is one profile name in nifi/Dockerfile.

Expected

QueryNiFiReportingTask is selectable as a Reporting Task in a NiFi Stacklet built from a stock SDP image.

Actual

The processor type does not exist; lib/ contains no nifi-sql-reporting-nar.

Workaround

Layer the upstream NAR onto the released image; no rebuild of NiFi needed. Example for
NiFi 2.7.2 from SDP 26.3.0:

FROM oci.stackable.tech/sdp/nifi:2.7.2-stackable26.3.0
USER 0
ADD --chown=1000:0 --chmod=660 \
  https://repo1.maven.org/maven2/org/apache/nifi/nifi-sql-reporting-nar/2.7.2/nifi-sql-reporting-nar-2.7.2.nar \
  /stackable/nifi/lib/
USER 1000
Dominant language
Dockerfile
Stars
22
Forks
6
Avg merge
16h 59m
Merged PRs (30d)
30

Contributor guide

No contributing guide indexed for this repository

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 stackabletech/docker-images

All issues in stackabletech/docker-images

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.