Download as PDF, PPTX
More Related Content
Similar to Big Data visualization with Apache Spark and Zeppelin
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Big Data visualization with Apache Spark and Zeppelin
- 1. Big Data Visualization using ApacheSpark and Zeppelin Prajod Vettiyattil, Software Architect, Wipro https://in.linkedin.com/in/prajod @prajods
- 2. Agenda • Big Dataand Ecosystem tools • Apache Spark • Apache Zeppelin • Data Visualization • Combining Spark and Zeppelin 2
- 3. BIG DATA ANDECOSYSTEM TOOLS
- 4. Big Data • Datasize beyond systems capability – Terabyte, Petabyte, Exabyte • Storage – Commodity servers, RAID, SAN • Processing – In reasonable response time – A challenge here 4
- 5. Server Tradition processing tools •Move what ? – the data to the code or – the code to the data 5 Data Server move data to code move code to data Code
- 6. Traditional processing tools •Traditional tools – RDBMS, DWH, BI – High cost – Difficult to scale beyond certain data size • price/performance skew • data variety not supported 6
- 7. Map-Reduce and NoSQL •Hadoop toolset – Free and open source – Commodity hardware – Scales to exabytes(1018), maybe even more • Not only SQL – Storage and query processing only – Complements Hadoop toolset – Volume, velocity and variety 7
- 8. All is well? • Hadoop was designed for batch processing • Disk based processing: slow • Many tools to enhance Hadoop’s capabilities – Distributed cache, Haloop, Hive, HBase • Not for interactive and iterative 8
- 9.
- 10. What is singularity? 10 0 1000 2000 3000 4000 5000 6000 7000 8000 1 2 3 4 5 6 7 AIcapacity Decade Decade vs AI capacity Point of singularity
- 11. Technological singularity • WhenAI capability exceeds Human capacity • AI or non-AI singularity • 2045: http://en.wikipedia.org/wiki/Ray_Kurzweil – The predicted year 11
- 12.
- 13. History of Spark 13 Spark1.3.1 released 2015 March Spark 1.0.0 released. 100TB sort achieved in 23 mins 2014 Spark donated to Apache Software Foundation 2013 Spark becomes open source. 2010 Spark created by Matei Zaharia at UC Berkeley 2009
- 14. Contributors in Spark •Yahoo • Intel • UC Berkeley • … • 50+ organizations 14
- 15. Hadoop and Spark •Spark complements the Hadoop ecosystem • Replaces: Hadoop MR • Spark integrates with – HDFS – Hive – HBase – YARN 15
- 16. Other big datatools • Spark also integrates with – Kafka – ZeroMQ – Cassandra – Mesos 16
- 17. Programming Spark • Java •Scala • Python • R 17
- 18. Spark toolset 18 Apache Spark Spark SQL Spark Streaming MLlibGraphX Spark R Blink DB Spark Cassandra Tachyon
- 19. What is Sparkfor ? 19 Batch Interactive Streaming
- 20. The main difference:speed • RAM access vs Disk access – RAM access is 100,000 times faster ! 20 https://gist.github.com/hellerbarde/2843375
- 21. Lambda Architecture pattern •Used for Lambda architecture implementation – Batch layer – Speed layer – Serving layer 21 Batch Layer Speed Layer Serving Layer Data Input Data consumers
- 22. Worker Node Executor Deployment Architecture 22 MasterNode Executor Task Cache TaskTask Worker Node ExecutorExecutorExecutor HDFS Data Node HDFS Data Node TaskTaskTask Cache Spark’s Cluster Manager Spark Driver HDFS Name Node
- 23. Core features ofSpark • Rich API • RDD: Resilient Distributed Datasets • DAG based execution • Data caching • Strong ecosystem tool support 23
- 24. Sample code inscala • Find the top 100,000 Wikipedia pages by page views • Log file format: code, title, num_hits • enPages.map(l => l.split(" ")) .map(l => (l(1), l(2).toInt)) .reduceByKey(_+_, 200) .filter(x => x._2 > 100000) .map(x => (x._2, x._1)) .collect .foreach(println) 24
- 25.
- 26. Interactive data analytics •For Spark and Flink • Web front end • At the back end, it connects to – SQL systems(Eg: Hive) – Spark – Flink 26
- 27. Deployment Architecture 27 Spark /Flink / Hive Zeppelin daemon Web browser 1 Web browser 2 Web browser 3 Web Server Local Interpreters Optional Remote Interpreters
- 28. Notebook • Is whereyou do your data analysis • Web UI REPL with pluggable interpreters • Interpreters – Scala, Python, Angular, SparkSQL, Markdown and Shell 28
- 29.
- 30. User Interface features •Markdown • Dynamic HTML generation • Dynamic chart generation • Screen sharing via websockets 30
- 31. SQL Interpreter • SQLshell – Query spark data using SQL queries – Return normal text, HTML or chart type results 31
- 32. Scala interpreter forSpark • Similar to the Spark shell • Upload your data into Spark • Query the data sets(RDDs) in your Spark server • Execute map-reduce tasks • Actions on RDD • Transformations on RDD 32
- 33.
- 34.
- 35.
- 36. The need forvisualization 36 Big Data Do something to data User gets comprehensible data
- 37. Tools for DataPresentation Architecture 37 1.Identify 2.Locate 3.Manipulate 4.Format 5.Present A data analysis tool/toolset would support:
- 38. COMBINING SPARK ANDZEPPELIN
- 39. Spark and Zeppelin 39 Spark Worker Node Spark Master Node Spark Worker Node Zeppelindaemon Web browser 1 Web browser 2 Web browser 3 Web Server Local Interpreters Remote Interpreters
- 40. Zeppelin views: Tablefrom SQL 40
- 41. Zeppelin views: Tablefrom SQL 41 %sql select age, count(1) from bank where marital="${marital=single,single|divorced|married}" group by age order by age
- 42. Zeppelin views: Piechart from SQL 42
- 43. Zeppelin views: Barchart from SQL 43
- 44.
- 45. Share variables: MVVM •Between Scala/Python/Spark and Angular • Observe scala variables from angular 45 Scala-Spark Angular x = “foo” x = “bar” Zeppelin
- 46. Zeppelin views: Angular-scalabinding 46
- 47. Screen sharing usingZeppelin • Share your graphical reports – Live sharing – Get the share URL from zeppelin and share with others – Uses websockets • Embed live reports in web pages 47
- 48.
- 49. Spark and Zeppelin •Spark – Berkeley Data Analytics Stack – More source and sinks; SparkSQL • Zeppelin – Notebooks for • Machine Learning using Spark • GraphX and Mllib – Additional interpreters – Better graphics, steaming views – Report persistence – More report templates – Better angular integration 49
- 50.
- 51. Summary • Spark andtools • The need for visualization • The role of Zeppelin • Zeppelin – Spark integration 51
- 52.