Dynamics Talks: "Writing Spark Pipelines with Less Boilerplate Code" - Egor Pakhomov, AirBnB

•

0 likes•323 views

Apache Spark is a general-purpose big data execution engine. You can work with different data sources with the same set of API in both batch and streaming mode. Such flexibility is great if you are experienced Spark developer solving a complicated data engineering problem, which might include ML or streaming. In Airbnb, 95% of all data pipelines are daily batch jobs, which read from Hive tables and write to Hive tables. For such jobs, you would like to trade some flexibility for more extensive functionality around writing to Hive or multiple days processing orchestration. Another advantage of reducing flexibility is creating "best practices", which can be followed by less experienced data engineers. In Airbnb, we've created a framework called "Sputnik," which tries to address these issues. In this talk, I'll show the typical boilerplate code, which Sputnik tries to reduce and concepts it introduces to simplify pipeline development.

Technology

WritingSpark
pipelineswithless
boilerplatecode
EGOR PAKHOMOV • AIRBNB

https://ogirardot.ﬁles.wordpress.com/2015/05/future-of-spark.png
Toomuchflexibility!
Ourcase

Joblogic
• Job does some business logic (for example multiply every value
from input table by 2)
• Job specifies:
- Source tables and result tables
- Partitioning schema
- Validations for result data
JoblogicvsRunLogic Runlogic(examples)
• Running job for specific date retrieves input only for that date
from input table
• Job tries to write to table, which does not exists, so we need to
create the table
• Job runs in testing mode, so all result tables are created with
“_testing” suffix

SputnikHiveTableWriter:
• creates table with “CREATE TABLE” hive statement, if table
does not yet exist.
• updates table metainformation
• manage result table name (staging/testing mode)
• normalize dataframe schema according to result Hive table
• repartitions and tries to reduce number of result files on disk
• runs the checks on result, before saving it.
• Etc…
Writingdata
inSputnik

Readingdata
inSputnik
Reading dataframe:
Reading dataset:

BackfillinginSputnik HiveTable
2019-01-01 2019-01-02 2019-01-03 2019-01-04 2019-01-05 2019-01-06 2019-01-082019-01-07
Dailyjob
--ds2019-01-07
Dailyjob
--ds2019-01-08
t

BackfillinginSputnik HiveTable
2019-01-01 2019-01-02 2019-01-03 2019-01-04 2019-01-05 2019-01-06
Backfilljob
--startDate2019-01-01--endDate2019-01-06
t
--stepSize3

Environments
inSputnik
some_database.some_input_table
some_database.result_table
Production
Sputnik

Environments
inSputnik
some_database.some_input_table
some_database.result_table
Production
Sputnik
some_database.result_table_dev
Testing
Sputnik
some_database.some_input_table

Environments
inSputnik
some_database.result_table_dev
Testing
Sputnik
some_database.some_input_table
-- writeEnv PROD some_database.result_table
-- writeEnv STAGE some_database.result_table_staging
-- writeEnv DEV some_database.result_table_dev

https://github.com/airbnb/sputnik
pahomov.egor@gmail.com
egor.pakhomov@airbnb.com

The document discusses using batch Apex jobs to improve the user experience by offloading long-running or complex processes asynchronously. It provides examples of scenarios where batch Apex would be useful, including updating 324k accounts, nulling a field on 142k opportunities, and changing record types on opportunities. The document also includes sample batch Apex code to implement these scenarios and discusses testing and monitoring batch jobs.

Batch Apex in Salesforce

David Helgerson

Windows Server AppFabric

Robert MacLean

The document discusses testing and deploying a workflow service application using Windows Server AppFabric and provides the following steps: 1. Prepare a demo workflow service app in Visual Studio to add and return the sum of two input integers. 2. Publish the app to a local IIS website using web deploy and test it using the WCF test client. 3. View and configure the services and endpoints for the site using the AppFabric dashboard. 4. Update the project's web.config and add error handling to demonstrate the AppFabric logging capabilities.

Дмитрий Лемешко. Comaqa Spring 2018. Continuous mobile automation in build pi...

COMAQA.BY

В докладе я расскажу, как был организован запуск автоматических тестов (appium/javascript) в gitlab CI для нативного Android приложения на каждый Merge Request. Опишу, как можно встроить автотесты в существующий процесс сборки, как правильно настроить запуск тестов в docker image (тесты бегут в TestObject облаке), как произошла интеграция с клаудом и какие результаты это принесло. Tech stack: Gitlab CI, kubernetes, android, appium, javascript, testobject.

