| Ian Maxon | 41b806c | 2019-03-07 15:58:20 -0800 | [diff] [blame^] | 1 | <!DOCTYPE html> |
| 2 | <!-- |
| 3 | | Generated by Apache Maven Doxia Site Renderer 1.8.1 from src/site/markdown/feeds/tutorial.md at 2019-03-07 |
| 4 | | Rendered using Apache Maven Fluido Skin 1.7 |
| 5 | --> |
| 6 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> |
| 7 | <head> |
| 8 | <meta charset="UTF-8" /> |
| 9 | <meta name="viewport" content="width=device-width, initial-scale=1.0" /> |
| 10 | <meta name="Date-Revision-yyyymmdd" content="20190307" /> |
| 11 | <meta http-equiv="Content-Language" content="en" /> |
| 12 | <title>AsterixDB – Support for Data Ingestion in AsterixDB</title> |
| 13 | <link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" /> |
| 14 | <link rel="stylesheet" href="../css/site.css" /> |
| 15 | <link rel="stylesheet" href="../css/print.css" media="print" /> |
| 16 | <script type="text/javascript" src="../js/apache-maven-fluido-1.7.min.js"></script> |
| 17 | |
| 18 | </head> |
| 19 | <body class="topBarDisabled"> |
| 20 | <div class="container-fluid"> |
| 21 | <div id="banner"> |
| 22 | <div class="pull-left"><a href=".././" id="bannerLeft"><img src="../images/asterixlogo.png" alt="AsterixDB"/></a></div> |
| 23 | <div class="pull-right"></div> |
| 24 | <div class="clear"><hr/></div> |
| 25 | </div> |
| 26 | |
| 27 | <div id="breadcrumbs"> |
| 28 | <ul class="breadcrumb"> |
| 29 | <li id="publishDate">Last Published: 2019-03-07</li> |
| 30 | <li id="projectVersion" class="pull-right">Version: 0.9.4</li> |
| 31 | <li class="pull-right"><a href="../index.html" title="Documentation Home">Documentation Home</a></li> |
| 32 | </ul> |
| 33 | </div> |
| 34 | <div class="row-fluid"> |
| 35 | <div id="leftColumn" class="span2"> |
| 36 | <div class="well sidebar-nav"> |
| 37 | <ul class="nav nav-list"> |
| 38 | <li class="nav-header">Get Started - Installation</li> |
| 39 | <li><a href="../ncservice.html" title="Option 1: using NCService"><span class="none"></span>Option 1: using NCService</a></li> |
| 40 | <li><a href="../ansible.html" title="Option 2: using Ansible"><span class="none"></span>Option 2: using Ansible</a></li> |
| 41 | <li><a href="../aws.html" title="Option 3: using Amazon Web Services"><span class="none"></span>Option 3: using Amazon Web Services</a></li> |
| 42 | <li class="nav-header">AsterixDB Primer</li> |
| 43 | <li><a href="../sqlpp/primer-sqlpp.html" title="Option 1: using SQL++"><span class="none"></span>Option 1: using SQL++</a></li> |
| 44 | <li><a href="../aql/primer.html" title="Option 2: using AQL"><span class="none"></span>Option 2: using AQL</a></li> |
| 45 | <li class="nav-header">Data Model</li> |
| 46 | <li><a href="../datamodel.html" title="The Asterix Data Model"><span class="none"></span>The Asterix Data Model</a></li> |
| 47 | <li class="nav-header">Queries - SQL++</li> |
| 48 | <li><a href="../sqlpp/manual.html" title="The SQL++ Query Language"><span class="none"></span>The SQL++ Query Language</a></li> |
| 49 | <li><a href="../sqlpp/builtins.html" title="Builtin Functions"><span class="none"></span>Builtin Functions</a></li> |
| 50 | <li class="nav-header">Queries - AQL</li> |
| 51 | <li><a href="../aql/manual.html" title="The Asterix Query Language (AQL)"><span class="none"></span>The Asterix Query Language (AQL)</a></li> |
| 52 | <li><a href="../aql/builtins.html" title="Builtin Functions"><span class="none"></span>Builtin Functions</a></li> |
| 53 | <li class="nav-header">API/SDK</li> |
| 54 | <li><a href="../api.html" title="HTTP API"><span class="none"></span>HTTP API</a></li> |
| 55 | <li><a href="../csv.html" title="CSV Output"><span class="none"></span>CSV Output</a></li> |
| 56 | <li class="nav-header">Advanced Features</li> |
| 57 | <li><a href="../aql/fulltext.html" title="Support of Full-text Queries"><span class="none"></span>Support of Full-text Queries</a></li> |
| 58 | <li><a href="../aql/externaldata.html" title="Accessing External Data"><span class="none"></span>Accessing External Data</a></li> |
| 59 | <li class="active"><a href="#"><span class="none"></span>Support for Data Ingestion</a></li> |
| 60 | <li><a href="../udf.html" title="User Defined Functions"><span class="none"></span>User Defined Functions</a></li> |
| 61 | <li><a href="../aql/filters.html" title="Filter-Based LSM Index Acceleration"><span class="none"></span>Filter-Based LSM Index Acceleration</a></li> |
| 62 | <li><a href="../aql/similarity.html" title="Support of Similarity Queries"><span class="none"></span>Support of Similarity Queries</a></li> |
| 63 | </ul> |
| 64 | <hr /> |
| 65 | <div id="poweredBy"> |
| 66 | <div class="clear"></div> |
| 67 | <div class="clear"></div> |
| 68 | <div class="clear"></div> |
| 69 | <div class="clear"></div> |
| 70 | <a href=".././" title="AsterixDB" class="builtBy"><img class="builtBy" alt="AsterixDB" src="../images/asterixlogo.png" /></a> |
| 71 | </div> |
| 72 | </div> |
| 73 | </div> |
| 74 | <div id="bodyColumn" class="span10" > |
| 75 | <!-- |
| 76 | ! Licensed to the Apache Software Foundation (ASF) under one |
| 77 | ! or more contributor license agreements. See the NOTICE file |
| 78 | ! distributed with this work for additional information |
| 79 | ! regarding copyright ownership. The ASF licenses this file |
| 80 | ! to you under the Apache License, Version 2.0 (the |
| 81 | ! "License"); you may not use this file except in compliance |
| 82 | ! with the License. You may obtain a copy of the License at |
| 83 | ! |
| 84 | ! http://www.apache.org/licenses/LICENSE-2.0 |
| 85 | ! |
| 86 | ! Unless required by applicable law or agreed to in writing, |
| 87 | ! software distributed under the License is distributed on an |
| 88 | ! "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
| 89 | ! KIND, either express or implied. See the License for the |
| 90 | ! specific language governing permissions and limitations |
| 91 | ! under the License. |
| 92 | !--> |
| 93 | <h1>Support for Data Ingestion in AsterixDB</h1> |
| 94 | <div class="section"> |
| 95 | <h2><a name="Table_of_Contents"></a><a name="atoc" id="#toc">Table of Contents</a></h2> |
| 96 | <ul> |
| 97 | |
| 98 | <li><a href="#Introduction">Introduction</a></li> |
| 99 | <li><a href="#FeedAdapters">Feed Adapters</a></li> |
| 100 | </ul><!-- * [Feed Policies](#FeedPolicies) --> |
| 101 | </div> |
| 102 | <div class="section"> |
| 103 | <h2><a name="Introduction">Introduction</a></h2> |
| 104 | <p>In this document, we describe the support for data ingestion in AsterixDB. Data feeds are a new mechanism for having continuous data arrive into a BDMS from external sources and incrementally populate a persisted dataset and associated indexes. We add a new BDMS architectural component, called a data feed, that makes a Big Data system the caretaker for functionality that used to live outside, and we show how it improves users’ lives and system performance.</p></div> |
| 105 | <div class="section"> |
| 106 | <h2><a name="Feed_Adapters"></a><a name="FeedAdapters">Feed Adapters</a></h2> |
| 107 | <p>The functionality of establishing a connection with a data source and receiving, parsing and translating its data into ADM objects (for storage inside AsterixDB) is contained in a feed adapter. A feed adapter is an implementation of an interface and its details are specific to a given data source. An adapter may optionally be given parameters to configure its runtime behavior. Depending upon the data transfer protocol/APIs offered by the data source, a feed adapter may operate in a push or a pull mode. Push mode involves just one initial request by the adapter to the data source for setting up the connection. Once a connection is authorized, the data source “pushes” data to the adapter without any subsequent requests by the adapter. In contrast, when operating in a pull mode, the adapter makes a separate request each time to receive data. AsterixDB currently provides built-in adapters for several popular data sources such as Twitter and RSS feeds. AsterixDB additionally provides a generic socket-based adapter that can be used to ingest data that is directed at a prescribed socket.</p> |
| 108 | <p>In this tutorial, we shall describe building two example data ingestion pipelines that cover the popular scenarios of ingesting data from (a) Twitter (b) RSS (c) Socket Feed source.</p> |
| 109 | <div class="section"> |
| 110 | <div class="section"> |
| 111 | <h4><a name="Ingesting_Twitter_Stream"></a>Ingesting Twitter Stream</h4> |
| 112 | <p>We shall use the built-in push-based Twitter adapter. As a pre-requisite, we must define a Tweet using the AsterixDB Data Model (ADM) and the AsterixDB Query Language (AQL). Given below are the type definitions in AQL that create a Tweet datatype which is representative of a real tweet as obtained from Twitter.</p> |
| 113 | |
| 114 | <div> |
| 115 | <div> |
| 116 | <pre class="source"> create dataverse feeds; |
| 117 | use dataverse feeds; |
| 118 | |
| 119 | create type TwitterUser as closed { |
| 120 | screen_name: string, |
| 121 | lang: string, |
| 122 | friends_count: int32, |
| 123 | statuses_count: int32 |
| 124 | }; |
| 125 | |
| 126 | create type Tweet as open { |
| 127 | id: int64, |
| 128 | user: TwitterUser |
| 129 | } |
| 130 | |
| 131 | create dataset Tweets (Tweet) |
| 132 | primary key id; |
| 133 | </pre></div></div> |
| 134 | |
| 135 | <p>We also create a dataset that we shall use to persist the tweets in AsterixDB. Next we make use of the <tt>create feed</tt> AQL statement to define our example data feed.</p> |
| 136 | <div class="section"> |
| 137 | <h5><a name="Using_the_.E2.80.9Cpush_twitter.E2.80.9D_feed_adapter"></a>Using the “push_twitter” feed adapter</h5> |
| 138 | <p>The “push_twitter” adapter requires setting up an application account with Twitter. To retrieve tweets, Twitter requires registering an application. Registration involves providing a name and a brief description for the application. Each application has associated OAuth authentication credentials that include OAuth keys and tokens. Accessing the Twitter API requires providing the following. 1. Consumer Key (API Key) 2. Consumer Secret (API Secret) 3. Access Token 4. Access Token Secret</p> |
| 139 | <p>The “push_twitter” adapter takes as configuration the above mentioned parameters. End users are required to obtain the above authentication credentials prior to using the “push_twitter” adapter. For further information on obtaining OAuth keys and tokens and registering an application with Twitter, please visit <a class="externalLink" href="http://apps.twitter.com">http://apps.twitter.com</a></p> |
| 140 | <p>Given below is an example AQL statement that creates a feed called “TwitterFeed” by using the “push_twitter” adapter.</p> |
| 141 | |
| 142 | <div> |
| 143 | <div> |
| 144 | <pre class="source"> use dataverse feeds; |
| 145 | |
| 146 | create feed TwitterFeed if not exists using "push_twitter" |
| 147 | (("type-name"="Tweet"), |
| 148 | ("format"="twitter-status"), |
| 149 | ("consumer.key"="************"), |
| 150 | ("consumer.secret"="**************"), |
| 151 | ("access.token"="**********"), |
| 152 | ("access.token.secret"="*************")); |
| 153 | </pre></div></div> |
| 154 | |
| 155 | <p>It is required that the above authentication parameters are provided valid. Note that the <tt>create feed</tt> statement does not initiate the flow of data from Twitter into the AsterixDB instance. Instead, the <tt>create feed</tt> statement only results in registering the feed with the instance. The flow of data along a feed is initiated when it is connected to a target dataset using the connect feed statement and activated using the start feed statement.</p> |
| 156 | <p>The Twitter adapter also supports several Twitter streaming APIs as follow:</p> |
| 157 | <ol style="list-style-type: decimal"> |
| 158 | |
| 159 | <li>Track filter (“keywords”=“AsterixDB, Apache”)</li> |
| 160 | <li>Locations filter (“locations”=“-29.7, 79.2, 36.7, 72.0; -124.848974,-66.885444, 24.396308, 49.384358”)</li> |
| 161 | <li>Language filter (“language”=“en”)</li> |
| 162 | <li>Filter level (“filter-level”=“low”)</li> |
| 163 | </ol> |
| 164 | <p>An example of Twitter adapter tracking tweets with keyword “news” can be described using following ddl:</p> |
| 165 | |
| 166 | <div> |
| 167 | <div> |
| 168 | <pre class="source"> use dataverse feeds; |
| 169 | |
| 170 | create feed TwitterFeed if not exists using "push_twitter" |
| 171 | (("type-name"="Tweet"), |
| 172 | ("format"="twitter-status"), |
| 173 | ("consumer.key"="************"), |
| 174 | ("consumer.secret"="**************"), |
| 175 | ("access.token"="**********"), |
| 176 | ("access.token.secret"="*************"), |
| 177 | ("keywords"="news")); |
| 178 | </pre></div></div> |
| 179 | |
| 180 | <p>For more details about these APIs, please visit <a class="externalLink" href="https://dev.twitter.com/streaming/overview/request-parameters">https://dev.twitter.com/streaming/overview/request-parameters</a></p></div></div> |
| 181 | <div class="section"> |
| 182 | <h4><a name="Lifecycle_of_a_Feed"></a>Lifecycle of a Feed</h4> |
| 183 | <p>A feed is a logical artifact that is brought to life (i.e., its data flow is initiated) only when it is activated using the <tt>start feed</tt> statement. Before we active a feed, we need to designate the dataset where the data to be persisted using <tt>connect feed</tt> statement. Subsequent to a <tt>connect feed</tt> statement, the feed is said to be in the connected state. After that, <tt>start feed</tt> statement will activate the feed, and start the dataflow from feed to its connected dataset. Multiple feeds can simultaneously be connected to a dataset such that the contents of the dataset represent the union of the connected feeds. Also one feed can be simultaneously connected to multiple target datasets.</p> |
| 184 | |
| 185 | <div> |
| 186 | <div> |
| 187 | <pre class="source"> use dataverse feeds; |
| 188 | |
| 189 | connect feed TwitterFeed to dataset Tweets; |
| 190 | |
| 191 | start feed TwitterFeed; |
| 192 | </pre></div></div> |
| 193 | |
| 194 | <p>The <tt>connect feed</tt> statement above directs AsterixDB to persist the data from <tt>TwitterFeed</tt> feed into the <tt>Tweets</tt> dataset. The <tt>start feed</tt> statement will activate the feed and start the dataflow. If it is required (by the high-level application) to also retain the raw tweets obtained from Twitter, the end user may additionally choose to connect TwitterFeed to a different dataset.</p> |
| 195 | <p>Let the feed run for a minute, then run the following query to see the latest tweets that are stored into the data set.</p> |
| 196 | |
| 197 | <div> |
| 198 | <div> |
| 199 | <pre class="source"> use dataverse feeds; |
| 200 | |
| 201 | for $i in dataset Tweets limit 10 return $i; |
| 202 | </pre></div></div> |
| 203 | |
| 204 | <p>The dataflow of data from a feed can be terminated explicitly by <tt>stop feed</tt> statement.</p> |
| 205 | |
| 206 | <div> |
| 207 | <div> |
| 208 | <pre class="source"> use dataverse feeds; |
| 209 | |
| 210 | stop feed TwitterFeed; |
| 211 | </pre></div></div> |
| 212 | |
| 213 | <p>The <tt>disconnnect statement</tt> can be used to disconnect the feed from certain dataset.</p> |
| 214 | |
| 215 | <div> |
| 216 | <div> |
| 217 | <pre class="source"> use dataverse feeds; |
| 218 | |
| 219 | disconnect feed TwitterFeed from dataset Tweets; |
| 220 | </pre></div></div> |
| 221 | </div></div> |
| 222 | <div class="section"> |
| 223 | <h3><a name="Ingesting_with_Other_Adapters"></a>Ingesting with Other Adapters</h3> |
| 224 | <p>AsterixDB has several builtin feed adapters for data ingestion. User can also implement their own adapters and plug them into AsterixDB. Here we introduce <tt>rss_feed</tt>, <tt>socket_adapter</tt> and <tt>localfs</tt> feed adapter that cover most of the common application scenarios.</p> |
| 225 | <div class="section"> |
| 226 | <div class="section"> |
| 227 | <h5><a name="Using_the_.E2.80.9Crss_feed.E2.80.9D_feed_adapter"></a>Using the “rss_feed” feed adapter</h5> |
| 228 | <p><tt>rss_feed</tt> adapter allows retrieving data given a collection of RSS end point URLs. As observed in the case of ingesting tweets, it is required to model an RSS data item using AQL.</p> |
| 229 | |
| 230 | <div> |
| 231 | <div> |
| 232 | <pre class="source"> use dataverse feeds; |
| 233 | |
| 234 | create type Rss if not exists as open { |
| 235 | id: string, |
| 236 | title: string, |
| 237 | description: string, |
| 238 | link: string |
| 239 | }; |
| 240 | |
| 241 | create dataset RssDataset (Rss) |
| 242 | primary key id; |
| 243 | </pre></div></div> |
| 244 | |
| 245 | <p>Next, we define an RSS feed using our built-in adapter “rss_feed”.</p> |
| 246 | |
| 247 | <div> |
| 248 | <div> |
| 249 | <pre class="source"> use dataverse feeds; |
| 250 | |
| 251 | create feed my_feed using |
| 252 | rss_feed ( |
| 253 | ("type-name"="Rss"), |
| 254 | ("format"="rss"), |
| 255 | ("url"="http://rss.cnn.com/rss/edition.rss") |
| 256 | ); |
| 257 | </pre></div></div> |
| 258 | |
| 259 | <p>In the above definition, the configuration parameter “url” can be a comma-separated list that reflects a collection of RSS URLs, where each URL corresponds to an RSS endpoint or an RSS feed. The “rss_feed” retrieves data from each of the specified RSS URLs (comma separated values) in parallel.</p> |
| 260 | <p>The following statements connect the feed into the <tt>RssDataset</tt>:</p> |
| 261 | |
| 262 | <div> |
| 263 | <div> |
| 264 | <pre class="source"> use dataverse feeds; |
| 265 | |
| 266 | connect feed my_feed to dataset RssDataset; |
| 267 | </pre></div></div> |
| 268 | |
| 269 | <p>The following statements activate the feed and start the dataflow:</p> |
| 270 | |
| 271 | <div> |
| 272 | <div> |
| 273 | <pre class="source"> use dataverse feeds; |
| 274 | |
| 275 | start feed my_feed; |
| 276 | </pre></div></div> |
| 277 | |
| 278 | <p>The following statements show the latest data from the data set, stop the feed, and disconnect the feed from the data set.</p> |
| 279 | |
| 280 | <div> |
| 281 | <div> |
| 282 | <pre class="source"> use dataverse feeds; |
| 283 | |
| 284 | for $i in dataset RssDataset limit 10 return $i; |
| 285 | |
| 286 | stop feed my_feed |
| 287 | |
| 288 | disconnect feed my_feed from dataset RssDataset; |
| 289 | </pre></div></div> |
| 290 | </div> |
| 291 | <div class="section"> |
| 292 | <h5><a name="Using_the_.E2.80.9Csocket_adapter.E2.80.9D_feed_adapter"></a>Using the “socket_adapter” feed adapter</h5> |
| 293 | <p><tt>socket_adapter</tt> feed opens a web socket on the given node which allows user to push data into AsterixDB directly. Here is an example:</p> |
| 294 | |
| 295 | <div> |
| 296 | <div> |
| 297 | <pre class="source"> drop dataverse feeds if exists; |
| 298 | create dataverse feeds; |
| 299 | use dataverse feeds; |
| 300 | |
| 301 | create type TestDataType as open { |
| 302 | screenName: string |
| 303 | } |
| 304 | |
| 305 | create dataset TestDataset(TestDataType) primary key screenName; |
| 306 | |
| 307 | create feed TestSocketFeed using socket_adapter |
| 308 | ( |
| 309 | ("sockets"="127.0.0.1:10001"), |
| 310 | ("address-type"="IP"), |
| 311 | ("type-name"="TestDataType"), |
| 312 | ("format"="adm") |
| 313 | ); |
| 314 | |
| 315 | connect feed TestSocketFeed to dataset TestDataset; |
| 316 | |
| 317 | use dataverse feeds; |
| 318 | start feed TestSocketFeed; |
| 319 | </pre></div></div> |
| 320 | |
| 321 | <p>The above statements create a socket feed which is listening to “10001” port of the host machine. This feed accepts data records in “adm” format. As an example, you can download the sample dataset <a href="../data/chu.adm">Chirp Users</a> and push them line by line into the socket feed using any socket client you like. Following is a socket client example in Python:</p> |
| 322 | |
| 323 | <div> |
| 324 | <div> |
| 325 | <pre class="source"> from socket import socket |
| 326 | |
| 327 | ip = '127.0.0.1' |
| 328 | port1 = 10001 |
| 329 | filePath = 'chu.adm' |
| 330 | |
| 331 | sock1 = socket() |
| 332 | sock1.connect((ip, port1)) |
| 333 | |
| 334 | with open(filePath) as inputData: |
| 335 | for line in inputData: |
| 336 | sock1.sendall(line) |
| 337 | sock1.close() |
| 338 | </pre></div></div> |
| 339 | </div></div> |
| 340 | <div class="section"> |
| 341 | <h4><a name="Using_the_.E2.80.9Clocalfs.E2.80.9D_feed_adapter"></a>Using the “localfs” feed adapter</h4> |
| 342 | <p><tt>localfs</tt> adapter enables data ingestion from local file system. It allows user to feed data records on local disk into a dataset. A DDL example for creating a <tt>localfs</tt> feed is given as follow:</p> |
| 343 | |
| 344 | <div> |
| 345 | <div> |
| 346 | <pre class="source"> use dataverse feeds; |
| 347 | |
| 348 | create type TweetType as closed { |
| 349 | id: string, |
| 350 | username : string, |
| 351 | location : string, |
| 352 | text : string, |
| 353 | timestamp : string |
| 354 | } |
| 355 | |
| 356 | create dataset Tweets(TweetType) |
| 357 | primary key id; |
| 358 | |
| 359 | create feed TweetFeed |
| 360 | using localfs |
| 361 | (("type-name"="TweetType"),("path"="HOSTNAME://LOCAL_FILE_PATH"),("format"="adm")) |
| 362 | </pre></div></div> |
| 363 | |
| 364 | <p>Similar to previous examples, we need to define the datatype and dataset this feed uses. The “path” parameter refers to the local datafile that we want to ingest data from. <tt>HOSTNAME</tt> can either be the IP address or node name of the machine which holds the file. <tt>LOCAL_FILE_PATH</tt> indicates the absolute path to the file on that machine. Similarly to <tt>socket_adapter</tt>, this feed takes <tt>adm</tt> formatted data records.</p></div></div> |
| 365 | <div class="section"> |
| 366 | <h3><a name="Datatype_for_feed_and_target_dataset"></a>Datatype for feed and target dataset</h3> |
| 367 | <p>The “type-name” parameter in create feed statement defines the <tt>datatype</tt> of the datasource. In most use cases, feed will have the same <tt>datatype</tt> as the target dataset. However, if we want to perform certain preprocess before the data records gets into the target dataset (append autogenerated key, apply user defined functions, etc.), we will need to define the datatypes for feed and dataset separately.</p> |
| 368 | <div class="section"> |
| 369 | <h4><a name="Ingestion_with_autogenerated_key"></a>Ingestion with autogenerated key</h4> |
| 370 | <p>AsterixDB supports using autogenerated uuid as the primary key for dataset. When we use this feature, we will need to define a datatype with the primary key field, and specify that field to be autogenerated when creating the dataset. Use that same datatype in feed definition will cause a type discrepancy since there is no such field in the datasource. Thus, we will need to define two separate datatypes for feed and dataset:</p> |
| 371 | |
| 372 | <div> |
| 373 | <div> |
| 374 | <pre class="source"> use dataverse feeds; |
| 375 | |
| 376 | create type DBLPFeedType as closed { |
| 377 | dblpid: string, |
| 378 | title: string, |
| 379 | authors: string, |
| 380 | misc: string |
| 381 | } |
| 382 | |
| 383 | create type DBLPDataSetType as open { |
| 384 | id: uuid, |
| 385 | dblpid: string, |
| 386 | title: string, |
| 387 | authors: string, |
| 388 | misc: string |
| 389 | } |
| 390 | create dataset DBLPDataset(DBLPDataSetType) primary key id autogenerated; |
| 391 | |
| 392 | create feed DBLPFeed using socket_adapter |
| 393 | ( |
| 394 | ("sockets"="127.0.0.1:10001"), |
| 395 | ("address-type"="IP"), |
| 396 | ("type-name"="DBLPFeedType"), |
| 397 | ("format"="adm") |
| 398 | ); |
| 399 | |
| 400 | connect feed DBLPFeed to dataset DBLPDataset; |
| 401 | |
| 402 | start feed DBLPFeed; |
| 403 | </pre></div></div> |
| 404 | </div></div></div> |
| 405 | <div class="section"> |
| 406 | <h2><a name="Policies_for_Feed_Ingestion"></a><a name="FeedPolicies">Policies for Feed Ingestion</a></h2> |
| 407 | <p>Multiple feeds may be concurrently operational on an AsterixDB cluster, each competing for resources (CPU cycles, network bandwidth, disk IO) to maintain pace with their respective data sources. As a data management system, AsterixDB is able to manage a set of concurrent feeds and make dynamic decisions related to the allocation of resources, resolving resource bottlenecks and the handling of failures. Each feed has its own set of constraints, influenced largely by the nature of its data source and the applications that intend to consume and process the ingested data. Consider an application that intends to discover the trending topics on Twitter by analyzing tweets that are being processed. Losing a few tweets may be acceptable. In contrast, when ingesting from a data source that provides a click-stream of ad clicks, losing data would translate to a loss of revenue for an application that tracks revenue by charging advertisers per click.</p> |
| 408 | <p>AsterixDB allows a data feed to have an associated ingestion policy that is expressed as a collection of parameters and associated values. An ingestion policy dictates the runtime behavior of the feed in response to resource bottlenecks and failures. AsterixDB provides a set of policies that help customize the system’s runtime behavior when handling excess objects.</p> |
| 409 | <div class="section"> |
| 410 | <div class="section"> |
| 411 | <h4><a name="Policies"></a>Policies</h4> |
| 412 | <ul> |
| 413 | |
| 414 | <li> |
| 415 | |
| 416 | <p><i>Spill</i>: Objects that cannot be processed by an operator for lack of resources (referred to as excess objects hereafter) should be persisted to the local disk for deferred processing.</p> |
| 417 | </li> |
| 418 | <li> |
| 419 | |
| 420 | <p><i>Discard</i>: Excess objects should be discarded.</p> |
| 421 | </li> |
| 422 | </ul> |
| 423 | <p>Note that the end user may choose to form a custom policy. For example, it is possible in AsterixDB to create a custom policy that spills excess objects to disk and subsequently resorts to throttling if the spillage crosses a configured threshold. In all cases, the desired ingestion policy is specified as part of the <tt>connect feed</tt> statement or else the “Basic” policy will be chosen as the default.</p> |
| 424 | |
| 425 | <div> |
| 426 | <div> |
| 427 | <pre class="source"> use dataverse feeds; |
| 428 | |
| 429 | connect feed TwitterFeed to dataset Tweets |
| 430 | using policy Basic; |
| 431 | </pre></div></div></div></div></div> |
| 432 | </div> |
| 433 | </div> |
| 434 | </div> |
| 435 | <hr/> |
| 436 | <footer> |
| 437 | <div class="container-fluid"> |
| 438 | <div class="row-fluid"> |
| 439 | <div class="row-fluid">Apache AsterixDB, AsterixDB, Apache, the Apache |
| 440 | feather logo, and the Apache AsterixDB project logo are either |
| 441 | registered trademarks or trademarks of The Apache Software |
| 442 | Foundation in the United States and other countries. |
| 443 | All other marks mentioned may be trademarks or registered |
| 444 | trademarks of their respective owners. |
| 445 | </div> |
| 446 | </div> |
| 447 | </div> |
| 448 | </footer> |
| 449 | </body> |
| 450 | </html> |