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

Release 89 #753

Merged
merged 9 commits into from
Apr 11, 2018
Merged

Release 89 #753

merged 9 commits into from
Apr 11, 2018

Conversation

BenFradet
Copy link
Contributor

No description provided.

Copy link
Contributor

@chuwy chuwy left a comment

Choose a reason for hiding this comment

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

LGTM!

@BenFradet
Copy link
Contributor Author

BenFradet commented Apr 6, 2018

@alexanderdean this is good to go 👍

We had to manually edit the ddl and jsonpaths since they weren't igluctl-compatible to begin with.

@alexanderdean alexanderdean self-requested a review April 8, 2018 00:27
Copy link
Member

@alexanderdean alexanderdean left a comment

Choose a reason for hiding this comment

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

Not sure why this was approved - unfortunately this release can't go out in this form: the reason is the JSON Paths modifications for the Mandrill 1-0-1s (message_bounced_1.json etc).

If this is released and these JSON Paths deployed, then the Redshift load of Mandrill data will suddenly break for existing Snowplow users.

The solution is to migrate just these JSON Path and Redshift table changes into a new branch, create corresponding ticket(s) and assign to the Blocked Redshift artifacts milestone.

The rest of the PR can go out - if you make the change I will give it a green tick.

@chuwy
Copy link
Contributor

chuwy commented Apr 8, 2018

Hey, @alexanderdean, we considered the fact about breaking JSONPaths (sorry, had to make conversation public). The reason why I approved this is because as far as I understand the problem - there's simply nothing to break: all data for com.mandril goes to enriched/bad because of this omnipresent subaccount property, so users either will have to migrate their tables or continue without Mandrill data.

@alexanderdean
Copy link
Member

Thanks @chuwy - that makes sense. @yalisassoon is that your understanding of the current Mandrill situation - that the webhook is not working for customers in its current form?

@BenFradet
Copy link
Contributor Author

BenFradet commented Apr 10, 2018

Removed ddl and jsonpaths which have been extracted into #763

CHANGELOG Outdated
@@ -1,3 +1,14 @@
Release 89 (2018-04-06)
Copy link
Member

Choose a reason for hiding this comment

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

Date needs changing to today

"properties": {
"vendor": {
"type": "string",
"maxLength": 256
Copy link
Member

Choose a reason for hiding this comment

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

Whitespace is all messed up in this file (see 6 more instances below).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

mix-indent ftw...

@BenFradet
Copy link
Contributor Author

@alexanderdean fixed 👍

Copy link
Member

@alexanderdean alexanderdean left a comment

Choose a reason for hiding this comment

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

Awesome thanks, proceeding with the release...

@alexanderdean alexanderdean merged commit 2b34a0d into master Apr 11, 2018
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