Salesforce DUG - Queueable Apex

Akshay Varu

Batchable vs @future vs Queueable

Boris Bachovski

Batchable, @future, and Queueable are interfaces in Apex that allow for asynchronous and batch processing. Batchable is used for processing large numbers of records asynchronously in batches of up to 50 million records. It defines start(), execute(), and finish() methods and allows scheduling batch jobs to run at a specific time. However, there are limits such as only 5 concurrent batch jobs and no @future calls allowed within a batch. @future allows for simple, frequent asynchronous processing of single records through static void methods but only supports primitive arguments. It has no concurrency limits but parameters are limited and jobs cannot be chained. Queueable is used when Batchable and @future need to be combined, such

SFDC Batch Apex

Sujit Kumar

This document provides an overview of Force.com Batch Apex, which allows processing of large data sets asynchronously by splitting the data into batches that are processed sequentially. Key aspects covered include the batchable interface with start, execute, and finish methods; splitting data into transactions of up to 200 records each; monitoring and error handling; making batches stateful; using query locators or iterables; testing and scheduling batches; and limitations of batch apex.

Salesforce asynchronous apex

Badan Singh Pundeer

When executing something synchronously, you wait for it to finish before moving on to another task. Asynchronously, you can move on before it finishes. Future methods, Queueable Apex, and Batch Apex allow asynchronous execution in Apex. Future methods are best for long-running methods or callouts. Queueable Apex allows job chaining and passing complex types. Batch Apex is best for large data volumes processed in batches. Continuations allow asynchronous callouts from Visualforce pages.

The document outlines the steps to create a Rails application called Depot that includes a Product model with title, description, image_url, and price attributes. It describes generating a scaffold for the Product model, running migrations to set up the database table, seeding the database with sample data, and pushing the application to Heroku. Key steps include generating the Rails application, adding the Product model, configuring the database, and deploying the application.

Gatling @ Scala.Io 2013

slandelle

Gatling 2 is planned for 2014 and will include significant refactoring and new features. Some key changes include: 1. A new expression API that uses Validation to handle errors and support different data types. 2. Improvements to the session API to make data access safer. 3. A new templating API that supports string interpolation and external EL templates for simple use cases. 4. Enhancements to checks like regex to support capturing multiple groups and different data types. 5. Support for fetching embedded resources in parallel to better simulate browser behavior during load tests.

Gatling

Gaurav Shukla

Load test REST APIs using gatling

Jayaram Sankaranarayanan

Governor limits

Shivanath Devinarayanan

Governor limits in Salesforce enforce runtime limits on Apex code to ensure fair sharing of system resources among multiple tenants. The key governor limits include limits on the number of SOQL queries, records retrieved, and number of scripts executed. Governor limits are calculated based on the entry point for the Apex code, such as Apex triggers, web services, or anonymous blocks. Limits are shared across an organization and apply to all code executed within a synchronous transaction, while asynchronous code like future methods has separate limits. Developers must optimize code to avoid hitting governor limits, for example by bulkifying code, minimizing SOQL queries, and using future calls appropriately.

Database Build and Release - SQL In The City - Ernest Hwang

Red Gate Software

Ernest Hwang discusses automating database maintenance tasks using Red Gate SQL Source Control, continuous integration with Jenkins, and unit testing with tSQLt. He demonstrates committing database changes to source control, how continuous integration runs builds and tests on each commit, and deploying changes between environments with SQL Compare. Automating these processes saves developers time by eliminating manual scripting and deployments while improving quality by catching errors early in continuous integration builds and unit tests.

Continuous performance management with Gatling

Radoslaw Smilgin

ajn11 BT appengine SDK updates

SATOSHI TAGOMORI

The document summarizes updates to the Google App Engine SDK in versions 1.3.3 through 1.3.8. Key updates include: allowing immediate task queue execution and higher bucket sizes in the admin console, removing limits on complex queries, adding an instances page to view server performance, and experimental tools to delete all or by-type entities in the Python SDK. It also notes new app.yaml handlers, login session length increase, and precompilation changes for Python.

7 steps to simplifying your AI workflows

Wisecube AI

