Change Details

As wdqs user I want to query a dataset that is coherent with the state of wikidata. During the past months some issues (T255657, T266211, T264042, T267924, T267175, T268408, T272120) caused the wdqs journal to be out of sync, salvaging current journal seems difficult as detecting all the discrepancies is not possible. Reloading the data from dump is probably the best approach. The approach is to use the `wdqs.data-reload` cookbook to one machine, catchup the lag and then copy over the fresh journal to other machines using the `wdqs.data-transfer` cookbook. AC: - Blazegraph is running with a journal created from a recent RDF dump on all servers (except wdqs1009)

As wdqs user I want to query a dataset that is coherent with the state of wikidata. During the past months some issues (T255657, T266211, T264042, T267924, T267175, T268408, T272120, T273937) caused the wdqs journal to be out of sync, salvaging current journal seems difficult as detecting all the discrepancies is not possible. Reloading the data from dump is probably the best approach. The approach is to use the `wdqs.data-reload` cookbook to one machine, catchup the lag and then copy over the fresh journal to other machines using the `wdqs.data-transfer` cookbook. AC: - Blazegraph is running with a journal created from a recent RDF dump on all servers (except wdqs1009)

As wdqs user I want to query a dataset that is coherent with the state of wikidata. During the past months some issues (T255657, T266211, T264042, T267924, T267175, T268408, T272120, T273937) caused the wdqs journal to be out of sync, salvaging current journal seems difficult as detecting all the discrepancies is not possible. Reloading the data from dump is probably the best approach. The approach is to use the `wdqs.data-reload` cookbook to one machine, catchup the lag and then copy over the fresh journal to other machines using the `wdqs.data-transfer` cookbook. AC: - Blazegraph is running with a journal created from a recent RDF dump on all servers (except wdqs1009)