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

remote b-metadata sync issue #80

Open
bnlawrence opened this issue Jul 13, 2022 · 2 comments
Open

remote b-metadata sync issue #80

bnlawrence opened this issue Jul 13, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@bnlawrence
Copy link
Collaborator

The use case is

User parses remote directory, returns b-metadata (and other stuff locally), then subsequently wants to update, how to make that efficient?

Option A is generate json remotely and update local database, but that means the entire remote needs to be parsed for any update.

Option B is keep a remote sqlite db and update that only as necessary, and pull back changes, so need to keep two dbs in sync.
See this stack overflow for some discussion.

@bnlawrence
Copy link
Collaborator Author

(That effectively requires a full installation of cfstore remotely, which may not be that good, but we need a cf install anyway to get b-metadata, or at the very least an NC install with a very cut-down script to pull attributes.)

@bnlawrence
Copy link
Collaborator Author

This is really a CF aggregation problem. We neeed to make sure there is a ticket in CF-python linked to this.

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

No branches or pull requests

2 participants