1) Nephos is a hybrid cloud-enabled AI workflow service that allows users to visually build and run AI workflows in the cloud. It provides a visual workflow editor to drag and drop datasets, executables, and draw connecting edges to create workflows. 2) The 7 steps to using Nephos include: setting up a cloud cluster, registering resources like datasets and executables, creating the first AI workflow, running the workflow, experimenting on workflows, collaborating with others, and scheduling recurring workflow runs as jobs. 3) Key features of Nephos include supporting hybrid clouds, using open source technologies like Pegasus and Docker, and being built by experienced AI practitioners to simplify complex AI workflows.

How To Practice TDD Without Shooting Yourself In The Foot

Dennis Doomen

It's 2018, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven't really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks.

Build, Test and Extend Integrated Workflows 3.7

StephenKardian

This document discusses building, testing, and extending integrated workflows in Neuron ESB. It covers containers, flow control, exception management, external assemblies, message processing, arguments and variables, custom workflows and activities, building workflows, and debugging workflows. The goals are to understand complex workflow logic, custom activities, flow control, exception handling, external code integration, message transformation, and testing workflows.

Metrics

Zach Cox

This document summarizes Zach Cox's presentation on metrics and the Metrics library. It discusses why metrics are important for business value and runtime performance. It also outlines the different metric types (gauge, counter, meter, histogram, timer), how to instrument code to collect metrics, and how to report metrics to tools like Graphite, Ganglia, JMX and CloudWatch. The document provides examples of how Pongr uses Metrics to collect timers and meters and report to Graphite, and how Rexster uses Metrics for monitoring.

Runtime performance

Eliran Eliassy

This document provides tips and tools for improving Angular application runtime performance. It discusses measuring performance using Benchmark.js, Chrome Dev Tools profiler, and @angular/benchpress. Specific optimizations covered include using the Ivy renderer, lazy loading modules, pre-rendering with Angular Universal, caching requests with service workers, immutable data structures, memoization, trackBy in *ngFor, virtual scrolling, RxJS operators, and controlling change detection. The document aims to help developers measure and improve the runtime performance of their Angular applications.

C# 6 New Features

zahid-mian

Spring batch

Chandan Kumar Rana

This document provides an overview of Spring Batch, an open source framework for batch processing in Java. It describes key concepts in Spring Batch including jobs which contain steps, item readers which provide input, item writers which handle output, and tasklets which represent units of work. The document also discusses architectures, executions, repositories for metadata, and other services like job launchers and locators.

Reactive

Pranav E K

This document provides an introduction to reactive programming with Reactor. It discusses some of the challenges with traditional imperative programming like blocking I/O and latency. Reactor uses asynchronous programming to improve responsiveness. It introduces key concepts like Mono and Flux for publishing 0-1 and 0-N values respectively. Examples are given for creating Mono and Flux instances. The document also mentions backpressure and how Reactor provides a high-level but valuable abstraction with readable and composable code.

PerfTest in SOA

Tharinda Liyanage

This document discusses performance testing for service oriented architectures (SOA) and enterprise middleware. It covers typical server performance patterns like latency and throughput. It recommends establishing a clustered test environment that mirrors production. Open source tools for performance testing SOA are discussed, including Apache JMeter for load testing and soapUI for functional tests. The document also covers monitoring tools for analyzing performance.

Apache Spark-Bench: Simulate, Test, Compare, Exercise, and Yes, Benchmark wit...

Spark Summit

spark-bench is an open-source benchmarking tool, and it’s also so much more. spark-bench is a flexible system for simulating, comparing, testing, and benchmarking Spark applications and Spark itself. spark-bench originally began as a benchmarking suite to get timing numbers on very specific algorithms mostly in the machine learning domain. Since then it has morphed into a highly configurable and flexible framework suitable for many use cases. This talk will discuss the high level design and capabilities of spark-bench before walking through some major, practical use cases. Use cases include, but are certainly not limited to: regression testing changes to Spark; comparing performance of different hardware and Spark tuning options; simulating multiple notebook users hitting a cluster at the same time; comparing parameters of a machine learning algorithm on the same set of data; providing insight into bottlenecks through use of compute-intensive and i/o-intensive workloads; and, yes, even benchmarking. In particular this talk will address the use of spark-bench in developing new features features for Spark core.

Sputnik: Airbnb’s Apache Spark Framework for Data Engineering

Databricks

CODAIT/Spark-Bench

Emily Curtin

Spark Summit 2014: Spark Job Server Talk

Evan Chan

This document discusses Spark Job Server, an open source project that allows Spark jobs to be submitted and run via a REST API. It provides features like job monitoring, context sharing between jobs to reuse cached data, and asynchronous APIs. The document outlines motivations for the project, how to use it including submitting and monitoring jobs, and future plans like high availability and hot failover support.

MuleSoft ESB Filtering data instead of Looping

akashdprajapati

This document provides instructions for filtering data instead of using a For-Each loop in MuleSoft ESB. It describes creating a Mule project with a Transform Message component containing a filter to select data, such as processing only employee records where the name is "ABC". The input payload is a sample JSON file containing an array of employee objects. A logger demonstrates that only the filtered record is processed, avoiding the need to loop through all data.

What's hot

Creating the application

Jason Noble

Gatling @ Scala.Io 2013

slandelle

Gatling

Gaurav Shukla

Load test REST APIs using gatling

Jayaram Sankaranarayanan

Governor limits

Shivanath Devinarayanan

Database Build and Release - SQL In The City - Ernest Hwang

Red Gate Software

Continuous performance management with Gatling

Radoslaw Smilgin

ajn11 BT appengine SDK updates

SATOSHI TAGOMORI

7 steps to simplifying your AI workflows

Wisecube AI

How To Practice TDD Without Shooting Yourself In The Foot

Dennis Doomen

Build, Test and Extend Integrated Workflows 3.7

Metrics

Runtime performance

C# 6 New Features

Spring batch

Reactive

PerfTest in SOA

What's hot (17)

Creating the application

Gatling @ Scala.Io 2013

Gatling

Load test REST APIs using gatling

Governor limits

Database Build and Release - SQL In The City - Ernest Hwang

Continuous performance management with Gatling

ajn11 BT appengine SDK updates

7 steps to simplifying your AI workflows

How To Practice TDD Without Shooting Yourself In The Foot

Build, Test and Extend Integrated Workflows 3.7

Metrics

Runtime performance

C# 6 New Features

Spring batch

Reactive

PerfTest in SOA

Similar to Dynamics Talks: "Writing Spark Pipelines with Less Boilerplate Code" - Egor Pakhomov, AirBnB

Apache Spark-Bench: Simulate, Test, Compare, Exercise, and Yes, Benchmark wit...

Spark Summit

Sputnik: Airbnb’s Apache Spark Framework for Data Engineering

Databricks

CODAIT/Spark-Bench

Emily Curtin

Spark Summit 2014: Spark Job Server Talk

Evan Chan

MuleSoft ESB Filtering data instead of Looping

akashdprajapati

How We Optimize Spark SQL Jobs With parallel and sync IO

Databricks

Although NVMe has been more and more popular these years, a large amount of HDD are still widely used in super-large scale big data clusters. In a EB-level data platform, IO(including decompression and decode) cost contributes a large proportion of Spark jobs’ cost. In another word, IO operation is worth optimizing. In ByteDancen, we do a series of IO optimization to improve performance, including parallel read and asynchronized shuffle. Firstly we implement file level parallel read to improve performance when there are a lot of small files. Secondly, we design row group level parallel read to accelerate queries for big-file scenario. Thirdly, implement asynchronized spill to improve job peformance. Besides, we design parquet column family, which will split a table into a few column families and different column family will be in different Parquets files. Different column family can be read in parallel, so the read performance is much higher than the existing approach. In our practice, the end to end performance is improved by 5% to 30% In this talk, I will illustrate how we implement these features and how they accelerate Apache Spark jobs.

Analytics Metrics delivery and ML Feature visualization: Evolution of Data Pl...

Chester Chen

GoPro’s camera, drone, mobile devices as well as web, desktop applications are generating billions of event logs. The analytics metrics and insights that inform product, engineering, and marketing team decisions need to be distributed quickly and efficiently. We need to visualize the metrics to find the trends or anomalies. While trying to building up the features store for machine learning, we need to visualize the features, Google Facets is an excellent project for visualizing features. But can we visualize larger feature dataset? These are issues we encounter at GoPro as part of the data platform evolution. In this talk, we will discuss few of the progress we made at GoPro. We will talk about how to use Slack + Plot.ly to delivery analytics metrics and visualization. And we will also discuss our work to visualize large feature set using Google Facets with Apache Spark.

Database Fundamental Concepts- Series 1 - Performance Analysis

DAGEOP LTD

This document discusses various tools and techniques for SQL Server performance analysis. It describes tools like SQL Trace, SQL Server Profiler, Distributed Replay Utility, Activity Monitor, graphical show plans, stored procedures, DBCC commands, built-in functions, trace flags, and analyzing STATISTICS IO output. These tools help identify performance bottlenecks, monitor server activity, diagnose issues using traces, and evaluate hardware upgrades. The document also covers using SQL Server Profiler to identify problems by creating, watching, storing and replaying traces.

Sqoop on Spark for Data Ingestion

DataWorks Summit

Sqoop on Spark provides a way to run Sqoop jobs using Apache Spark for parallel data ingestion. It allows Sqoop jobs to leverage Spark's speed and growing community. The key aspects covered are: - Sqoop jobs can be created and executed on Spark by initializing a Spark context and wrapping Sqoop and Spark initialization. - Data is partitioned and extracted in parallel using Spark RDDs and map transformations calling Sqoop connector APIs. - Loading also uses Spark RDDs and map transformations to parallelly load data calling connector load APIs. - Microbenchmarks show Spark-based ingestion can be significantly faster than traditional MapReduce-based Sqoop for large datasets

Quick tour to front end unit testing using jasmine

Gil Fink

This document discusses front-end unit testing using the Jasmine testing framework. It explains why unit testing is important, introduces behavior-driven development and the Jasmine framework. It also provides an overview of setting up Jasmine, creating test suites and specs, using matchers, and testing asynchronous code. The document demonstrates how to set up the testing environment, write tests with Jasmine, and integrate Jasmine with the Karma test runner.

Batching and Java EE (jdk.io)

Ryan Cuprak

JDK.IO 2016 (http://jdk.io) Java EE 7 introduced a new batch processing API. This session will go over how to use the batch processing API introduced with Java EE 7. This API is makes it easy to implement long running data/compute intensive jobs which need to be scheduled or initiated on-demand. Basics of the API will be demonstrated via code samples. The API will also be compared to Spring Batching and Hadoop to provide context and guidance on when these technologies are appropriate.

Java EE 7 Batch processing in the Real World

Roberto Cortez

This talk will explore one of the newest API for Java EE 7, the JSR 352, Batch Applications for the Java Platform. Batch processing is found in nearly every industry when you need to execute a non-interactive, bulk-oriented and long running operation task. A few examples are: financial transactions, billing, inventory management, report generation and so on. The JSR 352 specifies a common set of requirements that every batch application usually needs like: checkpointing, parallelization, splitting and logging. It also provides you with a job specification language and several interfaces that allow you to implement your business logic and interact with the batch container. We are going to live code a real life example batch application, starting with a simple task and then evolve it using the advanced API's until we have a full parallel and checkpointing reader-processor-writer batch. By the end of the session, attendees should be able to understand the use cases of the JSR 352, when to apply it and how to develop a full Java EE Batch Application.

Query Optimization with MySQL 5.6: Old and New Tricks - Percona Live London 2013

Jaime Crespo

Tutorial delivered at Percona MySQL Conference Live London 2013. It doesn't matter what new SSD technologies appear, or what are the latest breakthroughs in flushing algorithms: the number one cause for MySQL applications being slow is poor execution plan of SQL queries. While the latest GA version provided a huge amount of transparent optimizations -specially for JOINS and subqueries- it is still the developer's responsibility to take advantage of all new MySQL 5.6 features. In this tutorial we will propose the attendants a sample PHP application with bad response time. Through practical examples, we will suggest step-by-step strategies to improve its performance, including: * Checking MySQL & InnoDB configuration * Internal (performance_schema) and external tools for profiling (pt-query-digest) * New EXPLAIN tools * Simple and multiple column indexing * Covering index technique * Index condition pushdown * Batch key access * Subquery optimization

Springaopdecoded ajip

Makarand Bhatambarekar

This document discusses Spring AOP and how it can be used to add logging and performance monitoring across multiple classes and methods. It covers the problem of invasive and non-DRY logging code. It then explains key AOP concepts like pointcuts, advice, aspects, proxies, and weaving. It provides examples of defining pointcuts and advice for logging and monitoring using both annotation and XML-based Spring AOP configuration.

An Approach to Sql tuning - Part 1

Navneet Upneja

This document discusses SQL tuning and provides an overview of the SQL execution process. It outlines the steps to identify and analyze poorly performing SQL, including using views like v$session to find long running sessions, AWR to find top SQL, and generating execution plans using EXPLAIN PLAN or DBMS_XPLAN to interpret execution plans and identify bottlenecks. The next session will cover interpreting execution plans in more detail as well as additional techniques for SQL tuning.

Oracle SQL Tuning for Day-to-Day Data Warehouse Support

nkarag

10 Reasons to Start Your Analytics Project with PostgreSQL

Satoshi Nagayasu

PostgreSQL provides several advantages for analytics projects: 1) It allows connecting to external data sources and performing analytics queries across different data stores using features like foreign data wrappers. 2) Features like materialized views, transactional DDLs, and rich SQL capabilities help build effective data warehouses and data marts for analytics. 3) Performance optimizations like table partitioning, BRIN indexes, and parallel queries enable PostgreSQL to handle large datasets and complex queries efficiently.

Spring batch for large enterprises operations

Ignasi González

Spring Batch is a framework for writing batch applications in Java. It was designed to be integrated with Spring and supports features like dependency injection, transactions, and job processing. The document discusses two examples of large enterprises using Spring Batch: a bank undergoing a migration to a new mid-level system and an energy company with multiple software vendors. It describes how Spring Batch was used to integrate batch jobs, monitor executions, and facilitate the migration process at both companies.

OOW13 Exadata and ODI with Parallel

Kellyn Pot'Vin-Gorman

This document summarizes a case study on using Exadata, Oracle Data Integrator (ODI), and parallel data loading to improve ETL performance. It describes how the environment had performance issues with ODI loads due to temporary tablespace usage. Tuning included setting dynamic sampling to 0, adding rollup tables and materialized views to pre-aggregate data, and indexing to reduce sorting and aggregation during loads. These changes led to significant improvements in elapsed time.

Spark summit2014 techtalk - testing spark

Anu Shetty

The document discusses best practices for testing Spark applications including setting up test environments for unit and integration testing Spark in both batch and streaming modes. It also covers performance testing Spark applications using Gatling, including developing a sample performance test for a word count Spark job run on Spark job server. Key steps for testing, code coverage, continuous integration and analyzing performance test results are provided.

Similar to Dynamics Talks: "Writing Spark Pipelines with Less Boilerplate Code" - Egor Pakhomov, AirBnB (20)

Apache Spark-Bench: Simulate, Test, Compare, Exercise, and Yes, Benchmark wit...

Sputnik: Airbnb’s Apache Spark Framework for Data Engineering

CODAIT/Spark-Bench

Spark Summit 2014: Spark Job Server Talk

MuleSoft ESB Filtering data instead of Looping

How We Optimize Spark SQL Jobs With parallel and sync IO

Analytics Metrics delivery and ML Feature visualization: Evolution of Data Pl...

Database Fundamental Concepts- Series 1 - Performance Analysis

Sqoop on Spark for Data Ingestion

Quick tour to front end unit testing using jasmine

Batching and Java EE (jdk.io)

Java EE 7 Batch processing in the Real World

Query Optimization with MySQL 5.6: Old and New Tricks - Percona Live London 2013

Springaopdecoded ajip

An Approach to Sql tuning - Part 1

Oracle SQL Tuning for Day-to-Day Data Warehouse Support

10 Reasons to Start Your Analytics Project with PostgreSQL

Spring batch for large enterprises operations

OOW13 Exadata and ODI with Parallel

Spark summit2014 techtalk - testing spark

More from Grid Dynamics

Are you keeping up with your customer

Dynamics Talks: "Writing Spark Pipelines with Less Boilerplate Code" - Egor Pakhomov, AirBnB

Recommended

Recommended

More Related Content

What's hot

What's hot (17)

Similar to Dynamics Talks: "Writing Spark Pipelines with Less Boilerplate Code" - Egor Pakhomov, AirBnB

Similar to Dynamics Talks: "Writing Spark Pipelines with Less Boilerplate Code" - Egor Pakhomov, AirBnB (20)

More from Grid Dynamics

More from Grid Dynamics (20)

Recently uploaded

Recently uploaded (20)

Dynamics Talks: "Writing Spark Pipelines with Less Boilerplate Code" - Egor Pakhomov, AirBnB