You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the use of the message-queue-mapper to automatically integrate into the RabbitMQ-based SFM setup is rather manual. This could be improved by providing dockerfiles such that the docker-compose.yml file of sfm-docker can be extended to automatically start/stop our Knowledge Graph Generation component.
This may involve the creation of one Dockerfile which based on some environment variable or parameter can be instantiated several times. For example one time with the config-rabbitmq.json to handle warc_created messages, one time with config-besocial.json to handle rml_mapping messages or one time with another config to handle the HDT-compression.
The text was updated successfully, but these errors were encountered:
Currently the use of the message-queue-mapper to automatically integrate into the RabbitMQ-based SFM setup is rather manual. This could be improved by providing dockerfiles such that the
docker-compose.yml
file of sfm-docker can be extended to automatically start/stop our Knowledge Graph Generation component.This may involve the creation of one Dockerfile which based on some environment variable or parameter can be instantiated several times. For example one time with the
config-rabbitmq.json
to handlewarc_created
messages, one time withconfig-besocial.json
to handlerml_mapping
messages or one time with another config to handle the HDT-compression.The text was updated successfully, but these errors were encountered: