[{"_1":2,"_154":-5,"_155":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":11,"_130":-5,"_131":132},"canonicalUrl","https://hub.docker.com/r/nvdk/mu-migrations-service/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","nvdk","reponame","mu-migrations-service","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-09-16T08:14:20.867663Z","description","","is_private","last_updated","2019-12-16T09:52:25.772561Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",905,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# mu-migrations-service\n\nThe mu-migrations-service runs migrations on the database. This\ncurrently includes SPARQL queries (`*.sparql`) and Turtle files (`*.ttl`).\nWe intend more formats to be supported in the future.\n\n## How to\n\nMigrations are specified in files, to be executed in the order of\ntheir filename. The files may reside in subfolders. It is advised\nto use the unix system time as the basis for the filename of your\nmigration, postfixed with a short name of what the migration performs.\n\n### Specifying the migration\n\n#### SPARQL queries\nSpecify the migration in a file, like\n`./config/migrations/20160808225103-statuses.sparql` containing a SPARQL\nquery like:\n\n```\n PREFIX dct: \n PREFIX tac: \n PREFIX ext: \n PREFIX rm: \n PREFIX typedLiterals: \n PREFIX mu: \n PREFIX xsd: \n PREFIX app: \n PREFIX owl: \n PREFIX rdf: \n INSERT DATA {\n GRAPH {\n \n a tac:Status;\n mu:uuid \"wellknown-status-not_started\";\n dct:title \"not started\".\n \n a tac:Status;\n mu:uuid \"wellknown-status-ongoing\";\n dct:title \"ongoing\".\n \n a tac:Status;\n mu:uuid \"wellknown-status-done\";\n dct:title \"done\".\n }\n }\n```\n\n#### Turtle files\nSpecify the migration in a file, like\n`./config/migrations/20160808225103-statuses.ttl` containing triples in Turtle format like:\n\n```\n @prefix dct: .\n @prefix tac: .\n @prefix ext: .\n @prefix rm: .\n @prefix typedLiterals: .\n @prefix mu: .\n @prefix xsd: .\n @prefix app: .\n @prefix owl: .\n @prefix rdf: .\n\n \n a tac:Status;\n mu:uuid \"wellknown-status-not_started\";\n dct:title \"not started\".\n \n a tac:Status;\n mu:uuid \"wellknown-status-ongoing\";\n dct:title \"ongoing\".\n \n a tac:Status;\n mu:uuid \"wellknown-status-done\";\n dct:title \"done\".\n```\n\nBy default, the Turtle files will be imported in the `` graph.\n\n#### Graphs\nThis feature is experimental. In case a `.graph`-file by the same name as a `.ttl`-file is present, the triples in the `.ttl`-file will be imported into the graph specified in its corresponding `.graph`-file, in the same fashion as [OpenLink Virtuoso](http://docs.openlinksw.com/virtuoso/rdfperfloading/#rdfperfloadingutility) does. The content of a `.graph`-file such as `./config/migrations/20160808225103-statuses.graph` may look like this:\n\n```\nhttp://mu.semte.ch/custom-graph\n```\n\n\n### Sharing the migration with the service\n\nRun the migrations service in your pipeline, add the\nmigrations-service to your mu-project and make sure all migrations are\navailable in `/data/migrations`. The migrations may be grouped in subfolders.\n\n```\n migrationsservice:\n image: semtech/mu-migrations-service\n links:\n - db:database\n volumes:\n - ./config/migrations:/data/migrations\n```\n\nThe migration will be ran when the mu-migrations-service starts up,\nand output about the status of the ran migrations will be written to\nthe database for later inspection.\n\n## Configuration\n\nThe migration service supports configuration via environment variables.\n\n### Large datasets and batch size\nTriple stores typically can only handle a certain amount of triples to be ingested per request. The migration service supports batching to split of large datasets in multiple requests. This can be configured with the `BATCH_SIZE` environment variable. If an error occurs during batch ingestion the batch size will be halved and the request retried until `MINIMUM_BATCH_SIZE` is reached. At this point an error will be thrown. \n\nTo make sure a dataset is loaded completely it will first be ingested into a temporary graph, on success the contents will be added to the target graph with a SPARQL Graph query. \n\n\n- `BATCH_SIZE`: amount of triples to insert in one go (default: 12000)\n- `MINIMUM_BATCH_SIZE`: if the batch size drops below this number the service will stop with an error. (default: 100)\n\n### General configuration\nThis microservice is based on the [mu-ruby template](https://github.com/mu-semtech/mu-ruby-template) and supports the environment variables documented in its [README](https://github.com/mu-semtech/mu-ruby-template#configuration).\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",411859762,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",90112,"full_size",374651203,"id",68975247,"images",[97],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},"architecture","amd64","digest","sha256:788d2f61c02fcab1298ae5c3d1ad2b05b45d55c54bfd3dfaba62caf981458f1e","features","last_pulled","2026-09-24T23:56:58.27665455Z","last_pushed","2019-12-16T09:52:26Z","os","linux","os_features","os_version","size","variant","2019-12-16T09:52:25.506783Z","last_updater","last_updater_username","media_type","latest","repository",7704753,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":135,"_142":143,"_131":152,"_153":11},{"_36":136,"_38":137,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":138,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":139,"_75":11,"_76":141,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":140},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_144":60,"_145":-5,"_146":-5,"_147":148},"count","next","previous","results",[149],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":150,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[151],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

nvdk/mu-migrations-service

Tags for nvdk/mu-migrations-service