Russel,
I faced a similar issue recently and reported on slack channel.
I am working on a fix and hopefully submit a PR in the coming hours.
Chris was resourceful pointing out the cause.
Thanks,
Mathew
On Thu, 8 Jun 2023 at 15:58, Russell Bateman wrote:
> Thanks, Chris.
>
> In fact, I merely
Thanks, Chris.
In fact, I merely hand-corrected the instances of the version in
/Dockerfile/ and in /DockerImage.txt/, then ran /DockerBuild.sh/. I got
exactly the image I wanted. It looked like a potential if irrelevant bug
and I thought I'd report it.
Best,
Russ
On 6/7/23 19:17, Chris
The DockerImage.txt file isn't always updated in the repo, a bit like the
README for Docker Hub - it probably should be, but is often forgotten (same
for all of the convenience images built after a release). Indeed, this is
currently set to 1.15.1 on `main`, but the images in Docker Hub since then
I'm re-rolling in order to update the Java inside to 11 in order to
permit using the new Java HTTP client. This seems to work well; I fixed
the bug locally.
Maybe too old to be important, but NiFi 1.14.0 is a quantum step up for
several aspects of processor writing requiring refactoring. So,
> Because I have custom processors that cannot be rebuilt (source-code
gone)
IntelliJ can probably give you a close version of the source code if you
expand the JAR and drag the class files for your custom code into the IDE.
On Wed, Jun 7, 2023 at 5:32 PM Russell Bateman
wrote:
> I downloaded
I downloaded sources to 1.13.2 in order to hand-spin my own container
image. When I got down to
/nifi-1.13.2/nifi-docker/dockerhub/Dockerfile/, I found:
...
ARG NIFI_VERSION=1.13.1
...
and the version is also wrong in /DockerImage.txt/ which
/DockerBuild.sh/ consumes.
Indeed, the
