Configuration - ABBYY Documentation

FineParser Enterprise is configured with Helm values. Keep your settings in a values file and pass it to every helm install and helm upgrade. Helm checks the file against the chart’s schema and rejects a mistyped value before anything changes.

A starting values file

fineparser-values.yaml

serviceAccount:
  create: false
  name: fineparser

storage:
  inProcess:
    efs:
      fileSystemId: fs-0123456789abcdef0
  output:
    s3:
      bucket: my-fineparser-output
  s3:
    region: us-east-2

scaling:
  maxWorkers: 20

Apply it:

helm upgrade --install fineparser \
  oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/abbyy/fineparser-enterprise/fineparser-enterprise \
  --version <version> --namespace fineparser -f fineparser-values.yaml

Where settings are documented

Area	Page
Worker pool size	Scaling
Recognition defaults	Recognition settings
Volumes	Storage
Upload limits, exposure, retention	Production deployment
Node placement	Node groups and scheduling
Every value and its default	Chart values

Resource names

Resources are named after the release. A release whose name contains fineparser uses it as is, and any other name gets -fineparser appended. A release named fineparser creates fineparser-ingest, fineparser-orchestrator, and fineparser-worker. The examples in these pages use that release in the namespace fineparser.

Applying changes

helm upgrade restarts whatever a change affects. Workers finish the unit they hold before they stop, and the orchestrator resumes its queue. Changing the contents of worker.userProfile does not restart the workers. Restart them yourself:

kubectl -n fineparser rollout restart deployment/fineparser-worker