Skip to content

TDengine
TDengine

taosdata / TDengine
1 年多 前同步成功

通知 1185
Star 22016
Fork 4786
TDengine
TDengine
切换分支/标签
查找文件 普通视图历史永久链接Permalink
index.html 8.6 KB
Newer Older
S
Added local documentation files  
StoneT2000 已提交
1 2 3 4 
<!DOCTYPE html><html lang='en'><head><title>Documentation | Taos Data</title><meta name='description' content='TDengine is an open-source big data platform for IoT. Along with a 10x faster time-series database, it provides caching, stream computing, message queuing, and other functionalities. It is designed and optimized for Internet of Things, Connected Cars, and Industrial IoT. Read the documentation for TDengine here to get started right away.'><meta name='keywords' content='TDengine, Big Data, Open Source, IoT, Connected Cars, Industrial IoT, time-series database, caching, stream computing, message queuing, IT infrastructure monitoring, application performance monitoring, Internet of Things,TAOS Data, Documentation, programming, coding, syntax, frequently asked questions, questions, faq'><meta name='title' content='Documentation | Taos Data'><meta property='og:site_name' content='Taos Data'/><meta property='og:title' content='Documentation | Taos Data'/><meta property='og:type' content='article'/><meta property='og:url' content='https://www.taosdata.com/en/documentation/advanced-features/index.php'/><meta property='og:description' content='TDengine is an open-source big data platform for IoT. Along with a 10x faster time-series database, it provides caching, stream computing, message queuing, and other functionalities. It is designed and optimized for Internet of Things, Connected Cars, and Industrial IoT. Read the documentation for TDengine here to get started right away.' /><link rel='canonical' href='https://www.taosdata.com/en/documentation/advanced-features/index.php'/><script src='../lib/jquery-3.4.1.min.js' type='application/javascript'></script><link href='../lib/bootstrap.min.css' rel='stylesheet'><link href='../styles/base.min.css' rel='stylesheet'><link rel='stylesheet' href='../lib/docs/taosdataprettify.css'><link rel='stylesheet' href='../lib/docs/docs.css'><script src='../lib/docs/prettify.js'></script><script src='../lib/docs/prettyprint-sql.js'></script></head><body><script>$('#documentation-href').addClass('active')</script><div class='container-fluid'><main class='content-wrapper'><section class='documentation'><a href='../index.html'>Back</a><h1>Advanced Features</h1>
<a class='anchor' id='Continuous-Query'></a><h2>Continuous Query</h2>
<p>Continuous Query is a query executed by TDengine periodically with a sliding window, it is a simplified stream computing driven by timers, not by events. Continuous query can be applied to a table or a STable, and the result set can be passed to the application directly via call back function, or written into a new table in TDengine. The query is always executed on a specified time window (window size is specified by parameter interval), and this window slides forward while time flows (the sliding period is specified by parameter sliding).    </p>
<p>Continuous query is defined by TAOS SQL, there is nothing special. One of the best applications is downsampling. Once it is defined, at the end of each cycle, the system will execute the query, pass the result to the application or write it to a database. </p>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
5 
<p>If historical data pints are inserted into the stream, the query won't be re-executed, and the result set won't be updated. If the result set is passed to the application, the application needs to keep the status of continuous query, the server won't maintain it. If application re-starts, it needs to decide the time where the stream computing shall be started.</p>
S
Added local documentation files  
StoneT2000 已提交
6 7 8 9 
<h4>How to use continuous query</h4>
<ul>
<li><p>Pass result set to application</p>
<p>Application shall use API taos_stream (details in connector section) to start the stream computing. Inside the API, the SQL syntax is:</p>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
10 
<pre><code class="sql language-sql">SELECT aggregation FROM [table_name | stable_name]
S
Added local documentation files  
StoneT2000 已提交
11 12 13 
INTERVAL(window_size) SLIDING(period)</code></pre>
<p>where the new keyword INTERVAL specifies the window size, and SLIDING specifies the sliding period. If parameter sliding is not specified, the sliding period will be the same as window size. The minimum window size is 10ms. The sliding period shall not be larger than the window size. If you set a value larger than the window size, the system will adjust it to window size automatically.</p>
<p>For example:</p>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
14 
<pre><code class="sql language-sql">SELECT COUNT(*) FROM FOO_TABLE
S
Added local documentation files  
StoneT2000 已提交
15 
INTERVAL(1M) SLIDING(30S)</code></pre>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
16 
<p>The above SQL statement will count the number of records for the past 1-minute window every 30 seconds.</p></li>
S
Added local documentation files  
StoneT2000 已提交
17 18 
<li><p>Save the result into a database</p>
<p>If you want to save the result set of stream computing into a new table, the SQL shall be: </p>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
19 
<pre><code class="sql language-sql">CREATE TABLE table_name AS
S
Added local documentation files  
StoneT2000 已提交
20 21 22 
SELECT aggregation from [table_name | stable_name]  
INTERVAL(window_size) SLIDING(period)</code></pre>
<p>Also, you can set the time range to execute the continuous query. If no range is specified, the continuous query will be executed forever. For example, the following continuous query will be executed from now and will stop in one hour.</p>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
23 
<pre><code class="sql language-sql">CREATE TABLE QUERY_RES AS
S
Added local documentation files  
StoneT2000 已提交
24 25 
SELECT COUNT(*) FROM FOO_TABLE 
WHERE TS &gt; NOW AND TS &lt;= NOW + 1H
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
26 
INTERVAL(1M) SLIDING(30S) </code></pre></li>
S
Added local documentation files  
StoneT2000 已提交
27 28 
</ul>
<a class='anchor' id='Manage-the-Continuous-Query'></a><h3>Manage the Continuous Query</h3>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
29 
<p>Inside TDengine shell, you can use the command "show streams" to list the ongoing continuous queries, the command "kill stream" to kill a specific continuous query. </p>
S
Added local documentation files  
StoneT2000 已提交
30 31 
<p>If you drop a table generated by the continuous query, the query will be removed too.</p>
<a class='anchor' id='Publisher/Subscriber'></a><h2>Publisher/Subscriber</h2>
U
Fix typo DTengine => TDengine  
universeroc 已提交
32 
<p>Time series data is a sequence of data points over time. Inside a table, the data points are stored in order of timestamp. Also, there is a data retention policy, the data points will be removed once their lifetime is passed. From another view, a table in TDengine is just a standard message queue. </p>
S
Added local documentation files  
StoneT2000 已提交
33 
<p>To reduce the development complexity and improve data consistency, TDengine provides the pub/sub functionality. To publish a message, you simply insert a record into a table. Compared with popular messaging tool Kafka, you subscribe to a table or a SQL query statement, instead of a topic. Once new data points arrive, TDengine will notify the application. The process is just like Kafka.  </p>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
34 
<p>The detailed API will be introduced in the <a href="https://www.taosdata.com/en/documentation/advanced-features/">connectors</a> section. </p>
S
Added local documentation files  
StoneT2000 已提交
35 36 37 
<a class='anchor' id='Caching'></a><h2>Caching</h2>
<p>TDengine allocates a fixed-size buffer in memory, the newly arrived data will be written into the buffer first. Every device or table gets one or more memory blocks. For typical IoT scenarios, the hot data shall always be newly arrived data, they are more important for timely analysis. Based on this observation, TDengine manages the cache blocks in First-In-First-Out strategy. If no enough space in the buffer, the oldest data will be saved into hard disk first, then be overwritten by newly arrived data. TDengine also guarantees every device can keep at least one block of data in the buffer. </p>
<p>By this design, the application can retrieve the latest data from each device super-fast, since they are all available in memory. You can use last or last_row function to return the last data record. If the super table is used, it can be used to return the last data records of all or a subset of devices. For example, to retrieve the latest temperature from thermometers in located Beijing, execute the following SQL  </p>
S
Docs Update; Completed async functionality for Node.js connector, updated to 1.2.0  
StoneT2000 已提交
38 
<pre><code class="mysql language-mysql">select last(*) from thermometers where location=’beijing’</code></pre>
S
Added local documentation files  
StoneT2000 已提交
39 40 
<p>By this design, caching tool, like Redis, is not needed in the system. It will reduce the complexity of the system. </p>
<p>TDengine creates one or more virtual nodes(vnode) in each data node. Each vnode contains data for multiple tables and has its own buffer. The buffer of a vnode is fully separated from the buffer of another vnode, not shared. But the tables in a vnode share the same buffer.  </p>
U
Fix typo DTengine => TDengine  
universeroc 已提交
41 
<p>System configuration parameter cacheBlockSize configures the cache block size in bytes, and another parameter cacheNumOfBlocks configures the number of cache blocks. The total memory for the buffer of a vnode is $cacheBlockSize \times cacheNumOfBlocks$. Another system parameter numOfBlocksPerMeter configures the maximum number of cache blocks a table can use. When you create a database, you can specify these parameters. </p><a href='../index.html'>Back</a></section></main></div><?php include($s.'/footer.php'); ?><script>$('pre').addClass('prettyprint linenums');PR.prettyPrint()</script><script src='lib/docs/liner.js'></script></body></html>