{'fraction_non_alphanumeric': 0.033084311632870865, 'fraction_numerical': 0.0, 'mean_word_length': 5.130718954248366, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The pipeflow approach: write once, run in different stream-processing engines

Recently, some distributed stream computing platforms, such as Storm and Spark Streaming, have been developed for processing massive data streams. However, these platforms lack support for higher-level declarative languages and provide only programming interfaces. Moreover, the users should be well versed of the syntax and programming constructs of each language in these platforms. In this paper, we are going to demonstrate our PipeFlow system. In the PipeFlow system, the user can write a stream-processing script (i.e., query) using a higher-level dataflow language. This script can be translated into different stream-processing programs that run in the corresponding engines. In this case, the user is only willing to know a single language, thus, he/she can write one stream-processing script and expects to execute this script on different engines.