codspire / awesome-demo-apps.md

Last active July 20, 2021 22:44

Awesome Demo Apps

codspire / running-flink-locally-on-windows-10.md

Last active March 30, 2025 10:18

Running Flink Locally on Windows 10

I had to make few tweaks to Flink scripts inside $FLINK_HOME/bin folder to make it work locally on my Windows 10 PC.

Thanks to https://stackoverflow.com/questions/62232422/flink-cluster-not-starting-due-to-could-not-find-or-load-main-class-error for the tips.

Let me describe the issues first

Details of my environment

codspire / spark-standalone-pyspark-on-ec2.md

Last active June 9, 2020 16:17

Running Standalone Spark, PySpark on EC2

codspire / getting-started-with-superset-airbnb-data-exploration-platform.md

Last active February 12, 2024 21:41

Getting Started With Superset: Airbnb’s data exploration platform

Update Python and PIP versions on EC2 (Amazon AMI)

At the time of writing, Python v3.5 and PIP v9.0.1 were available on AWS EC2.

sudo yum update -y
sudo yum install python35 -y

codspire / making-zeppelin-work-on-windows.md

Last active December 2, 2021 03:54

Making Zeppelin, Spark, pyspark work on Windows

Zeppelin, Spark, PySpark Setup on Windows (10)

I wish running Zeppelin on windows wasn't as hard as it is. Things go haiwire if you already have Spark installed on your computer. Zeppelin's embedded Spark interpreter does not work nicely with existing Spark and you may need to perform below steps (hacks!) to make it work. I am hoping that these will be fixed in newer Zeppelin versions.

If you try to run Zeppelin after extracting the package, you might encounter "The filename, directory name, or volume label syntax is incorrect."

Google search landed me to https://issues.apache.org/jira/browse/ZEPPELIN-1584, this link was helpful but wasn't enough to get Zeppelin working.

Below is what I had to do to make it work on my Windows 10 computer.

codspire / PythonCLIOnGitBash.md

Last active June 12, 2017 00:56

Make Python CLI interpreter work on GitBash

Add below lines to ~/.bashrc file

alias python="winpty python.exe"

Restart the console or source ~/.bashrc

codspire / Access_EC2_from_behind_the firewall_ that_block_port_22.md

Last active August 4, 2016 15:21

Access EC2 from behind the firewall that block port 22

If your corporate firewall does not allow ssh to EC2 instances due to blocked port 22 you can follow below workaround temporarily to ssh to EC2 instances.

Essentially you need to change the sshd configuration to use port 80 which is typically open in most firewalls to allow http access.

Step 1: Launch a new EC2 instance

Step 2: On "3. Configure Instance" step, expand the "Advanced Details" section and put the below code

Rakesh Nagar codspire