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

Scala Common Enrich: write out event_vendor/name/format/version fields #1800

Closed
alexanderdean opened this issue Jun 23, 2015 · 2 comments
Closed
Assignees

Comments

@alexanderdean
Copy link
Member

I think the most futureproof way of doing this would be to have a structure in atomic.events like this:

event       | event_vendor                   | event_name  | event_format | event_version
-----------------------------------------------------------------------------------------
unstruct    | com.snowplowanalytics.snowplow | ad_click    | jsonschema   | 1-0-0
page_view   | com.snowplowanalytics.snowplow | page_view   | jsonschema   | 1-0-0
struct      | com.google.analytics           | event       | jsonschema   | 1-0-0
transaction | com.snowplowanalytics.snowplow | transaction | jsonschema   | 1-0-0

The rationale here is:

  • Anybody using the existing event column can continue to do so
  • Anybody using unstructured events can use the new event_vendor/name/format/version columns, which map directly onto the Iglu URI components
  • As we convert our legacy events (e.g. GA-style 5-field structured events) into JSONs, then the corresponding event_vendor/name/format/version columns are futureproofed - their values won't change

Depends on #1637

@alexanderdean alexanderdean self-assigned this Jun 23, 2015
@alexanderdean alexanderdean added this to the Release 69 XXX milestone Jun 23, 2015
@alexanderdean
Copy link
Member Author

@danisola will work on this

@pvdb
Copy link

pvdb commented Jun 24, 2015

:g/will/s/will/might/g

😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants