@emqx/shared-ui-i18n 0.0.65 → 0.0.68

package/dist/index.js

@@ -174,6 +174,7 @@ FROM
     health_check_interval_jitter: "Health Check Interval Jitter",
     health_check_timeout: "Health Check Timeout",
     query_mode: "Query Mode",
+    dispatch_strategy: "Dispatch Strategy",
     max_retries: "Max Retries",
     worker_pool_size: "Buffer Pool Size",
     start_after_created: "Start After Created",
@@ -440,6 +441,9 @@ FROM
   },
   bigquery: {
     dataset: "Dataset"
+  },
+  quasardb: {
+    health_check_table: "Health Check Table"
   }
 }, a = {
   common: {
@@ -447,6 +451,7 @@ FROM
     health_check_timeout: "健康检查超时",
     health_check_interval_jitter: "健康检查间隔抖动",
     query_mode: "请求模式",
+    dispatch_strategy: "调度策略",
     max_retries: "最大重试次数",
     worker_pool_size: "缓存池大小",
     start_after_created: "创建后立即启动",
@@ -713,6 +718,9 @@ FROM
   },
   bigquery: {
     dataset: "数据集"
+  },
+  quasardb: {
+    health_check_table: "健康检查表"
   }
 }, o = {
   common: {
@@ -785,7 +793,8 @@ FROM
     gcp_project_id: "GCP Project ID",
     gcp_project_number: "GCP Project Number",
     gcp_wif_pool_id: "Workload Identity Pool ID",
-    gcp_wif_pool_provider_id: "Workload Identity Provider ID"
+    gcp_wif_pool_provider_id: "Workload Identity Provider ID",
+    audience: "OAuth Request Audience"
   },
   kafka_producer: {
     kerberos_principal: "Kerberos Principal",
@@ -812,7 +821,9 @@ FROM
   },
   redis: {
     parameters: "Redis Mode",
-    sentinel: "Sentinel Mode"
+    sentinel: "Sentinel Mode",
+    sentinel_username: "Sentinel Username",
+    sentinel_password: "Sentinel Password"
   },
   mongodb: {
     parameters: "MongoDB Mode",
@@ -834,7 +845,8 @@ FROM
     min_heartbeat_frequency_ms: "Minimum Heartbeat Period"
   },
   influxdb: {
-    parameters: "Version of InfluxDB"
+    parameters: "Version of InfluxDB",
+    ping_with_auth: "Ping With Auth"
   },
   iotdb: {
     base_url: "IoTDB REST Service Base URL",
@@ -850,8 +862,13 @@ FROM
     server: "Server"
   },
   mqtt: {
+    keepalive: "MQTT Keepalive",
+    tcp_opts_keepalive: "TCP Keepalive",
     node: "EMQX Node",
-    ids: "Static Client IDs"
+    ids: "Static Client IDs",
+    buffer: "TCP Connection Buffer Size",
+    delay_send: "Delay Send",
+    active_n: "Active N"
   },
   cassandra: {
     keyspace: "Keyspace"
@@ -1032,7 +1049,8 @@ FROM
     gcp_project_id: "GCP 项目 ID",
     gcp_project_number: "GCP 项目编号",
     gcp_wif_pool_id: "工作负载身份池 ID",
-    gcp_wif_pool_provider_id: "工作负载身份提供商 ID"
+    gcp_wif_pool_provider_id: "工作负载身份提供商 ID",
+    audience: "OAuth 请求受众 (Audience)"
   },
   kafka_producer: {
     kerberos_principal: "Kerberos Principal",
@@ -1059,7 +1077,9 @@ FROM
   },
   redis: {
     parameters: "部署模式",
-    sentinel: "哨兵模式"
+    sentinel: "哨兵模式",
+    sentinel_username: "Sentinel 用户名",
+    sentinel_password: "Sentinel 密码"
   },
   mongodb: {
     parameters: "部署模式",
@@ -1081,7 +1101,8 @@ FROM
     min_heartbeat_frequency_ms: "最小心跳周期"
   },
   influxdb: {
-    parameters: "InfluxDB 版本"
+    parameters: "InfluxDB 版本",
+    ping_with_auth: "Ping 请求携带认证"
   },
   iotdb: {
     base_url: "IoTDB REST 服务基础 URL",
@@ -1097,8 +1118,13 @@ FROM
     server: "服务器地址"
   },
   mqtt: {
+    keepalive: "MQTT Keepalive",
+    tcp_opts_keepalive: "TCP Keepalive",
     node: "节点名称",
-    ids: "客户端 ID 列表"
+    ids: "客户端 ID 列表",
+    buffer: "TCP 连接缓冲区大小",
+    delay_send: "延迟发送",
+    active_n: "TCP 接收批量数"
   },
   cassandra: {
     keyspace: "Keyspace"
@@ -1278,6 +1304,8 @@ HGETALL mqtt_acl:\${username}`
 }, i = {
   async: "Async",
   sync: "Sync",
+  per_clientid: "Per Client ID",
+  random: "Random",
   get: "GET",
   post: "POST",
   delete: "DELETE",
@@ -1366,6 +1394,8 @@ HGETALL mqtt_acl:\${username}`
 }, n = {
   async: "异步",
   sync: "同步",
+  per_clientid: "按客户端 ID",
+  random: "随机",
   get: "GET",
   post: "POST",
   delete: "DELETE",
@@ -1461,6 +1491,7 @@ HGETALL mqtt_acl:\${username}`
     health_check_interval_jitter: "在健康检查间隔中添加一个均匀的随机延迟，以便使用同一连接器的动作和 Source 在不同时间点开始其健康检查。",
     inflight_window: "请求飞行队列窗口大小。当请求模式为异步时，如果需要严格保证来自同一 MQTT 客户端的消息有序，则必须将此值设为 1。",
     query_mode: "请求模式。可选 '同步/异步'，默认为'异步'模式。",
+    dispatch_strategy: "当请求未显式设置 pick key 时的分发策略。默认值 <code>按客户端 ID</code> 保持现有行为；设置为 <code>随机</code> 时，此类请求会随机分散到多个 worker。",
     request_ttl: "从请求进入缓冲区开始计时，如果请求在规定的时间内仍停留在缓冲区内或者已发送但未能及时收到响应或确认，该请求将被视为过期。",
     start_timeout: "在回复资源创建请求前等待资源进入健康状态的时间。",
     worker_pool_size: "缓存队列 worker 数量。仅对 egress 类型的桥接有意义。当桥接仅有 ingress 方向时，可设置为 0，否则必须大于 0。",
@@ -1501,7 +1532,8 @@ HGETALL mqtt_acl:\${username}`
     max_row_group_bytes: "行组大小超过此值时，将刷新行组。 实际触发行组刷新使用缓冲数据大小的估计值，因为实际输出可能与原始输入数据大小不同。",
     name: "Schema Registry 中的 Avro Schema 名称。",
     default_compression: "用于压缩 Parquet 行组中数据页的默认算法。",
-    def: "JSON 格式的 Avro Schema。"
+    def: "JSON 格式的 Avro Schema。",
+    audience: "指定请求 OAuth 访问令牌时提供的 `audience` 参数。"
   },
   mqtt: {
     bridge_mode: "该设置仅适用于 MQTT 协议版本低于 5.0 的情况，且远程 MQTT 服务必须支持该功能。开启后，远端服务器将识别当前连接为一个桥接，消息回环检测更高效，收到的保留消息标志位会透传给本地。",
@@ -1514,7 +1546,9 @@ HGETALL mqtt_acl:\${username}`
     payload: "例如：${'{'}payload{'}'}, ${'{'}clientid{'}'}, ${'{'}topic{'}'}, ${'{'}username{'}'} 等。请根据使用动作的业务需求来选择字段，置空则原样转发消息。支持使用 ${'{'}field{'}'} 语法读取数据。",
     static_clientids: "配置 EMQX 节点与静态客户端 ID 的对应关系。当配置了映射关系后，只有在映射中指定的 EMQX 节点才会创建对应的 MQTT 客户端连接。",
     node: "EMQX 的节点名称，例如：<code>emqx{'@'}10.0.0.1</code>",
-    ids: "指定给该节点的静态客户端 ID 列表"
+    ids: "指定给该节点的静态客户端 ID 列表",
+    delay_send: "启用后，EMQX 可能会将较小的 TCP 写入短暂缓存，并合并后一次发送为较大的数据包。适合大量小消息场景，可提升吞吐，但可能增加少量延迟。默认值：<code>false</code>。",
+    active_n: "每个连接在一次批处理中处理的 TCP 入站事件数量。值越大，繁忙连接的吞吐可能越高；值越小，单连接延迟可能更低。默认值：<code>10</code>。"
   },
   http: {
     url: "HTTP 连接器的 URL。<br/>路径中支持占位符，但在主机或端口部分中不能使用占位符。<br/>例如，`http://localhost:9901/${'{'}topic{'}'}` 是允许的，但是 `http://${'{'}host{'}'}:9901/message` 或 `http://localhost:${'{'}port{'}'}/message `不允许。",
@@ -1574,7 +1608,8 @@ HGETALL mqtt_acl:\${username}`
     org: "InfluxDB 组织名称。",
     bucket: "InfluxDB bucket 名称。",
     write_syntax: "使用 InfluxDB API Line Protocol 写入 InfluxDB 的数据，支持占位符，参考 [InfluxDB 2.3 Line Protocol](https://docs.influxdata.com/influxdb/v2.3/reference/syntax/line-protocol/) 及 [InfluxDB 1.8 Line Protocol](https://docs.influxdata.com/influxdb/v1.8/write_protocols/line_protocol_tutorial/) <br/>TLDR: <br/>```<measurement>[,<tag_key>=<tag_value>[,<tag_key>=<tag_value>]] <field_key>=<field_value>[,<field_key>=<field_value>] [<timestamp>]```<br/>注意，整形数值占位符后需要添加一个字符 `i` 类型标识。例如 `${'{'}payload.int_value{'}'}i`",
-    precision: "InfluxDB 时间精度。"
+    precision: "InfluxDB 时间精度。",
+    ping_with_auth: "控制 EMQX 在发送 /ping 健康检查请求时是否附带连接器认证信息。如果你的 InfluxDB 服务要求 /ping 也进行认证，请启用此项。默认值为 false，即保持原有行为，不在 /ping 请求中附带认证信息。"
   },
   datalayers: {
     write_syntax: "Datalayers 采用与 InfluxDB v1 完全兼容的行协议，为用户提供了熟悉且高效的数据写入方式。虽然兼容InfluxDB v1 的语法，但 Datalayers 在底层实现上有其独特之处，以优化性能和适应其特定的存储结构。参考 [InfluxDB Line Protocol](https://docs.datalayers.cn/datalayers/latest/development-guide/writing-with-influxdb-line-protocol.html)",
@@ -1684,6 +1719,8 @@ HGETALL mqtt_acl:\${username}`
     server: "将要连接的 IPv4 或 IPv6 地址，或者主机名。<br/>主机名具有以下形式：`Host[:Port]`。<br/>如果未指定 `[:Port]`，则使用 Redis 默认端口 6379。",
     servers: "集群将要连接的节点列表。 节点之间用逗号分隔，如：`Node[,Node].`<br/>每个节点的配置为：将要连接的 IPv4 或 IPv6 地址或主机名。<br/>主机名具有以下形式：`Host[:Port]`。<br/>如果未指定 `[:Port]`，则使用 Redis 默认端口 6379。",
     sentinel: "哨兵模式。当 Redis 服务运行在哨兵模式下，该配置必须设置为 'sentinel'。",
+    sentinel_username: "用于向 Redis Sentinel 进行身份认证的用户名。若 Sentinel 不需要 ACL 用户名认证，请留空。",
+    sentinel_password: "用于向 Redis Sentinel 进行身份认证的密码。若 Sentinel 不需要认证，请留空。",
     command_template: "用于推送数据的 Redis 命令模板。 每个列表元素代表一个命令名称或其参数。<br/>例如，要通过键 `msgs` 将消息体推送到 Redis 列表中，数组元素应该是： `rpush`, `msgs`, `${'{'}payload{'}'}`。"
   },
   rocketmq: {
@@ -1894,6 +1931,9 @@ HGETALL mqtt_acl:\${username}`
   },
   s3tables: {
     s_3_client_transport_options_request_timeout: "向 S3 服务发起单次 HTTP 请求的最大等待时间，超时后会重试或失败。"
+  },
+  quasardb: {
+    health_check_table: "在动作健康检查中使用的表名。目前，无法直接从 SQL 中推断表名。如果设置，此值将在 `SHOW TABLE <table>` 语句中用于在动作健康检查期间探测表的存在。"
   }
 }, l = {
   common: {
@@ -1907,6 +1947,7 @@ When disabled the messages are buffered in RAM only.`,
     health_check_interval_jitter: "A uniform random delay to be added to health check interval, so that Actions and Sources from the same Connector start their health checks at different instants.",
     inflight_window: "Query inflight window. When query_mode is set to async, this config has to be set to 1 if messages from the same MQTT client have to be strictly ordered.",
     query_mode: "Query mode. Optional 'sync/async', default 'async'.",
+    dispatch_strategy: "The strategy for dispatching queries when a query does not set an explicit pick key. The default value <code>per_clientid</code> preserves the existing behavior. Set to <code>random</code> to spread such queries across multiple workers.",
     request_ttl: "Starting from the moment when the request enters the buffer, if the request remains in the buffer for the specified time or is sent but does not receive a response or acknowledgement in time, the request is considered expired.",
     start_timeout: "Time interval to wait for an auto-started resource to become healthy before responding resource creation requests.",
     worker_pool_size: `The number of buffer workers. Only applicable for egress type bridges.
@@ -1947,7 +1988,8 @@ For bridges only have ingress direction data flow, it can be set to 0 otherwise
     max_row_group_bytes: "The size above which row groups are flushed.  The actual triggering of row group flushes uses estimates of the buffered data sizes, since the actual output may differ in size from the raw input data size.",
     name: "Avro schema name that lives in Schema Registry.",
     default_compression: "The default algorithm to use for compressing data pages in Parquet row groups.",
-    def: "Avro schema definition in JSON format."
+    def: "Avro schema definition in JSON format.",
+    audience: "Specify the `audience` to be provided when requesting the OAuth access token."
   },
   mqtt: {
     bridge_mode: "This setting is only for MQTT protocol version older than 5.0, and the remote MQTT broker MUST support this feature. After being enabled, the remote broker will recognize the current connection as a bridge, that loop detection will be more effective and that retained messages will be propagated correctly.",
@@ -1960,7 +2002,9 @@ For bridges only have ingress direction data flow, it can be set to 0 otherwise
     payload: "For example: ${'{'}payload{'}'}, ${'{'}clientid{'}'}, ${'{'}topic{'}'} , ${'{'}username{'}'}, etc. Use fields according to the action requirements of your business and forwards the message as it is if it is empty.Supports reading data using ${'{'}field{'}'} syntax.",
     static_clientids: "Entries mapping EMQX node names to static client IDs. If any entries are defined, then only EMQX nodes matching those entries will start MQTT clients with the corresponding clientids.",
     node: "EMQX node name, e.g.: <code>emqx{'@'}10.0.0.1</code>.",
-    ids: "Array of static client IDs assigned to this node."
+    ids: "Array of static client IDs assigned to this node.",
+    delay_send: "When enabled, EMQX may briefly buffer small outgoing TCP writes and send them together as larger packets. This can improve throughput when publishing many small messages, but may add a small amount of latency. Default: <code>false</code>.",
+    active_n: "Number of incoming TCP events EMQX processes in one active batch for each connection. A higher value may improve throughput on busy connections; a lower value may reduce per-connection latency. Default: <code>10</code>."
   },
   http: {
     url: "The URL of the HTTP Connector.<br/>Template with variables is allowed in the path, but variables cannot be used in the host or port part.<br/>For example, `http://localhost:9901/${'{'}topic{'}'}` is allowed, but`http://${'{'}host{'}'}:9901/message` or `http://localhost:${'{'}port{'}'}/message`is not allowed.",
@@ -2020,7 +2064,8 @@ For bridges only have ingress direction data flow, it can be set to 0 otherwise
     org: "Organization name of InfluxDB.",
     bucket: "InfluxDB bucket name.",
     write_syntax: "Conf of InfluxDB line protocol to write data points. It is a text-based format that provides the measurement, tag set, field set, and timestamp of a data point, and placeholder supported. See also [InfluxDB 2.3 Line Protocol](https://docs.influxdata.com/influxdb/v2.3/reference/syntax/line-protocol/) and [InfluxDB 1.8 Line Protocol](https://docs.influxdata.com/influxdb/v1.8/write_protocols/line_protocol_tutorial/) <br/>TLDR:<br/>```<measurement>[,<tag_key>=<tag_value>[,<tag_key>=<tag_value>]] <field_key>=<field_value>[,<field_key>=<field_value>] [<timestamp>]```<br/>Please note that a placeholder for an integer value must be annotated with a suffix `i`. For example `${'{'}payload.int_value{'}'}i`.",
-    precision: "InfluxDB time precision."
+    precision: "InfluxDB time precision.",
+    ping_with_auth: "Controls whether EMQX includes connector credentials in /ping health-check requests. Enable this option if your InfluxDB service requires authentication on /ping. The default is false, which preserves the previous behavior and sends /ping without authentication."
   },
   datalayers: {
     write_syntax: "Datalayers adopts a line protocol fully compatible with InfluxDB v1, providing users with a familiar and efficient method for data ingestion. While compatible with InfluxDB v1 syntax, Datalayers has its unique characteristics in its underlying implementation to optimize performance and adapt to its specific storage structure. For more information, refer to [InfluxDB Line Protocol](https://docs.datalayers.cn/datalayers/latest/development-guide/writing-with-influxdb-line-protocol.html).",
@@ -2132,6 +2177,8 @@ Note: this parameter only takes effect when the <code>Driver Type</code> set to
     server: "The IPv4 or IPv6 address or the hostname to connect to.<br/>A host entry has the following form: `Host[:Port]`.<br/>The Redis default port 6379 is used if `[:Port]` is not specified.",
     servers: "A Node list for Cluster to connect to. The nodes should be separated with commas, such as: `Node[,Node].`<br/>For each Node should be: The IPv4 or IPv6 address or the hostname to connect to.<br/>A host entry has the following form: `Host[:Port]`.<br/>The Redis default port 6379 is used if `[:Port]` is not specified.",
     sentinel: "Sentinel mode. Must be set to 'sentinel' when Redis server is running in sentinel mode.",
+    sentinel_username: "Username used to authenticate with Redis Sentinel. Leave it unset when Sentinel does not require ACL username authentication.",
+    sentinel_password: "Password used to authenticate with Redis Sentinel. Leave it unset when Sentinel does not require authentication.",
     command_template: "Redis command template used to export messages. Each list element stands for a command name or its argument.<br/>For example, to push payloads in a Redis list by key `msgs`, the elements should be the following:<br/>`rpush`, `msgs`, `${'{'}payload{'}'}`."
   },
   rocketmq: {
@@ -2345,6 +2392,9 @@ Default: 1, i.e., the primary shard.`,
   },
   s3tables: {
     s_3_client_transport_options_request_timeout: "The maximum time allowed for a single HTTP request to the S3 service. If exceeded, the request will be retried or fail."
+  },
+  quasardb: {
+    health_check_table: "Table name to use in Action health checks. Currently, it's not possible to infer the table name directly from the SQL. If set, this value will be used in a `SHOW TABLE <table>` statement to probe the table existence during Action health checks."
   }
 }, d = {
   title: "Streaming (beta)",
@@ -2421,7 +2471,7 @@ Default: 1, i.e., the primary shard.`,
     total_messages_in_rate: "Messages In",
     total_messages_out_rate: "Messages Out"
   }
-}, m = {
+}, u = {
   title: "Streaming (beta)",
   streams: "Streams",
   streamName: "Stream 名称",
@@ -2495,7 +2545,7 @@ Default: 1, i.e., the primary shard.`,
     total_messages_in_rate: "消息流入速率",
     total_messages_out_rate: "消息流出速率"
   }
-}, u = {
+}, m = {
   title: "ストリーミング（ベータ）",
   streams: "ストリーム",
   streamName: "ストリーム名",
@@ -3127,7 +3177,7 @@ export {
   x as jaFlow,
   g as jaRuleFunction,
   k as jaRuleSQL,
-  u as jaStreaming,
+  m as jaStreaming,
   a as zhActionsLabel,
   S as zhAiLog,
   h as zhCommon,
@@ -3136,6 +3186,6 @@ export {
   c as zhIntegrationDesc,
   b as zhRuleFunction,
   v as zhRuleSQL,
-  m as zhStreaming,
+  u as zhStreaming,
   n as zhSymbolLabel
 };