Skip to content

T
TDengine

taosdata / TDengine
大约 2 年 前同步成功

通知 1192
Star 22018
Fork 4786
T
TDengine
提交 a171c0c8 编写于 作者: K kailixu
浏览文件
操作

Merge branch '3.0' into fix/TD-21457-3.0

上级 a3bf49d2 0bb468af
显示空白变更内容
内联 并排
Showing with 651 addition and 584 deletion
docs/en/13-operation/10-monitor.md
浏览文件 @ a171c0c8
......@@ -36,7 +36,7 @@ You can use below command to setup Grafana alert notification.
An existing Grafana Notification Channel can be specified with parameter `-E`, the notifier uid of the channel can be obtained by `curl -u admin:admin localhost:3000/api/alert-notifications |jq`
```bash
sudo ./TDinsight.sh -a http://localhost:6041 -u root -p taosdata -E <notifier uid>
./TDinsight.sh -a http://localhost:6041 -u root -p taosdata -E <notifier uid>
```
Launch `TDinsight.sh` with the command above and restart Grafana, then open Dashboard `http://localhost:3000/d/tdinsight`.
......@@ -274,7 +274,7 @@ The data of tdinsight dashboard is stored in `log` database (default. You can ch
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||metric value|
|gauge|DOUBLE||metric value|
|client\_ip|NCHAR|TAG|client ip|
|endpoint|NCHAR|TAG|taosadpater endpoint|
|request\_method|NCHAR|TAG|request method|
......@@ -288,7 +288,7 @@ The data of tdinsight dashboard is stored in `log` database (default. You can ch
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||metric value|
|gauge|DOUBLE||metric value|
|client\_ip|NCHAR|TAG|client ip|
|endpoint|NCHAR|TAG|taosadpater endpoint|
|request\_method|NCHAR|TAG|request method|
......@@ -302,7 +302,7 @@ The data of tdinsight dashboard is stored in `log` database (default. You can ch
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||metric value|
|gauge|DOUBLE||metric value|
|endpoint|NCHAR|TAG|taosadpater endpoint|
### taosadapter\_restful\_http\_request\_summary\_milliseconds table
......@@ -330,7 +330,7 @@ The data of tdinsight dashboard is stored in `log` database (default. You can ch
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||metric value|
|gauge|DOUBLE||metric value|
|endpoint|NCHAR|TAG|taosadpater endpoint|
### taosadapter\_system\_cpu\_percent table
......@@ -340,6 +340,6 @@ The data of tdinsight dashboard is stored in `log` database (default. You can ch
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||mertic value|
|gauge|DOUBLE||mertic value|
|endpoint|NCHAR|TAG|taosadpater endpoint|
docs/en/14-reference/07-tdinsight/index.md
浏览文件 @ a171c0c8
......@@ -149,7 +149,7 @@ curl --no-progress-meter -u admin:admin http://localhost:3000/api/alert-notifica
Use the `uid` value obtained above as `-E` input.
```bash
sudo ./TDinsight.sh -a http://tdengine:6041 -u root1 -p pass5ord -E existing-notifier
./TDinsight.sh -a http://tdengine:6041 -u root1 -p pass5ord -E existing-notifier
```
If you want to monitor multiple TDengine clusters, you need to set up numerous TDinsight dashboards. Setting up non-default TDinsight requires some changes: the `-n` `-i` `-t` options need to be changed to non-default names, and `-N` and `-L` should also be changed if using the built-in SMS alerting feature.
......
docs/en/14-reference/12-config/index.md
浏览文件 @ a171c0c8
......@@ -46,7 +46,7 @@ The parameters described in this document by the effect that they have on the sy
### firstEp
| Attribute | Description |
| -------- | -------------------------------------------------------------- |
| ---------- | ---------------------------------------------------------------------------------------------------- |
| Applicable | Server and Client |
| Meaning | The end point of the first dnode in the cluster to be connected to when `taosd` or `taos` is started |
| Default | localhost:6030 |
......@@ -54,7 +54,7 @@ The parameters described in this document by the effect that they have on the sy
### secondEp
| Attribute | Description |
| -------- | ------------------------------------------------------------------------------------- |
| ---------- | ---------------------------------------------------------------------------------------------------------------------- |
| Applicable | Server and Client |
| Meaning | The end point of the second dnode to be connected to if the firstEp is not available when `taosd` or `taos` is started |
| Default | None |
......@@ -71,7 +71,7 @@ The parameters described in this document by the effect that they have on the sy
### serverPort
| Attribute | Description |
| -------- | ----------------------------------------------------------------------------------------------------------------------- |
| ------------- | ----------------------------------------------------- |
| Applicable | Server Only |
| Meaning | The port for external access after `taosd` is started |
| Default Value | 6030 |
......@@ -80,12 +80,12 @@ The parameters described in this document by the effect that they have on the sy
- Ensure that your firewall rules do not block TCP port 6042 on any host in the cluster. Below table describes the ports used by TDengine in details.
:::
| Protocol | Default Port | Description | How to configure |
| :------- | :----------- | :----------------------------------------------- | :--------------------------------------------------------------------------------------------- |
| :------- | :----------- | :-------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------- |
| TCP | 6030 | Communication between client and server. In a multi-node cluster, communication between nodes. serverPort |
| TCP | 6041 | REST connection between client and server | Prior to 2.4.0.0: serverPort+11; After 2.4.0.0 refer to [taosAdapter](/reference/taosadapter/) |
| TCP | 6043 | Service Port of taosKeeper | The parameter of taosKeeper |
| TCP | 6044 | Data access port for StatsD | Configurable through taosAdapter parameters.
| UDP | 6045 | Data access for statsd | Configurable through taosAdapter parameters.
| TCP | 6044 | Data access port for StatsD | Configurable through taosAdapter parameters. |
| UDP | 6045 | Data access for statsd | Configurable through taosAdapter parameters. |
| TCP | 6060 | Port of Monitoring Service in Enterprise version | |
### maxShellConns
......@@ -97,6 +97,24 @@ The parameters described in this document by the effect that they have on the sy
| Value Range | 10-50000000 |
| Default Value | 5000 |
### numOfRpcSessions
| Attribute | Description |
| ------------- | ------------------------------------------ |
| Applicable | Client/Server |
| Meaning | The maximum number of connection to create |
| Value Range | 100-100000 |
| Default Value | 10000 |
### timeToGetAvailableConn
| Attribute | Description |
| ------------- | ---------------------------------------------- |
| Applicable | Client/Server |
| Meaning | The maximum waiting time to get avaliable conn |
| Value Range | 10-50000000(ms) |
| Default Value | 500000 |
## Monitoring Parameters
:::note
......@@ -105,16 +123,16 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### monitor
| Attribute | Description |
| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Applicable | Server only |
| Meaning | The switch for monitoring inside server. The main object of monitoring is to collect information about load on physical nodes, including CPU usage, memory usage, disk usage, and network bandwidth. Monitoring information is sent over HTTP to the taosKeeper service specified by `monitorFqdn` and `monitorProt`.
| Meaning | The switch for monitoring inside server. The main object of monitoring is to collect information about load on physical nodes, including CPU usage, memory usage, disk usage, and network bandwidth. Monitoring information is sent over HTTP to the taosKeeper service specified by `monitorFqdn` and `monitorProt`. |
| Value Range | 0: monitoring disabled, 1: monitoring enabled |
| Default | 0 |
### monitorFqdn
| Attribute | Description |
| -------- | -------------------------- |
| ---------- | ------------------------------------- |
| Applicable | Server Only |
| Meaning | FQDN of taosKeeper monitoring service |
| Default | None |
......@@ -122,7 +140,7 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### monitorPort
| Attribute | Description |
| -------- | --------------------------- |
| ------------- | ------------------------------------- |
| Applicable | Server Only |
| Meaning | Port of taosKeeper monitoring service |
| Default Value | 6043 |
......@@ -130,7 +148,7 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### monitorInterval
| Attribute | Description |
| -------- | -------------------------------------------- |
| ------------- | ------------------------------------------ |
| Applicable | Server Only |
| Meaning | The interval of collecting system workload |
| Unit | second |
......@@ -140,7 +158,7 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### telemetryReporting
| Attribute | Description |
| -------- | ---------------------------------------- |
| ------------- | ---------------------------------------------------------------------------- |
| Applicable | Server Only |
| Meaning | Switch for allowing TDengine to collect and report service usage information |
| Value Range | 0: Not allowed; 1: Allowed |
......@@ -148,9 +166,9 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### crashReporting
| Attribute | Description |
| -------- | -------------------------------------------- |
| ------------- | ---------------------------------------------------------------------------- |
| Applicable | Server Only |
| Meaning |Switch for allowing TDengine to collect and report crash related information |
| Meaning | Switch for allowing TDengine to collect and report crash related information |
| Value Range | 0,1 0: Not allowed; 1: allowed |
| Default Value | 1 |
......@@ -160,7 +178,7 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### queryPolicy
| Attribute | Description |
| -------- | ----------------------------- |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Applicable | Client only |
| Meaning | Execution policy for query statements |
| Unit | None |
......@@ -170,17 +188,17 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### querySmaOptimize
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Applicable | Client only |
| Meaning | SMA index optimization policy |
| Unit | None |
| Default Value | 0 |
| Notes |0: Disable SMA indexing and perform all queries on non-indexed data; 1: Enable SMA indexing and perform queries from suitable statements on precomputation results.|
| Notes | 0: Disable SMA indexing and perform all queries on non-indexed data; 1: Enable SMA indexing and perform queries from suitable statements on precomputation results. |
### countAlwaysReturnValue
| Attribute | Description |
| -------- | -------------------------------- |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Applicable | Server only |
| Meaning | count()/hyperloglog() return value or not if the input data is empty or NULL |
| Vlue Range | 0: Return empty line, 1: Return 0 |
......@@ -190,7 +208,7 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### maxNumOfDistinctRes
| Attribute | Description |
| -------- | -------------------------------- |
| ------------- | -------------------------------------------- |
| Applicable | Server Only |
| Meaning | The maximum number of distinct rows returned |
| Value Range | [100,000 - 100,000,000] |
......@@ -199,7 +217,7 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### keepColumnName
| Attribute | Description |
| -------- | -------------------------------- |
| ------------- | --------------------------------------------------------------------------------------------------------------- |
| Applicable | Client only |
| Meaning | When the Last, First, LastRow function is queried, whether the returned column name contains the function name. |
| Value Range | 0 means including the function name, 1 means not including the function name. |
......@@ -210,7 +228,7 @@ Please note the `taoskeeper` needs to be installed and running to create the `lo
### timezone
| Attribute | Description |
| -------- | ------------------------------ |
| ------------- | ------------------------------- |
| Applicable | Server and Client |
| Meaning | TimeZone |
| Default Value | TimeZone configured in the host |
......@@ -315,7 +333,7 @@ The charset that takes effect is UTF-8.
### dataDir
| Attribute | Description |
| -------- | ------------------------------------------ |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Applicable | Server Only |
| Meaning | All data files are stored in this directory |
| Default Value | /var/lib/taos |
......@@ -324,7 +342,7 @@ The charset that takes effect is UTF-8.
### tempDir
| Attribute | Description |
| -------- | ------------------------------------------ |
| ---------- | ---------------------------------------------------------------------------------- |
| Applicable | Server only |
| Meaning | The directory where to put all the temporary files generated during system running |
| Default | /tmp |
......@@ -332,7 +350,7 @@ The charset that takes effect is UTF-8.
### minimalTmpDirGB
| Attribute | Description |
| -------- | ------------------------------------------------ |
| ------------- | ----------------------------------------------------------------------------------------------- |
| Applicable | Server and Client |
| Meaning | When the available disk space in tmpDir is below this threshold, writing to tmpDir is suspended |
| Unit | GB |
......@@ -341,7 +359,7 @@ The charset that takes effect is UTF-8.
### minimalDataDirGB
| Attribute | Description |
| -------- | ------------------------------------------------ |
| ------------- | ------------------------------------------------------------------------------------------------- |
| Applicable | Server Only |
| Meaning | When the available disk space in dataDir is below this threshold, writing to dataDir is suspended |
| Unit | GB |
......@@ -352,7 +370,7 @@ The charset that takes effect is UTF-8.
### supportVnodes
| Attribute | Description |
| -------- | --------------------------- |
| ------------- | ---------------------------------- |
| Applicable | Server Only |
| Meaning | Maximum number of vnodes per dnode |
| Value Range | 0-4096 |
......@@ -374,7 +392,7 @@ The charset that takes effect is UTF-8.
### logDir
| Attribute | Description |
| -------- | -------------------------------------------------- |
| ------------- | ----------------------------------- |
| Applicable | Server and Client |
| Meaning | The directory for writing log files |
| Default Value | /var/log/taos |
......@@ -382,7 +400,7 @@ The charset that takes effect is UTF-8.
### minimalLogDirGB
| Attribute | Description |
| -------- | -------------------------------------------- |
| ------------- | -------------------------------------------------------------------------------------------------- |
| Applicable | Server and Client |
| Meaning | When the available disk space in logDir is below this threshold, writing to log files is suspended |
| Unit | GB |
......@@ -391,7 +409,7 @@ The charset that takes effect is UTF-8.
### numOfLogLines
| Attribute | Description |
| -------- | ---------------------------- |
| ------------- | ------------------------------------------ |
| Applicable | Server and Client |
| Meaning | Maximum number of lines in single log file |
| Default Value | 10000000 |
......@@ -399,7 +417,7 @@ The charset that takes effect is UTF-8.
### asyncLog
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ---------------------------- |
| Applicable | Server and Client |
| Meaning | The mode of writing log file |
| Value Range | 0: sync way; 1: async way |
......@@ -408,7 +426,7 @@ The charset that takes effect is UTF-8.
### logKeepDays
| Attribute | Description |
| -------- | ----------------------------------------------------------------------------------- |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Applicable | Server and Client |
| Meaning | The number of days for log files to be kept |
| Unit | day |
......@@ -418,7 +436,7 @@ The charset that takes effect is UTF-8.
### debugFlag
| Attribute | Description |
| -------- | ------------------------------------------------------------------------------------------------- |
| ------------- | --------------------------------------------------------- |
| Applicable | Server and Client |
| Meaning | Log level |
| Value Range | 131: INFO/WARNING/ERROR; 135: plus DEBUG; 143: plus TRACE |
......@@ -427,7 +445,7 @@ The charset that takes effect is UTF-8.
### tmrDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------------- |
| Applicable | Server and Client |
| Meaning | Log level of timer module |
| Value Range | same as debugFlag |
......@@ -436,7 +454,7 @@ The charset that takes effect is UTF-8.
### uDebugFlag
| Attribute | Description |
| -------- | ---------------------- |
| ------------- | -------------------------- |
| Applicable | Server and Client |
| Meaning | Log level of common module |
| Value Range | same as debugFlag |
......@@ -445,7 +463,7 @@ The charset that takes effect is UTF-8.
### rpcDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ----------------------- |
| Applicable | Server and Client |
| Meaning | Log level of rpc module |
| Value Range | same as debugFlag |
......@@ -454,7 +472,7 @@ The charset that takes effect is UTF-8.
### jniDebugFlag
| Attribute | Description |
| -------- | ------------------ |
| ------------- | ----------------------- |
| Applicable | Client Only |
| Meaning | Log level of jni module |
| Value Range | same as debugFlag |
......@@ -463,7 +481,7 @@ The charset that takes effect is UTF-8.
### qDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------------- |
| Applicable | Server and Client |
| Meaning | Log level of query module |
| Value Range | same as debugFlag |
......@@ -472,7 +490,7 @@ The charset that takes effect is UTF-8.
### cDebugFlag
| Attribute | Description |
| -------- | --------------------- |
| ------------- | ------------------- |
| Applicable | Client Only |
| Meaning | Log level of Client |
| Value Range | same as debugFlag |
......@@ -481,7 +499,7 @@ The charset that takes effect is UTF-8.
### dDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------ |
| Applicable | Server Only |
| Meaning | Log level of dnode |
| Value Range | same as debugFlag |
......@@ -490,7 +508,7 @@ The charset that takes effect is UTF-8.
### vDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------ |
| Applicable | Server Only |
| Meaning | Log level of vnode |
| Value Range | same as debugFlag |
......@@ -499,7 +517,7 @@ The charset that takes effect is UTF-8.
### mDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------------- |
| Applicable | Server Only |
| Meaning | Log level of mnode module |
| Value Range | same as debugFlag |
......@@ -508,7 +526,7 @@ The charset that takes effect is UTF-8.
### wDebugFlag
| Attribute | Description |
| -------- | ------------------ |
| ------------- | ----------------------- |
| Applicable | Server Only |
| Meaning | Log level of WAL module |
| Value Range | same as debugFlag |
......@@ -517,7 +535,7 @@ The charset that takes effect is UTF-8.
### sDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------------ |
| Applicable | Server and Client |
| Meaning | Log level of sync module |
| Value Range | same as debugFlag |
......@@ -526,7 +544,7 @@ The charset that takes effect is UTF-8.
### tsdbDebugFlag
| Attribute | Description |
| -------- | ------------------- |
| ------------- | ------------------------ |
| Applicable | Server Only |
| Meaning | Log level of TSDB module |
| Value Range | same as debugFlag |
......@@ -535,7 +553,7 @@ The charset that takes effect is UTF-8.
### tqDebugFlag
| Attribute | Description |
| -------- | ----------------- |
| ------------- | ---------------------- |
| Applicable | Server only |
| Meaning | Log level of TQ module |
| Value Range | same as debugFlag |
......@@ -544,7 +562,7 @@ The charset that takes effect is UTF-8.
### fsDebugFlag
| Attribute | Description |
| -------- | ----------------- |
| ------------- | ---------------------- |
| Applicable | Server only |
| Meaning | Log level of FS module |
| Value Range | same as debugFlag |
......@@ -553,7 +571,7 @@ The charset that takes effect is UTF-8.
### udfDebugFlag
| Attribute | Description |
| -------- | ------------------ |
| ------------- | ----------------------- |
| Applicable | Server Only |
| Meaning | Log level of UDF module |
| Value Range | same as debugFlag |
......@@ -562,7 +580,7 @@ The charset that takes effect is UTF-8.
### smaDebugFlag
| Attribute | Description |
| -------- | ------------------ |
| ------------- | ----------------------- |
| Applicable | Server Only |
| Meaning | Log level of SMA module |
| Value Range | same as debugFlag |
......@@ -571,7 +589,7 @@ The charset that takes effect is UTF-8.
### idxDebugFlag
| Attribute | Description |
| -------- | -------------------- |
| ------------- | ------------------------- |
| Applicable | Server Only |
| Meaning | Log level of index module |
| Value Range | same as debugFlag |
......@@ -580,7 +598,7 @@ The charset that takes effect is UTF-8.
### tdbDebugFlag
| Attribute | Description |
| -------- | ------------------ |
| ------------- | ----------------------- |
| Applicable | Server Only |
| Meaning | Log level of TDB module |
| Value Range | same as debugFlag |
......@@ -591,7 +609,7 @@ The charset that takes effect is UTF-8.
### smlChildTableName
| Attribute | Description |
| -------- | ------------------------- |
| ------------- | ------------------------------------------ |
| Applicable | Client only |
| Meaning | Custom subtable name for schemaless writes |
| Type | String |
......@@ -600,7 +618,7 @@ The charset that takes effect is UTF-8.
### smlTagName
| Attribute | Description |
| -------- | ------------------------------------ |
| ------------- | ------------------------------------------------------------- |
| Applicable | Client only |
| Meaning | Default tag for schemaless writes without tag value specified |
| Type | String |
......@@ -609,9 +627,9 @@ The charset that takes effect is UTF-8.
### smlDataFormat
| Attribute | Description |
| -------- | ----------------------------- |
| ----------- | ----------------------------------------------------------------------------------- |
| Applicable | Client only |
| Meaning | Whether schemaless columns are consistently ordered, depat, discarded since 3.0.3.0|
| Meaning | Whether schemaless columns are consistently ordered, depat, discarded since 3.0.3.0 |
| Value Range | 0: not consistent; 1: consistent. |
| Default | 0 |
......@@ -620,7 +638,7 @@ The charset that takes effect is UTF-8.
### compressMsgSize
| Attribute | Description |
| -------- | ----------------------------- |
| ----------- | ------------------------------------------------------------------------------------------------------------------ |
| Applicable | Both Client and Server side |
| Meaning | Whether RPC message is compressed |
| Value Range | -1: none message is compressed; 0: all messages are compressed; N (N>0): messages exceeding N bytes are compressed |
......@@ -632,7 +650,7 @@ The charset that takes effect is UTF-8.
### enableCoreFile
| Attribute | Description |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Applicable | Server and Client |
| Meaning | Whether to generate core file when server crashes |
| Value Range | 0: false, 1: true |
......@@ -642,7 +660,7 @@ The charset that takes effect is UTF-8.
### enableScience
| Attribute | Description |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| ------------- | ------------------------------------------------------------- |
| Applicable | Only taos-CLI client |
| Meaning | Whether to show float and double with the scientific notation |
| Value Range | 0: false, 1: true |
......@@ -652,7 +670,7 @@ The charset that takes effect is UTF-8.
### udf
| Attribute | Description |
| -------- | ------------------ |
| ------------- | ---------------------------------- |
| Applicable | Server Only |
| Meaning | Whether the UDF service is enabled |
| Value Range | 0: disable UDF; 1: enabled UDF |
......@@ -662,7 +680,7 @@ The charset that takes effect is UTF-8.
## 3.0 Parameters
| # | **Parameter** | **Applicable to 2.x ** | **Applicable to 3.0 ** | Current behavior in 3.0 |
| --- | :---------------------: | --------------- | --------------- | ------------------------------------------------- |
| --- | :--------------------: | ---------------------- | ---------------------------- | ----------------------- |
| 1 | firstEp | Yes | Yes | |
| 2 | secondEp | Yes | Yes | |
| 3 | fqdn | Yes | Yes | |
......
docs/zh/14-reference/07-tdinsight/index.mdx
浏览文件 @ a171c0c8
......@@ -177,7 +177,7 @@ Install and configure TDinsight dashboard in Grafana on Ubuntu 18.04/20.04 syste
假设您在主机 `tdengine` 上启动 TDengine 数据库，HTTP API 端口为 `6041`，用户为 `root1`，密码为 `pass5ord`。执行脚本：
```bash
sudo ./TDinsight.sh -a http://tdengine:6041 -u root1 -p pass5ord
./TDinsight.sh -a http://tdengine:6041 -u root1 -p pass5ord
```
我们提供了一个“-E”选项，用于从命令行配置 TDinsight 使用现有的通知通道(Notification Channel)。假设你的 Grafana 用户和密码是 `admin:admin`，使用以下命令获取已有的通知通道的`uid`：
......@@ -189,7 +189,7 @@ curl --no-progress-meter -u admin:admin http://localhost:3000/api/alert-notifica
使用上面获取的 `uid` 值作为 `-E` 输入。
```bash
sudo ./TDinsight.sh -a http://tdengine:6041 -u root1 -p pass5ord -E existing-notifier
./TDinsight.sh -a http://tdengine:6041 -u root1 -p pass5ord -E existing-notifier
```
如果要监控多个 TDengine 集群，则需要设置多个 TDinsight 仪表盘。设置非默认 TDinsight 需要进行一些更改： `-n` `-i` `-t` 选项需要更改为非默认名称，如果使用 内置短信告警功能，`-N` 和 `-L` 也应该改变。
......
docs/zh/14-reference/12-config/index.md
浏览文件 @ a171c0c8
......@@ -80,11 +80,11 @@ taos --dump-config
确保集群中所有主机在端口 6030 上的 TCP 协议能够互通。（详细的端口情况请参见下表）
:::
| 协议 | 默认端口 | 用途说明 | 修改方法 |
| :--- | :-------- | :---------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------- |
| :--- | :------- | :----------------------------------------------- | :------------------------------------------------------------------------------------------------- |
| TCP | 6030 | 客户端与服务端之间通讯，多节点集群的节点间通讯。 | 由配置文件设置 serverPort 决定。 |
| TCP | 6041 | 客户端与服务端之间的 RESTful 通讯。 | 随 serverPort 端口变化。注意 taosAdapter 配置或有不同，请参考相应[文档](/reference/taosadapter/)。 |
| TCP | 6043 | taosKeeper 监控服务端口。 | 随 taosKeeper 启动参数设置变化。 |
| TCP | 6044 | 支持 StatsD 的数据接入端口。 | 随 taosAdapter 启动参数设置变化|
| TCP | 6044 | 支持 StatsD 的数据接入端口。 | 随 taosAdapter 启动参数设置变化 |
| UDP | 6045 | 支持 collectd 数据接入端口。 | 随 taosAdapter 启动参数设置变化 |
| TCP | 6060 | 企业版内 Monitor 服务的网络端口。 | |
......@@ -97,6 +97,24 @@ taos --dump-config
| 取值范围 | 10-50000000 |
| 缺省值 | 5000 |
### numOfRpcSessions
| 属性 | 说明 |
| -------- | ---------------------------- |
| 适用范围 | 客户端和服务端都适用 |
| 含义 | 一个客户端能创建的最大连接数 |
| 取值范围 | 100-100000 |
| 缺省值 | 10000 |
### timeToGetAvailableConn
| 属性 | 说明 |
| -------- | -------------------------- |
| 适用范围 | 客户端和服务端都适用 |
| 含义 | 获得可用连接的最长等待时间 |
| 取值范围 | 10-50000000(单位为毫秒) |
| 缺省值 | 500000 |
## 监控相关
:::note
......@@ -140,18 +158,18 @@ taos --dump-config
### telemetryReporting
| 属性 | 说明 |
| -------- | -------------------------------------------- |
| -------- | ------------------------ |
| 适用范围 | 仅服务端适用 |
| 含义 |是否上传 telemetry |
| 含义 | 是否上传 telemetry |
| 取值范围 | 0,1 0: 不上传；1：上传 |
| 缺省值 | 1 |
### crashReporting
| 属性 | 说明 |
| -------- | -------------------------------------------- |
| -------- | ------------------------ |
| 适用范围 | 仅服务端适用 |
| 含义 |是否上传 crash 信息 |
| 含义 | 是否上传 crash 信息 |
| 取值范围 | 0,1 0: 不上传；1：上传 |
| 缺省值 | 1 |
......@@ -160,7 +178,7 @@ taos --dump-config
### queryPolicy
| 属性 | 说明 |
| -------- | ----------------------------- |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 适用范围 | 仅客户端适用 |
| 含义 | 查询语句的执行策略 |
| 单位 | 无 |
......@@ -170,12 +188,12 @@ taos --dump-config
### querySmaOptimize
| 属性 | 说明 |
| -------- | -------------------- |
| -------- | ---------------------------------------------------------------------------------------------------------------- |
| 适用范围 | 仅客户端适用 |
| 含义 | sma index 的优化策略 |
| 单位 | 无 |
| 缺省值 | 0 |
| 补充说明 |0: 表示不使用 sma index，永远从原始数据进行查询; 1: 表示使用 sma index，对符合的语句，直接从预计算的结果进行查询 |
| 补充说明 | 0: 表示不使用 sma index，永远从原始数据进行查询; 1: 表示使用 sma index，对符合的语句，直接从预计算的结果进行查询 |
### maxNumOfDistinctRes
......@@ -189,7 +207,7 @@ taos --dump-config
### keepColumnName
| 属性 | 说明 |
| -------- | -------------------------------- |
| -------- | ----------------------------------------------------------- |
| 适用范围 | 仅客户端适用 |
| 含义 | Last、First、LastRow 函数查询时，返回的列名是否包含函数名。 |
| 取值范围 | 0 表示包含函数名，1 表示不包含函数名。 |
......@@ -198,7 +216,7 @@ taos --dump-config
### countAlwaysReturnValue
| 属性 | 说明 |
| -------- | -------------------------------- |
| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| 适用范围 | 仅服务端适用 |
| 含义 | count/hyperloglog函数在输入数据为空或者NULL的情况下是否返回值 |
| 取值范围 | 0：返回空行，1：返回 0 |
......@@ -315,7 +333,7 @@ charset 的有效值是 UTF-8。
### dataDir
| 属性 | 说明 |
| -------- | ------------------------------------------ |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 适用范围 | 仅服务端适用 |
| 含义 | 数据文件目录，所有的数据文件都将写入该目录 |
| 缺省值 | /var/lib/taos |
......@@ -324,7 +342,7 @@ charset 的有效值是 UTF-8。
### tempDir
| 属性 | 说明 |
| -------- | ------------------------------------------ |
| -------- | ------------------------------------------------ |
| 适用范围 | 仅服务端适用 |
| 含义 | 该参数指定所有系统运行过程中的临时文件生成的目录 |
| 缺省值 | /tmp |
......@@ -341,7 +359,7 @@ charset 的有效值是 UTF-8。
### minimalDataDirGB
| 属性 | 说明 |
| -------- | ------------------------------------------------ |
| -------- | ---------------------------------------------- |
| 适用范围 | 仅服务端适用 |
| 含义 | dataDir 指定的时序数据存储目录所需要保留的最小 |
| 单位 | GB |
......@@ -382,7 +400,7 @@ charset 的有效值是 UTF-8。
### minimalLogDirGB
| 属性 | 说明 |
| -------- | -------------------------------------------- |
| -------- | ------------------------------------------------------ |
| 适用范围 | 服务端和客户端均适用 |
| 含义 | 当日志文件夹所在磁盘可用空间大小小于该值时，停止写日志 |
| 单位 | GB |
......@@ -591,7 +609,7 @@ charset 的有效值是 UTF-8。
### smlChildTableName
| 属性 | 说明 |
| -------- | ------------------------- |
| -------- | ------------------------------- |
| 适用范围 | 仅客户端适用 |
| 含义 | schemaless 自定义的子表名的 key |
| 类型 | 字符串 |
......@@ -609,7 +627,7 @@ charset 的有效值是 UTF-8。
### smlDataFormat
| 属性 | 说明 |
| -------- | ----------------------------- |
| -------- | -------------------------------------------------------- |
| 适用范围 | 仅客户端适用 |
| 含义 | schemaless 列数据是否顺序一致，从3.0.3.0开始，该配置废弃 |
| 值域 | 0：不一致；1: 一致 |
......@@ -630,7 +648,7 @@ charset 的有效值是 UTF-8。
### enableScience
| 属性 | 说明 |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| -------- | ---------------------------- |
| 适用范围 | 仅客户端 TAOS-CLI 适用 |
| 含义 | 是否开启科学计数法显示浮点数 |
| 取值范围 | 0：否，1：是 |
......@@ -650,7 +668,7 @@ charset 的有效值是 UTF-8。
### compressMsgSize
| 属性 | 说明 |
| -------- | ----------------------------- |
| -------- | ------------------------------------------------------------------------------- |
| 适用于 | 服务端和客户端均适用 |
| 含义 | 是否对 RPC 消息进行压缩 |
| 取值范围 | -1: 所有消息都不压缩; 0: 所有消息都压缩; N (N>0): 只有大于 N 个字节的消息才压缩 |
......@@ -659,7 +677,7 @@ charset 的有效值是 UTF-8。
## 3.0 中有效的配置参数列表
| # | **参数** | **适用于 2.X ** | **适用于 3.0 ** | 3.0 版本的当前行为 |
| --- | :---------------------: | --------------- | --------------- | ------------------------------------------------- |
| --- | :--------------------: | --------------- | ------------------------------- | ------------------ |
| 1 | firstEp | 是 | 是 | |
| 2 | secondEp | 是 | 是 | |
| 3 | fqdn | 是 | 是 | |
......@@ -716,7 +734,7 @@ charset 的有效值是 UTF-8。
## 2.x->3.0 的废弃参数
| # | **参数** | **适用于 2.X ** | **适用于 3.0 ** | 3.0 版本的当前行为 |
| --- | :---------------------: | --------------- | --------------- | ------------------------------------------------- |
| --- | :---------------------: | --------------- | --------------- | ---------------------------------------------------- |
| 1 | arbitrator | 是 | 否 | 通过 RAFT 协议选主 |
| 2 | numOfThreadsPerCore | 是 | 否 | 有其它参数设置多种线程池的大小 |
| 3 | numOfMnodes | 是 | 否 | 通过 create mnode 命令动态创建 mnode |
......
docs/zh/17-operation/10-monitor.md
浏览文件 @ a171c0c8
......@@ -32,7 +32,7 @@ chmod +x TDinsight.sh
- 使用已经存在的 Grafana Notification Channel `uid`，参数 `-E`。该参数可以使用 `curl -u admin:admin localhost:3000/api/alert-notifications |jq` 来获取。
```bash
sudo ./TDinsight.sh -a http://localhost:6041 -u root -p taosdata -E <notifier uid>
./TDinsight.sh -a http://localhost:6041 -u root -p taosdata -E <notifier uid>
```
运行程序并重启 Grafana 服务，打开面板：`http://localhost:3000/d/tdinsight`。
......@@ -270,7 +270,7 @@ TDinsight dashboard 数据来源于 log 库（存放监控数据的默认db，
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||监控指标值|
|gauge|DOUBLE||监控指标值|
|client\_ip|NCHAR|TAG|client ip|
|endpoint|NCHAR|TAG|taosadpater endpoint|
|request\_method|NCHAR|TAG|request method|
......@@ -284,7 +284,7 @@ TDinsight dashboard 数据来源于 log 库（存放监控数据的默认db，
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||监控指标值|
|gauge|DOUBLE||监控指标值|
|client\_ip|NCHAR|TAG|client ip|
|endpoint|NCHAR|TAG|taosadpater endpoint|
|request\_method|NCHAR|TAG|request method|
......@@ -298,7 +298,7 @@ TDinsight dashboard 数据来源于 log 库（存放监控数据的默认db，
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||监控指标值|
|gauge|DOUBLE||监控指标值|
|endpoint|NCHAR|TAG|taosadpater endpoint|
### taosadapter\_restful\_http\_request\_summary\_milliseconds 表
......@@ -326,7 +326,7 @@ TDinsight dashboard 数据来源于 log 库（存放监控数据的默认db，
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||监控指标值|
|gauge|DOUBLE||监控指标值|
|endpoint|NCHAR|TAG|taosadpater endpoint|
### taosadapter\_system\_cpu\_percent 表
......@@ -336,5 +336,5 @@ TDinsight dashboard 数据来源于 log 库（存放监控数据的默认db，
|field|type|is\_tag|comment|
|:----|:---|:-----|:------|
|\_ts|TIMESTAMP||timestamp|
|guage|DOUBLE||监控指标值|
|gauge|DOUBLE||监控指标值|
|endpoint|NCHAR|TAG|taosadpater endpoint|
docs/zh/27-train-faq/01-faq.md
浏览文件 @ a171c0c8
......@@ -247,4 +247,10 @@ launchctl limit maxfiles
该提示是创建 db 的 vnode 数量不够了，需要的 vnode 不能超过了 dnode 中 vnode 的上限。因为系统默认是一个 dnode 中有 CPU 核数两倍的 vnode，也可以通过配置文件中的参数 supportVnodes 控制。
正常调大 taos.cfg 中 supportVnodes 参数即可。
### 21 【查询】在服务器上的使用 tao-CLI 能查到指定时间段的数据，但在客户端机器上查不到？
这种情况是因为客户端与服务器上设置的时区不一致导致的，调整客户端与服务器的时区一致即可解决。
### 22 【表名】表名确认是存在的，但写入或查询时报表不存在错误，非常奇怪，什么原因？
TDengine 中的所有名称，包括数据库名、表名等都是区分大小写的，如果这些名称在程序或 taos-CLI 中没有使用反引号（`）括起来使用，即使你输入的是大写的，引擎也会转化成小写来使用，如果名称前后加上了反引号，引擎就不会再转化成小写，会保持原样来使用。
source/dnode/vnode/src/inc/tsdb.h
浏览文件 @ a171c0c8
......@@ -351,6 +351,7 @@ typedef struct {
rocksdb_writeoptions_t *writeoptions;
rocksdb_readoptions_t *readoptions;
rocksdb_writebatch_t *writebatch;
rocksdb_writebatch_t *rwritebatch;
TdThreadMutex rMutex;
STSchema *pTSchema;
} SRocksCache;
......
source/dnode/vnode/src/tsdb/tsdbCache.c
浏览文件 @ a171c0c8
......@@ -164,8 +164,10 @@ static int32_t tsdbOpenRocksCache(STsdb *pTsdb) {
}
rocksdb_writebatch_t *writebatch = rocksdb_writebatch_create();
rocksdb_writebatch_t *rwritebatch = rocksdb_writebatch_create();
pTsdb->rCache.writebatch = writebatch;
pTsdb->rCache.rwritebatch = rwritebatch;
pTsdb->rCache.my_comparator = cmp;
pTsdb->rCache.options = options;
pTsdb->rCache.writeoptions = writeoptions;
......@@ -198,6 +200,7 @@ static void tsdbCloseRocksCache(STsdb *pTsdb) {
rocksdb_close(pTsdb->rCache.db);
rocksdb_flushoptions_destroy(pTsdb->rCache.flushoptions);
rocksdb_writebatch_destroy(pTsdb->rCache.writebatch);
rocksdb_writebatch_destroy(pTsdb->rCache.rwritebatch);
rocksdb_readoptions_destroy(pTsdb->rCache.readoptions);
rocksdb_writeoptions_destroy(pTsdb->rCache.writeoptions);
rocksdb_options_destroy(pTsdb->rCache.options);
......@@ -208,14 +211,18 @@ static void tsdbCloseRocksCache(STsdb *pTsdb) {
taosMemoryFree(pTsdb->rCache.pTSchema);
}
static void rocksMayWrite(STsdb *pTsdb, bool force) {
static void rocksMayWrite(STsdb *pTsdb, bool force, bool read) {
rocksdb_writebatch_t *wb = pTsdb->rCache.writebatch;
if (force || rocksdb_writebatch_count(wb) >= 1024) {
if (read) {
wb = pTsdb->rCache.rwritebatch;
}
int count = rocksdb_writebatch_count(wb);
if ((force && count > 0) || count >= 1024) {
char *err = NULL;
rocksdb_write(pTsdb->rCache.db, pTsdb->rCache.writeoptions, wb, &err);
if (NULL != err) {
tsdbError("vgId:%d, %s failed at line %d since %s", TD_VID(pTsdb->pVnode), __func__, __LINE__, err);
tsdbError("vgId:%d, %s failed at line %d, count: %d since %s", TD_VID(pTsdb->pVnode), __func__, __LINE__, count,
err);
rocksdb_free(err);
}
......@@ -227,7 +234,8 @@ int32_t tsdbCacheCommit(STsdb *pTsdb) {
int32_t code = 0;
char *err = NULL;
rocksMayWrite(pTsdb, true);
rocksMayWrite(pTsdb, true, false);
rocksMayWrite(pTsdb, true, true);
rocksdb_flush(pTsdb->rCache.db, pTsdb->rCache.flushoptions, &err);
if (NULL != err) {
tsdbError("vgId:%d, %s failed at line %d since %s", TD_VID(pTsdb->pVnode), __func__, __LINE__, err);
......@@ -453,7 +461,7 @@ int32_t tsdbCacheUpdate(STsdb *pTsdb, tb_uid_t suid, tb_uid_t uid, TSDBROW *pRow
taosMemoryFree(values_list);
taosMemoryFree(values_list_sizes);
rocksMayWrite(pTsdb, false);
rocksMayWrite(pTsdb, false, false);
taosThreadMutexUnlock(&pTsdb->rCache.rMutex);
_exit:
......@@ -537,7 +545,7 @@ int32_t tsdbCacheGetSlow(STsdb *pTsdb, tb_uid_t uid, SArray *pLastArray, SCacheR
}
// store result back to rocks cache
wb = pTsdb->rCache.writebatch;
wb = pTsdb->rCache.rwritebatch;
char *value = NULL;
size_t vlen = 0;
tsdbCacheSerialize(pLastCol, &value, &vlen);
......@@ -552,7 +560,7 @@ int32_t tsdbCacheGetSlow(STsdb *pTsdb, tb_uid_t uid, SArray *pLastArray, SCacheR
}
if (wb) {
rocksMayWrite(pTsdb, false);
rocksMayWrite(pTsdb, false, true);
}
taosThreadMutexUnlock(&pTsdb->rCache.rMutex);
......@@ -602,7 +610,7 @@ static SLastCol *tsdbCacheLoadCol(STsdb *pTsdb, SCacheRowsReader *pr, int16_t sl
}
// store result back to rocks cache
wb = pTsdb->rCache.writebatch;
wb = pTsdb->rCache.rwritebatch;
char *value = NULL;
size_t vlen = 0;
tsdbCacheSerialize(pLastCol, &value, &vlen);
......@@ -620,7 +628,7 @@ static SLastCol *tsdbCacheLoadCol(STsdb *pTsdb, SCacheRowsReader *pr, int16_t sl
}
if (wb) {
rocksMayWrite(pTsdb, false);
rocksMayWrite(pTsdb, false, true);
}
taosThreadMutexUnlock(&pTsdb->rCache.rMutex);
......@@ -671,6 +679,13 @@ static int32_t tsdbCacheLoadFromRaw(STsdb *pTsdb, tb_uid_t uid, SArray *pLastArr
pLastCol = &noneCol;
}
taosArraySet(pLastArray, idxKey->idx, pLastCol);
// taosArrayRemove(remainCols, i);
if (!pTmpColArray) {
continue;
}
SLastCol *pTmpLastCol = taosMemoryCalloc(1, sizeof(SLastCol));
*pTmpLastCol = *pLastCol;
pLastCol = pTmpLastCol;
......@@ -687,7 +702,7 @@ static int32_t tsdbCacheLoadFromRaw(STsdb *pTsdb, tb_uid_t uid, SArray *pLastArr
}
// store result back to rocks cache
wb = pTsdb->rCache.writebatch;
wb = pTsdb->rCache.rwritebatch;
char *value = NULL;
size_t vlen = 0;
tsdbCacheSerialize(pLastCol, &value, &vlen);
......@@ -696,13 +711,10 @@ static int32_t tsdbCacheLoadFromRaw(STsdb *pTsdb, tb_uid_t uid, SArray *pLastArr
size_t klen = ROCKS_KEY_LEN;
rocksdb_writebatch_put(wb, (char *)key, klen, value, vlen);
taosMemoryFree(value);
taosArraySet(pLastArray, idxKey->idx, pLastCol);
// taosArrayRemove(remainCols, i);
}
if (wb) {
rocksMayWrite(pTsdb, false);
rocksMayWrite(pTsdb, false, true);
}
taosArrayDestroy(pTmpColArray);
......@@ -932,7 +944,7 @@ int32_t tsdbCacheDel(STsdb *pTsdb, tb_uid_t suid, tb_uid_t uid, TSKEY sKey, TSKE
size_t *values_list_sizes = taosMemoryCalloc(num_keys * 2, sizeof(size_t));
char **errs = taosMemoryCalloc(num_keys * 2, sizeof(char *));
taosThreadMutexLock(&pTsdb->rCache.rMutex);
rocksMayWrite(pTsdb, true);
rocksMayWrite(pTsdb, true, false);
rocksdb_multi_get(pTsdb->rCache.db, pTsdb->rCache.readoptions, num_keys * 2, (const char *const *)keys_list,
keys_list_sizes, values_list, values_list_sizes, errs);
for (int i = 0; i < num_keys; ++i) {
......@@ -971,7 +983,7 @@ int32_t tsdbCacheDel(STsdb *pTsdb, tb_uid_t suid, tb_uid_t uid, TSKEY sKey, TSKE
taosMemoryFree(values_list);
taosMemoryFree(values_list_sizes);
rocksMayWrite(pTsdb, true);
rocksMayWrite(pTsdb, true, false);
taosThreadMutexUnlock(&pTsdb->rCache.rMutex);
_exit:
......
source/dnode/vnode/src/tsdb/tsdbRead.c
浏览文件 @ a171c0c8
......@@ -3112,6 +3112,10 @@ static int32_t doLoadLastBlockSequentially(STsdbReader* pReader) {
// load the last data block of current table
STableBlockScanInfo* pScanInfo = *(STableBlockScanInfo**)pStatus->pTableIter;
if (pReader->pIgnoreTables && taosHashGet(*pReader->pIgnoreTables, &pScanInfo->uid, sizeof(pScanInfo->uid))) {
// reset the index in last block when handing a new file
doCleanupTableScanInfo(pScanInfo);
pStatus->mapDataCleaned = true;
bool hasNexTable = moveToNextTable(pUidList, pStatus);
if (!hasNexTable) {
return TSDB_CODE_SUCCESS;
......
source/libs/planner/src/planOptimizer.c
浏览文件 @ a171c0c8
......@@ -2219,6 +2219,13 @@ static bool lastRowScanOptMayBeOptimized(SLogicNode* pNode) {
FOREACH(pFunc, ((SAggLogicNode*)pNode)->pAggFuncs) {
SFunctionNode* pAggFunc = (SFunctionNode*)pFunc;
if (FUNCTION_TYPE_LAST == pAggFunc->funcType) {
SNode* pPar = nodesListGetNode(pAggFunc->pParameterList, 0);
if (QUERY_NODE_COLUMN == nodeType(pPar)) {
SColumnNode* pCol = (SColumnNode*)pPar;
if (pCol->colType == COLUMN_TYPE_TAG) {
return false;
}
}
if (hasSelectFunc || QUERY_NODE_VALUE == nodeType(nodesListGetNode(pAggFunc->pParameterList, 0))) {
return false;
}
......@@ -2319,6 +2326,7 @@ static int32_t lastRowScanOptimize(SOptimizeContext* pCxt, SLogicSubplan* pLogic
if (NULL != cxt.pLastCols) {
cxt.doAgg = false;
lastRowScanOptSetLastTargets(pScan->pScanCols, cxt.pLastCols, true);
nodesWalkExprs(pScan->pScanPseudoCols, lastRowScanOptSetColDataType, &cxt);
lastRowScanOptSetLastTargets(pScan->node.pTargets, cxt.pLastCols, false);
nodesClearList(cxt.pLastCols);
}
......
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或