we changed it already; I could move it there.
@BenFradet I just read your article https://discourse.snowplowanalytics.com/t/a-new-bad-row-format/2558 -> I am not sure if it's to late but I'd like to have one more row in
I have schemas which are fired from Front-End and Back-End respectively, or more generally - from different emitters, for me it would be super useful to have also the app_id in there;
With this I could finally have a reasonable escalation path to approach teams in my company.
payloadfield after the tracker protocol validation stage such that it won't be an http payload but a tracker payload
:wave: Question: Just curious if you considered it moving forward: I am using events with context's often, so the main event gives the
I am just curious if you consider to denormalize the event / contexts sent somewhere into the event?
Reason: Sometimes I am not sure which context was set and would like to have a programmatic way of finding that out in Redshift;
Could also be that I am missing one piece / best practise here ...
@hejfelix, @amirhmd sorry for delay guys.
Felix, you can have a look at CLI arguments in EMR console. EER just sumbits the steps and moves data around. But please bear in mind that we’re deprecating a batch pipeline along with Spark enrich and EER
Amir, it depends on which subproject you’re interested in. There’s no way to build whole snowplow/snowplow repo, but if you go into a specific subfolder - they’re almost all typical Scala projects with SBT configuration
remote: Permission to snowplow/snowplow.git denied to piyushknoldus. fatal: unable to access 'https://github.com/snowplow/snowplow.git/': The requested URL returned an error: 403
Hi all, we don't actively monitor this gitter room any more - our new primary communication channel is our Discourse: https://discourse.snowplowanalytics.com/
As for pushing fixes, you need to fork the repository in to your own account first, make the changes in your own version of the
snowplow repository and then you can open a PR from your version of
snowplow/snowplow. This applies for all repositories on Github no matter the original author :-)