ThrawnCA
ThrawnCA
XLoader doesn't require any particular Redis version. Whatever ckanext-harvest chooses to install ought to work.
Sample file displaying this error: [28082023c.csv](https://github.com/ckan/ckanext-xloader/files/12470449/28082023c.csv)
A smaller sample file: [unclaimedmoneyopen-1.part.csv](https://github.com/ckan/ckanext-xloader/files/13066302/unclaimedmoneyopen-1.part.csv)
HA XLoader is certainly possible. However, there is an increased risk of slowdowns and database transaction deadlocks when datasets have a high number of resources and different XLoader instances compete...
@JVickery-TBS Merge conflict needs to be resolved.
Another issue with asynchronous processing is that the logic in `plugin.py` to check whether XLoader can proceed will always see the _previous_ `validation_status`.
> So I don't know the logic to determine if the caller is from the View or from the Validation Job yet. (maybe I can see if we are currently...
@JVickery-TBS Have you looked at the interaction between the archiver and QA plugins? Archiver defines an `IPipe` interface to receive callbacks, QA implements that interface, so when Archiver has finished...
@OriHoch This looks like it could proceed, but needs the merge conflict resolved.
You should be able to pass a `resource_id` to the `xloader_submit` API to run the XLoader for that resource.