Demonstrate how to tie a database into the upstream data pipeline

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

Research direction

No files, tests, or entry points are named. Start by reviewing the repository's existing GNU Make targets and data-pipeline examples, then determine how to populate a database, write a file containing the latest relevant last_updated_date values, and declare that file as a data dependency while accessing the database over the network. Done means the demonstration runs end to end without treating the database file itself as the dependency.

Written by the indexing model from the issue text.

Description

enhancement
  1. Add a build target that populates a database with some random data
  2. Add a build target that writes to a file to match the most current last_updated_date for any database tables we're interested in.
  3. Add this file as a data dependency

... or something like that. Could trivially add the db file as a dependency, but let's pretend we only have network access to the database to prove the concept.

Dominant language
HTML
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dmarx/make_for_datascience

All issues in dmarx/make_for_datascience

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.