Document Library Common Components

Common utilities and components used in the document library including:

• Custom BSON codecs for converting Scala objects to BSON structures - io.mdcatapult.doclib.codec
• Custom Json converters for converting json to Scala types - io.mdcatapult.doclib.json
• Common message structures - io.mdcatapult.doclib.messages
• Common object models - io.mdcatapult.doclib.models
• DocLibFlags - Object to allow easy checking and manipulation of doclib flags ie started, ended, errored - io.mdcatapult.doclib.models.DocLibFlag
• TargetPath - Trait to include tooling for the generation of doclib target paths for a source document - io.mdcatapult.doclib.path.TargetPath
• PrefetchUtils - Trait with various convenience methods used by the Prefetch process for a DocLibDoc - io.mdcatapult.doclib.util.PrefetchUtils.

Creating a new Consumer

The basic pattern is that the Consumer creates the queues and connections to Mongo. Then it creates a handler for the messages. The Consumer should extend the AbstractConsumer class.

Abstract Handler

Handlers within a consumer should extend the AbstractHandler class with the appropriate typed parameters that represent the type of message Envelope received and the HandlerResult that is returned. The handle method accepts a CommittableReadResult which contains the rabbit message that extends the Envelope trait and returns a tuple which contains the original message and a HandlerResult. The handle method represents the "business logic" that a Queue is subscribed with. The postHandleProcess receives messages that extend the HandlerResult trait, ensuring a message's associated DoclibDoc has the correct post processing operations applied. This includes logging, optionally sending a message to the supervisor, and writing appropriate flags to the DoclibDoc.

Fetch dependencies from internal package repository

Make sure your ~/.sbt/.credentials file is set up correctly.

realm=GitLab Packages Registry
host=gitlab.com
user=Private-Token
password=your-private-gitlab-token

Set the REGISTRY_HOST_PROJECT_ID to point to the gitlab internal package repo. ie

export REGISTRY_HOST_PROJECT_ID=12345678

Ask SE for the actual ID you should use. You may need to set it in any env within your run config in your IDE.

If updating sbt packages, compiling or running tests inside your IDE you will need to add the env var to the sbt setup within it. For example, for intellij go to the settings and add the env var in the Environment Variables field via Build, Execution, Deployment > Build Tools > SBT

Testing

To run tests, do

sbt clean test

For integration tests, do

docker-compose up -d
sbt clean it:test

To do all tests and get a coverage report, do

docker-compose up -d
sbt clean coverage test it:test coverageReport

Dependency Scanning

https://github.com/albuch/sbt-dependency-check

The sbt-dependency-check plugin can be used to create a HTML report under target/scala-x.x/dependency-check-report.html

sbt dependencyCheck

Dependency Issues

Tika > 1.28.5 causes compilation issues - Note this no longer seems an issue since moving to 2.9.2

[error] While parsing annotations in /Users/ian.dunlop/.ivy2/cache/org.mongodb/mongodb-driver-core/jars/mongodb-driver-core-4.4.1.jar(com/mongodb/lang/Nullable.class), could not find MAYBE in enum <none>.
[error] This is likely due to an implementation restriction: an annotation argument cannot refer to a member of the annotated class (scala/bug#7014).

Prometheus > 0.9.0 causes integration test failures in ConsumerHandlerSpec.

License

This project is licensed under the terms of the Apache 2 license, which can be found in the repository as LICENSE.txt