- update 1: add a FAQ section
- update 2: benchmark chart and feature comparison table
- update 3:
- improve the table with missing features for antigen
- new
zplg times
result
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.
- Create your Glue Dev endpoint (this involves creating a keypair, I just used
ssh-keygen
) - 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 [email protected]
- 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
- 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
#!/usr/bin/env bash | |
# When run, first tries to figure out if the full-refresh flag is set. | |
# Then, runs dbt with or without the flag. | |
# Do not run me in dev mode! | |
full_refresh_needed="$( | |
psql $REDSHIFT_URI -t <<EOF | |
SELECT full_refresh |
;; For supporting more PG types, see https://github.com/remodoy/clj-postgresql | |
(ns pg-test.types | |
(:require [cheshire.core :as json] | |
[clojure.java.jdbc :as jdbc]) | |
(:import [org.postgresql.util PGobject] | |
[java.sql PreparedStatement])) | |
;; Writing | |
(defn- to-pg-json [data json-type] |
MIT License | |
Copyright (c) 2018 Noel Bundick | |
Permission is hereby granted, free of charge, to any person obtaining a copy | |
of this software and associated documentation files (the "Software"), to deal | |
in the Software without restriction, including without limitation the rights | |
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
copies of the Software, and to permit persons to whom the Software is | |
furnished to do so, subject to the following conditions: |
... | |
apply from: './flavors.gradle' | |
... | |
android { | |
buildTypes { | |
productFlavors { | |
project.flavors.each { flavor, config -> | |
"$flavor" { | |
dimension 'scope' | |
if (flavor != 'full') { |
This cheat sheet provides a detailed overview of the exposed lifecycle events and available commands (and entrypoints) of the Serverless framework, that can be hooked by plugins (internal and external ones). The document is structured by the commands invoked by the user.
Lifecycle events are shown as the globally available outer events (all providers) and sub lifecycle events that are provider specific in the called order. Currently only the AWS provider is shown. If you have information about the other provider,
#!groovy | |
import groovy.json.JsonOutput | |
import groovy.json.JsonSlurper | |
def label = "mypod-${UUID.randomUUID().toString()}" | |
podTemplate(label: label, yaml: """ | |
spec: | |
containers: | |
- name: mvn | |
image: maven:3.3.9-jdk-8 |
cd /Library/Preferences
sudo rm com.sophos.sav.plist
cd /Library/Application\ Support/Sophos/cloud/Installer.app/Contents/MacOS/tools/
sudo ./InstallationDeployer —force_remove
(ns background | |
(:require [clojure.tools.logging :as log]) | |
(:import [java.util.concurrent])) | |
(defonce !executor (delay (java.util.concurrent.Executors/newCachedThreadPool))) | |
(defn background | |
"Calls the fn passed in a thread from a thread pool, returning immediately. | |
Unlike future, background does not swallow exceptions." | |
[f] |