I am reaching out to inquire about the purpose of the internal database in DataPusher (default location: /tmp/job_store.db). I am unclear about its necessity, particularly in the context of using CKAN's "ckan datapusher submit" command. When this command is executed, it appears that the jobs for submitting to the datastore are stored in CKAN's own database. Additionally, if the same resource is submitted again, the process seems to be omitted. Given that CKAN already has a job database, I am curious as to why there is a need for a separate database within DataPusher. Could you please explain the role and necessity of this database in DataPusher's functionality?
Hello DataPusher team,
I am reaching out to inquire about the purpose of the internal database in DataPusher (default location: /tmp/job_store.db). I am unclear about its necessity, particularly in the context of using CKAN's "ckan datapusher submit" command. When this command is executed, it appears that the jobs for submitting to the datastore are stored in CKAN's own database. Additionally, if the same resource is submitted again, the process seems to be omitted. Given that CKAN already has a job database, I am curious as to why there is a need for a separate database within DataPusher. Could you please explain the role and necessity of this database in DataPusher's functionality?
Thank you for your time and assistance.