Java High Level Stream API
Download as pptx, pdf1 like1,932 views
The document provides an overview of the Stream API for Apex, detailing its architecture that utilizes Directed Acyclic Graphs (DAG) and custom operators for processing data streams. It includes examples of applications demonstrating word count functionality, highlighting the ease of use and flexibility of the high-level API. The document also outlines the current status and future roadmap for enhancements to the Stream API, as well as resources for further information.
Java High Level Stream API
- 1. Stream API For Apex June 2016
- 3. Apex Overview • YARN is the resource manager • HDFS used for storing any persistent state
- 4. Current Development Model Directed Acyclic Graph (DAG) Output Stream Tupl e Tupl e er Operator er Operator er Operator er Operator er Operator er Operator ● Stream is a sequence of data tuples ● Typical Operator takes one or more input streams, performs computations & emits one or more output streams ● Each operator is your custom business logic in java, or built-in operator from our open source library ● Operator has many instances that run in parallel and each instance is single-threaded ● Directed Acyclic Graph (DAG) is made up of operators and streams
- 5. Current Application Example @ApplicationAnnotation(name="WordCountDemo") public class Application implements StreamingApplication { @Override public void populateDAG(DAG dag, Configuration conf) { WordCountInputOperator input = dag.addOperator("wordinput", new WordCountInputOperator()); UniqueCounter<String> wordCount = dag.addOperator("count", new UniqueCounter<String>()); ConsoleOutputOperator consoleOperator = dag.addOperator("console", new ConsoleOutputOperator()); dag.addStream("wordinput-count", input.outputPort, wordCount.data); dag.addStream("count-console",wordCount.count, consoleOperator.input); } }
- 6. o Easier for beginners to start with o Fluent API o Smaller learning curve o Transform methods in one place vs operator library o Operator API provides flexibility while high-level API provides ease of use Why we need high-level API
- 8. Stream API (Application Example) @ApplicationAnnotation(name = "WordCountStreamingApiDemo") public class ApplicationWithStreamAPI implements StreamingApplication { @Override public void populateDAG(DAG dag, Configuration configuration) { String localFolder = "./src/test/resources/data"; ApexStream<String> stream = StreamFactory .fromFolder(localFolder) .flatMap(new Split()) .window(new WindowOption.GlobalWindow(), new TriggerOption().withEarlyFiringsAtEvery(Duration.millis(1000)).accumulatingFiredPanes()) .countByKey(new ConvertToKeyVal()).print(); stream.populateDag(dag); } }
- 9. How it works o ApexStream<T> literally means bounded/unbounded data set of type T o ApexStream<T> also holds a graph data struture of all operator and connections between operators from input to current point o Each transform method attach one or more operators to current graph data structure and return a new Apex Stream object o The graph data structure won’t be translated to Apex DAG until populateDag or run method are called
- 10. How it works (Con’t)
- 11. ○ Method chain for readability ○ Stateless transform(map, flatmap, filter) ○ Some input and output are available (file, console, Kafka) ○ Some interoperability (addOperator, getDag, set property/attributes etc) ○ Local mode and distributed mode ○ Annonymous function class support ○ Extensible Current Status
- 12. ○ WindowedStream is in pull request along with Operators that support it ○ A few window transforms (count, reduce, etc) ○ 3 Window types (fix window, sliding window, session window) ○ 3 Trigger types (early trigger, late trigger, at watermark) ○ 3 Accumulation modes(accumulate, discard, accumulation_retraction) ○ In memory window state (checkpointed) Current Status (Con’t)
- 13. Roadmap ○ Persistent window state for windowed operators (large state) ○ Fully follow Beam model (window, trigger, watermark) ○ Rich selection of windowed transform (group, combine, join) ○ Support custom window assignor ○ Support custom trigger ○ More input/output (hbase, cassendra, jdbc, etc) ○ Better schema support ○ More language support (java 8, scala, etc...) ○ What the community asks for
- 14. Resources ○ Apache Apex website - http://apex.apache.org/ ○ Subscribe - http://apex.apache.org/community.html ○ Download - http://apex.apache.org/downloads.html ○ Twitter - @ApacheApex; Follow - https://twitter.com/apacheapex ○ Facebook - https://www.facebook.com/ApacheApex/ ○ Meetup - http://www.meetup.com/topics/apache-apex ○ SlideShare - http://www.slideshare.net/ApacheApex/presentations ○ More Examples - https://github.com/DataTorrent/examples ○ Pull request https://github.com/apache/apex-malhar/pull/319 https://github.com/apache/apex-malhar/pull/327
- 15. Demo & Code Example ○ Word Count ○ AutoComplete