gwhitelaw

validateUuid = (text) -> (text || "").match(/[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}/)

validateUuid(null) # returns null
validateUuid("") # returns null
validateUuid("not-a-valid-uuid") # returns null
validateUuid("73963155-27db-48ad-abee-7afa2dd14af1") # returns regex match array

gwhitelaw

require 'sugar'
{ compact } = require 'underscore'

parseFriendlyDate = (friendlyDate) ->
  date = new Date().getTime()
  dateOffset = date
  dateSections = compact((friendlyDate.trim()).split(/(\d+\s\w+)\s/))
  dateEnding = dateSections.splice(-1)
  dateSections.forEach((section) -> dateOffset -= (date - Date.create("#{section} #{dateEnding}").getTime()))
  new Date(dateOffset)

gwhitelaw

This is how I quickly got an Apache Zepplin notebook running against the AWS Glue Dev endpoint. None of the guides out there seemed concise, and I found some custom Docker containers doing what you can do easily. This gives you the power - it sets up port forwarding & runs the official Docker image.

1. Create your Glue Dev endpoint (this involves creating a keypair, I just used ssh-keygen)
2. Once READY, select it and copy the "SSH tunnel to remote interpreter"

• eg: ssh -i <private-key.pem> -vnNT -L :9007:169.254.76.1:9007 glue@..compute.amazonaws.com

3. Connect to the endpoint in a terminal session, modifying the above to match: ssh -i ~/.ssh/glue-dev -vnNT -L :9007:*127.0.0.1*:9007 glue@<ec2-endpoint>.<region>.compute.amazonaws.com
4. Run the Apache Zepplin Docker container `docker run -p 8080:8080 --rm -v $PWD/logs:/logs -v $PWD/notebook:/notebook -e ZEPPELIN_LOG_DIR='/l