ckan / ckan/datapusher

Clarification on the Role of Internal Database in DataPusher

Open
#262 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
82
Forks
157
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.