Skip to content

Conversation

tswast
Copy link
Contributor

@tswast tswast commented May 1, 2018

These samples are to be included in the Cloud Composer docs at https://cloud.google.com/composer/docs/

Note that these samples have already been reviewed via Gerrit.

janczak10 and others added 9 commits May 1, 2018 08:44
Add first airflow example DAG. This DAG demonstrates how to call
Dataproc from airflow.

Change-Id: I2f0464da37f11085dfc927f4f4d96d6a99634aad
Also, adjusts indentation to 4 spaces so that `flake8` passes.

Change-Id: Id3e1fbfa5bd41a4e11e0cd7991b058b063241e6b
Change-Id: Ib0bbacd91529fac272e2da0c72abca5db9b4fad8
The GCP Airflow operators only work on Python 2.7 (a constraint
they inherited from Apache Beam), so I've made some changes to nox.py to
exclude them from the Python 3 builds.

Change-Id: Ia10971dd5a7b14279b236041836e317e79693258
Since there are not Cloud client libraries for Composer yet, this sample
uses the REST API directly via the google-auth and requests libraries.

Sample to be used at https://cloud.google.com/composer/docs/how-to/using/managing-dags

Also, enables Kokoro testing for Composer samples. (Uses Python 2.7
since Cloud Composer is currently restricted to Python 2.7)

Change-Id: Icb37e079992c88eedc06cdcc3d72db5106d10ef5
Add a sample Airflow DAG that will create BigQuery dataset, run
BigQuery, export results to Cloud Storage, notify user by email when
results are ready, and clean up the dataset.

Change-Id: Ia8242df29223d910b2d269a9bb93720b35470b7a
Requires master copy of Airflow for `bigquery_get_data` operartor.

Change-Id: I73cd2cfb2458b67bed1a77e65966d5018e8bb45d
Change-Id: I2856bc6cb866bd6f7abbac8de3323797a83c9857
Change-Id: I657e052fa851daa7c72045762090a2e27dd406d3
@tswast tswast requested a review from SurferJeffAtGoogle May 1, 2018 15:51
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label May 1, 2018
@tswast tswast requested review from michaelawyu and removed request for SurferJeffAtGoogle May 1, 2018 15:53
@tswast
Copy link
Contributor Author

tswast commented May 1, 2018

Question: Are we still using Travis? I see the Kokoro configs and thought we had migrated.

The default machine type was n1-standard-4, which exceeds trial
project quota. This CL changes the machine type to n1-standard-1
since a more powerful machine is not necessary for quickstart
sample data.

Change-Id: I46af68c29145f7a7ce303afdad4708bda7d9e6dd
@michaelawyu
Copy link
Contributor

Hi Tim! I think Travis is still used.

Copy link
Contributor

@michaelawyu michaelawyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍Will merge after the tests pass :)

Change-Id: I9c27c75cbea8c5ed4edf859d26980e24ea270eea
@tswast
Copy link
Contributor Author

tswast commented May 1, 2018

A composer environment is currently being created for the test project, and I've updated the Travis environment secrets file to reflect it. 🤞

@tswast tswast merged commit a4de1a3 into master May 1, 2018
@tswast tswast deleted the composer branch May 1, 2018 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants