Review and cleanup of material for new data pipeline developer onboarding

os-climate / os_c_data_commons

Repository for Data Commons platform architecture overview, as well as developer and user documentation

Apache License 2.0

18 stars 10 forks source link

Review and cleanup of material for new data pipeline developer onboarding #125

Open caldeirav opened 2 years ago

caldeirav commented 2 years ago

This issue will be used to create a task list of items to track against in order to ensure we have the latest documentation / code samples available to support developer onboarding for new contributors.

[ ] Add references to relevant mailing lists and descriptions in Developer documentation
[ ] Review and identify relevant samples of demo notebooks, and ensure they can be executed against the latest platform deployment (using Iceberg and injection via df.to_sql / Trino engine)
[ ] Document conventions for trino schema / tables naming
[ ] Ensure we have an example of metadata structure with proper schema / table naming for metadata (temporary)
[ ] Document conventions for team naming, access in repositories

caldeirav commented 2 years ago

Additional items to document:

[ ] SQL Script execution as part of overall pipeline (e.g. create table structure in SQL before ingestion in Python) - could demonstrate the Trino CLI potentially there
[ ] Developer onboarding should also include steps to have own sandbox - based on developer github id = schema name (requires config update in Trino)
[ ] Add link to an example of pipeline with metadata management

MichaelTiemannOSC commented 2 years ago

@HeatherAck @cdeliaRH

HeatherAck commented 1 year ago

Need to add Open Metadata, DBT pipelines, etc back into architecture doc. Will use global power plant data as sample; updates to be completed by 24-Oct (include Real-Time ingestion capability, Kepler - incl. Data Centers - CO2 emissions of OS-Climate) for COP27 [AWS vs. Google scheduling of ML workloads]

HeatherAck commented 1 year ago

@caldeirav - can you please update https://github.com/os-climate/os_c_data_commons/blob/main/os-c-data-commons-developer-guide.md

MichaelTiemannOSC commented 4 months ago

Related: This dbt documentation (https://docs.getdbt.com/docs/build/packages) exposes a lot of complexity that the Data Mesh pattern should hide: how and where these configuration files go, how they should be populated, and how the pipeline environment just makes this as easy as pie. Right now (not least because of the version skew between the Pachyderm-friendly 1.4.9 and the latest 1.7.x developments over the past two years), there is no clarity at all.