This is an automated email from the ASF dual-hosted git repository. jiabaosun pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/flink-connector-mongodb.git
commit 2abed8e2d4e2a91cba25457ceb0004435572cdc8 Author: xli1996 <[email protected]> AuthorDate: Thu Feb 27 22:53:09 2025 -0800 [hotfix][docs] fix lookup.partial-cache.cache-missing-key option name in docs --- docs/content.zh/docs/connectors/table/mongodb.md | 4 ++-- docs/content/docs/connectors/table/mongodb.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/content.zh/docs/connectors/table/mongodb.md b/docs/content.zh/docs/connectors/table/mongodb.md index ea8a35d..ec739ce 100644 --- a/docs/content.zh/docs/connectors/table/mongodb.md +++ b/docs/content.zh/docs/connectors/table/mongodb.md @@ -207,7 +207,7 @@ ON myTopic.key = MyUserTable._id; 请参阅下面的 <a href="#lookup-cache">Lookup Cache</a> 部分了解更多详情。</td> </tr> <tr> - <td><h5>lookup.partial-cache.caching-missing-key</h5></td> + <td><h5>lookup.partial-cache.cache-missing-key</h5></td> <td>可选</td> <td>否</td> <td style="word-wrap: break-word;">true</td> @@ -344,7 +344,7 @@ lookup cache 的主要目的是用于提高时态表关联 MongoDB 连接器的 当缓存命中最大缓存行 `lookup.partial-cache.max-rows` 或当行超过 `lookup.partial-cache.expire-after-write` 或 `lookup.partial-cache.expire-after-access` 指定的最大存活时间时，缓存中的行将被设置为已过期。 缓存中的记录可能不是最新的，用户可以将缓存记录超时设置为一个更小的值以获得更好的刷新数据，但这可能会增加发送到数据库的请求数。所以要做好吞吐量和正确性之间的平衡。 -默认情况下，flink 会缓存主键的空查询结果，你可以通过将 `lookup.partial-cache.caching-missing-key` 设置为 false 来切换行为。 +默认情况下，flink 会缓存主键的空查询结果，你可以通过将 `lookup.partial-cache.cache-missing-key` 设置为 false 来切换行为。 ### 幂等写入 如果在 DDL 中定义了主键，MongoDB connector 将使用 UPSERT 模式 `db.connection.update(<query>, <update>, { upsert: true })` 写入 MongoDB diff --git a/docs/content/docs/connectors/table/mongodb.md b/docs/content/docs/connectors/table/mongodb.md index 8b15b95..29b90d9 100644 --- a/docs/content/docs/connectors/table/mongodb.md +++ b/docs/content/docs/connectors/table/mongodb.md @@ -212,7 +212,7 @@ Connector Options "lookup.cache" must be set to "PARTIAL" to use this option. See the following <a href="#lookup-cache">Lookup Cache</a> section for more details. </td> </tr> <tr> - <td><h5>lookup.partial-cache.caching-missing-key</h5></td> + <td><h5>lookup.partial-cache.cache-missing-key</h5></td> <td>optional</td> <td>no</td> <td style="word-wrap: break-word;">true</td> @@ -373,7 +373,7 @@ have a better fresh data, but this may increase the number of requests send to d So this is a balance between throughput and correctness. By default, flink will cache the empty query result for a Primary key, you can toggle the behaviour -by setting `lookup.partial-cache.caching-missing-key` to false. +by setting `lookup.partial-cache.cache-missing-key` to false. ### Idempotent Writes
