Skip to content

Conversation

@akohlbre
Copy link
Contributor

Main changes are two new fields added to the schema (also removed overly-aggressive validation).

Checklist for reviewer:

  • Commits should reference a bug or github issue, if relevant (if a bug is referenced, the pull request should include the bug number in the title)
  • Scan the PR and verify that no changes (particularly to .circleci/config.yml) will cause environment variables (particularly credentials) to be exposed in test logs
  • If the PR comes from a fork, trigger the integration CI test by pushing this revision as discussed in the README and review the report posted in the comments.

For glean changes:

  • Update templates/include/glean/CHANGELOG.md

Copy link
Contributor

@acmiyaguchi acmiyaguchi left a comment

Choose a reason for hiding this comment

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

Hi @akohlbre, could you rebase this PR onto the latest version of mozilla-pipeline-schemas. Make sure the main repo is set as a remote (e.g. upstream) and rebase the new patches onto the main branch. It should be something like the following:

git rebase --onto upstream/master HEAD~2

"type": "object"
},
"WebScience.SurveyId": {
"type": "string"
Copy link
Contributor

Choose a reason for hiding this comment

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

It's good practice to document the use of this field using the description property, which will get inserted into the BigQuery schema.

"other"
],
"type": "string"
"type": "integer"
Copy link
Contributor

Choose a reason for hiding this comment

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

This type change won't play well with automated checks in our deployment pipeline. There are two ways to change this. The first is document this field as deprecated in a description and to add a new property (e.g. pageClassification) which would be evolution compatible. The other is to copy the schema with the version bumped.

@akohlbre
Copy link
Contributor Author

Alright --

could you rebase this PR onto the latest version of mozilla-pipeline-schemas

Oops, sorry, I totally forgot to grab updates. Think I got the rebase to work, thanks.

It's good practice to document the use of this field using the description property, which will get inserted into the BigQuery schema.

Added a description for the survey ID field.

This type change won't play well with automated checks in our deployment pipeline. There are two ways to change this. The first is document this field as deprecated in a description and to add a new property (e.g. pageClassification) which would be evolution compatible. The other is to copy the schema with the version bumped.

Added the old field back and labeled it deprecated, and used your suggested name for the replacement.

Thanks!

@acmiyaguchi
Copy link
Contributor

Looks good to me.

@acmiyaguchi acmiyaguchi merged commit 0d2262b into mozilla-services:master Oct 29, 2020
dataops-pipeline-schemas added a commit that referenced this pull request Oct 30, 2020
0d2262b	2020-10-29 12:52:37 -0700	Updates for CITP Pioneer study schema (#634)
jklukas pushed a commit that referenced this pull request Nov 2, 2020
7b15df7	2020-10-30 18:09:50 +0000	add few fields to CITP pioneer study schema (#635)
0d2262b	2020-10-29 12:52:37 -0700	Updates for CITP Pioneer study schema (#634)
dda5d19	2020-10-22 17:37:57 -0700	Add schema for CITP's Pioneer study (#632)
7ad71b3	2020-10-16 14:27:09 -0400	Add fissionEnabled to new uninstall ping (#631)
0f34b31	2020-10-16 14:04:03 -0400	Bug 1461690 - Add Uninstall Telemetry ping schema (#629)
a48ef97	2020-10-13 21:27:37 +0200	Bug 1669208 - Add fissionEnabled field to environment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants