[github-actions]

Automated version bump of the Apache Tika Docker image.

Old version: 3.3.0.0-full
New version: 3.3.1.0-full
Chart version: 3.3.1

View available tags on Docker Hub

[jocelynthode]

@lewismc Hey, would it be possible to cut a new helm chart release to integrate all these changes please as the release as a helm chart only seem to occur when a release and not just a tag is made.

[lewismc]

Hi @jocelynthode sorry for late response. The new chart was published. Thanks for any feedback. Are you able to use it OK?

[jocelynthode]

@lewismc unfortunately It still looks like it's not working. I was first trying to use the one published by apache on Artifacthub https://artifacthub.io/packages/helm/apache-tika/tika but it seems this part isn't maintained anymore (or rely on the github tag releases).

When trying to use it as per the readme here through an OCI chart like so:

dependencies:
  - name: tika
    version: 3.3.1
    repository: oci://apache.jfrog.io/tika-helm/tika

I get:

Downloading tika from repo oci://apache.jfrog.io/tika-helm/tika
Save error occurred:  could not download oci://apache.jfrog.io/tika-helm/tika/tika: failed to perform "FetchReference" on source: apache.jfrog.io/tika-helm/tika/tika:3.3.1: not found
Error: could not download oci://apache.jfrog.io/tika-helm/tika/tika: failed to perform "FetchReference" on source: apache.jfrog.io/tika-helm/tika/tika:3.3.1: not found

[lewismc]

Hi @jocelynthode thanks and I am so sorry for the late response. Thanks for the concrete error; that .../tika/tika path is Helm appending the dependency name to repository.

Use the registry root, not the chart URL:

dependencies:
  - name: tika
    version: "4.0.0"
    repository: "oci://apache.jfrog.io/tika-helm"

Then helm dependency update. Direct install:
helm install tika oci://apache.jfrog.io/tika-helm/tika --version 4.0.0
That is the current official chart (Tika Docker 4.0.0-1-full). I pulled that OCI artifact and smoke-tested detect / metadata / text extract against it successfully.

Chart 3.3.1 was tagged in git but not published to OCI (tag push with GITHUB_TOKEN does not start the release workflow). Sorry for the gap. Artifact Hub’s old HTTP repo (https://apache.jfrog.io/artifactory/tika) is deprecated; OCI is the install path.

This is documented under Chart.yaml dependencies in the README. Happy to help if 4.0.0 still misbehaves. Please let me know and again, I apologize about that.

[jocelynthode]

Hey, thanks for the feedback ! I admit I'm still a bit new to using OCI charts in helm, thanks for the explanation now I'll remember Helm appends the chart name. Thanks for updating the doc as well!

I'll get around to testing this probably next week

[lewismc]

@jocelynthode thank you

[jocelynthode]

@lewismc I tested it and it works, but unfortunately I need to stay on tika v3 for now as we use it with SolR for moodle search indexing with PDF and I don't think it's all ready for this big major migration.

Would it be possible to fix the OCI gap in the meantime ?

[lewismc]

Hi @jocelynthode do you mean, making OCI containers available for 3.X?
Which version do you want and I can make the release. Thanks.

[jocelynthode]

The latest 3.x (I believe 3.3.1) would be great to have for the oci container!

Thanks for your efforts!

[jocelynthode]

3.3.2 is actually the latest sorry about that

[lewismc]

I'll publish the OCI for 3.3.2 tomorrow. Thanks