Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification on the Role of Internal Database in DataPusher #262

Open
MasaGon opened this issue Dec 4, 2023 · 0 comments
Open

Clarification on the Role of Internal Database in DataPusher #262

MasaGon opened this issue Dec 4, 2023 · 0 comments

Comments

@MasaGon
Copy link

MasaGon commented Dec 4, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant