Skip to content

Instantly share code, notes, and snippets.

View praveev's full-sized avatar

Praveen praveev

View GitHub Profile
@praveev
praveev / netlify.toml
Created May 5, 2020 07:28
netlify toml
# Settings in the [build] context are global and are applied to all contexts
# unless otherwise overridden by more specific contexts.
[build]
# Directory to change to before starting a build.
# This is where we will look for package.json/.nvmrc/etc.
base = ""
# Directory (relative to root of your repo) that contains the deploy-ready
# HTML files and assets generated by the build. If a base directory has
# been specified, include it in the publish directory path.
@praveev
praveev / pull request template.md
Last active May 16, 2020 20:31
pull-request template

Description

Please include a summary of the change and why this is needed.

  • [Design Document](paste URL here or delete)
  • [Jira Ticket](paste URL here or delete)

Type of change

Please delete options that are not relevant.

***************
Total duration: 352693ns
DBB write time -> 86.0ns
DBB select time -> 737.0ns
DBB total c++ time -> 1032.0ns
***************
Total duration: 27173ns
Unsafe write time -> 79.0ns
Unsafe select time -> 738.0ns
Unsafe total c++ time -> 932.0ns
t1 = DistCpSensor(
task_id='sensor',
lookback=2,
distcp_dao=distcp_dao,
source_conn=source_conn,
parent_paths=['/tmp/testAirflowDistCp'],
timeout=12*60*60,
dag=dag)
def run_distcp_on_each(*args, **kwargs):
Traceback (most recent call last):
File "/home/y/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
response = self.full_dispatch_request()
File "/home/y/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/y/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/y/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
rv = self.dispatch_request()
File "/home/y/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
{
"spec" : {
"dataSchema" : {
"dataSource" : "website",
"parser" : {
"type" : "string",
"parseSpec" : {
"format" : "csv",
"timestampSpec" : {
"column" : "timestamp",
{
"type" : "index_hadoop",
"id" : "index_hadoop_wikipedia_partition_2016-03-07T02:43:12.977Z",
"spec" : {
"dataSchema" : {
"dataSource" : "wikipedia_partition",
"parser" : {
"type" : "string",
"parseSpec" : {
"format" : "json",
io.druid.indexing.worker.executor.ExecutorLifecycle - Running with task: {
"type" : "index_hadoop",
"id" : "index_hadoop_wikipedia_partition_2016-03-07T02:43:12.977Z",
"spec" : {
"dataSchema" : {
"dataSource" : "wikipedia_partition",
"parser" : {
"type" : "string",
"parseSpec" : {
"format" : "json",
How to design a system where you send instructions to an appliance like sonos or nest from your phone
===============
I am an iOS engineer and have just recently started doing side projects that required me to build products end-to-end (backend + serving/middle tier + front end). During one such exercise I wondered how to design a system where you send instructions to an appliance like sonos or nest from your phone.
How are such systems designed? I am looking to learn how to architect and build such systems.
For instance: What database would you choose to store the device information, user information and user-device relationship?
The flow of information I am thinking is of the following: