IntroductionJW Player receives an average of 45,000 log entries per second (or "pings") into a lambda architecture data pipeline. This equates to a daily data set that contains between 3 and 4 billion rows. To improve query performance and save storage costs the Data team at JW Player has started an initiative to re-define the data domain where pings are stored as sessions in a columnar format.
We’re pleased to announce the launch of our new support site! support.jwplayer.com features lots of cool new tools to assist with your questions and troubleshooting. Let’s take a quick tour and go over some of the more interesting changes:
How to do itAll you need to do here is set up a normal JW Player embed like we always do, and use our API, and onComplete(), to tell the player to display the call to action at the end. This demo shows a movie preview with a CTA to watch the entire film when the preview is over:
As long as our player has been around, we have received requests from our customers asking for the ability to age gate their users. This feature presents users with an age verification prompt requiring them to enter their birthday. If the users are older than the required age, they are granted access to watch the video (i.e. video playback starts). If they are younger than the required age, they are taken to a different page and are unable to view the video. It is a simple, but useful feature to restrict underage viewers from mature content.
If you are looking to encode only a couple of videos, you could consider converting all videos manually, but if you have a larger library, it is important to replace any manual steps with a good encoding pipeline. Amazon’s Elastic transcoder has all the important components you need to create a transcoding pipeline using Amazon’s API’s.