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

📜 add history to JSON objects #53

Open
jadudm opened this issue Dec 28, 2024 · 0 comments
Open

📜 add history to JSON objects #53

jadudm opened this issue Dec 28, 2024 · 0 comments

Comments

@jadudm
Copy link
Contributor

jadudm commented Dec 28, 2024

As objects pass through the queued pipeline, we should build up a list of processes that touched the object.

For example, when fetch grabs a page, we create both a .raw and .json object in S3. The JSON object should have a field, history (or similar) that contains a list of values. To start, it would contain fetch. After we walk the page, we should have fetch,walk. After extraction, fetch,walk,extract, and so on.

validate can then tell whether or not objects have gone through the entire pipeline.

Part of this, however, involves us knowing when a process is "done."

for thought

do we want this with the object, or in a work database? Having it decoupled could be more trouble, but it would give us the ability to analyze more quickly/easily than retrieving all of the objects to inspect them.

@jadudm jadudm added this to jemison Dec 28, 2024
@jadudm jadudm converted this from a draft issue Dec 28, 2024
@jadudm jadudm changed the title add history to JSON objects 📜 add history to JSON objects Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: triage
Development

No branches or pull requests

1 participant