This is an automated email from the ASF dual-hosted git repository.
renqs pushed a commit to branch release-1.16
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/release-1.16 by this push:
new 9699ca7ac18 [FLINK-29389][docs] Update documentation of JDBC and HBase
lookup table for new caching options (#20884)
9699ca7ac18 is described below
commit 9699ca7ac188d24a3a8d33fc6749b08c10ca85c7
Author: Qingsheng Ren <[email protected]>
AuthorDate: Fri Sep 23 22:41:51 2022 +0800
[FLINK-29389][docs] Update documentation of JDBC and HBase lookup table for
new caching options (#20884)
---
docs/content.zh/docs/connectors/table/hbase.md | 69 +++++++++++++++++++--
docs/content.zh/docs/connectors/table/jdbc.md | 79 ++++++++++++++++++++----
docs/content/docs/connectors/table/hbase.md | 73 ++++++++++++++++++++--
docs/content/docs/connectors/table/jdbc.md | 83 ++++++++++++++++++++++----
4 files changed, 269 insertions(+), 35 deletions(-)
diff --git a/docs/content.zh/docs/connectors/table/hbase.md
b/docs/content.zh/docs/connectors/table/hbase.md
index 2ff3fa49ea1..76e4026ac70 100644
--- a/docs/content.zh/docs/connectors/table/hbase.md
+++ b/docs/content.zh/docs/connectors/table/hbase.md
@@ -168,18 +168,42 @@ ON myTopic.key = hTable.rowkey;
<td>是否启用异步查找。如果为真，查找将是异步的。注意：异步方式只支持 hbase-2.2 连接器</td>
</tr>
<tr>
- <td><h5>lookup.cache.max-rows</h5></td>
+ <td><h5>lookup.cache</h5></td>
<td>可选</td>
- <td style="word-wrap: break-word;">-1</td>
+ <td style="word-wrap: break-word;">NONE</td>
+ <td><p>枚举类型</p>可选值: NONE, PARTIAL</td>
+ <td>维表的缓存策略。 目前支持 NONE（不缓存）和 PARTIAL（只在外部数据库中查找数据时缓存）。</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.max-rows</h5></td>
+ <td>可选</td>
+ <td style="word-wrap: break-word;">(none)</td>
<td>Long</td>
- <td>查找缓存的最大行数，超过这个值，最旧的行将过期。注意："lookup.cache.max-rows" 和
"lookup.cache.ttl" 必须同时被设置。默认情况下，查找缓存是禁用的。 </td>
+ <td>查找缓存的最大行数，超过这个值，最旧的行将过期。使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。</td>
</tr>
<tr>
- <td><h5>lookup.cache.ttl</h5></td>
+ <td><h5>lookup.partial-cache.expire-after-write</h5></td>
<td>可选</td>
- <td style="word-wrap: break-word;">0 s</td>
+ <td style="word-wrap: break-word;">(none)</td>
<td>Duration</td>
- <td>查找缓存中每一行的最大生存时间，在这段时间内，最老的行将过期。注意："lookup.cache.max-rows" 和
"lookup.cache.ttl" 必须同时被设置。默认情况下，查找缓存是禁用的。</td>
+ <td>在记录写入缓存后该记录的最大保留时间。
+ 使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.expire-after-access</h5></td>
+ <td>可选</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>在缓存中的记录被访问后该记录的最大保留时间。
+ 使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.caching-missing-key</h5></td>
+ <td>可选</td>
+ <td style="word-wrap: break-word;">true</td>
+ <td>Boolean</td>
+ <td>是否缓存维表中不存在的键，默认为true。
+ 使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。</td>
</tr>
<tr>
<td><h5>lookup.max-retries</h5></td>
@@ -201,6 +225,39 @@ ON myTopic.key = hTable.rowkey;
</tbody>
</table>
+### 已弃用的配置
+这些弃用配置已经被上述的新配置代替，而且最终会被弃用。请优先考虑使用新配置。
+<table>
+ <thead>
+ <tr>
+ <th class="text-left" style="width: 25%">Option</th>
+ <th class="text-left" style="width: 8%">Required</th>
+ <th class="text-left" style="width: 8%">Forwarded</th>
+ <th class="text-left" style="width: 7%">Default</th>
+ <th class="text-left" style="width: 10%">Type</th>
+ <th class="text-left" style="width: 42%">Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><h5>lookup.cache.max-rows</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Integer</td>
+ <td>请配置 "lookup.cache" = "PARTIAL" 并使用
"lookup.partial-cache.max-rows" 代替</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.cache.ttl</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>请配置 "lookup.cache" = "PARTIAL" 并使用
"lookup.partial-cache.expire-after-write" 代替</td>
+ </tr>
+ </tbody>
+<table>
+
数据类型映射表
diff --git a/docs/content.zh/docs/connectors/table/jdbc.md
b/docs/content.zh/docs/connectors/table/jdbc.md
index 9a812fc8918..4fe8f53c583 100644
--- a/docs/content.zh/docs/connectors/table/jdbc.md
+++ b/docs/content.zh/docs/connectors/table/jdbc.md
@@ -201,28 +201,44 @@ ON myTopic.key = MyUserTable.id;
它决定了每个语句是否在事务中自动提交。有些 JDBC 驱动程序，特别是
<a
href="https://jdbc.postgresql.org/documentation/head/query.html#query-with-cursor";>Postgres</a>，可能需要将此设置为
false 以便流化结果。</td>
</tr>
+ <tr>
+ <td><h5>lookup.cache</h5></td>
+ <td>可选</td>
+ <td style="word-wrap: break-word;">NONE</td>
+ <td><p>枚举类型</p>可选值: NONE, PARTIAL</td>
+ <td>维表的缓存策略。 目前支持 NONE（不缓存）和 PARTIAL（只在外部数据库中查找数据时缓存）。</td>
+ </tr>
<tr>
<td><h5>lookup.cache.max-rows</h5></td>
<td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>Integer</td>
- <td>lookup cache 的最大行数，若超过该值，则最老的行记录将会过期。
- 默认情况下，lookup cache 是未开启的。请参阅下面的 <a href="#lookup-cache">Lookup Cache</a>
部分了解更多详情。</td>
+ <td>维表缓存的最大行数，若超过该值，则最老的行记录将会过期。
+ 使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。请参阅下面的 <a
href="#lookup-cache">Lookup Cache</a> 部分了解更多详情。</td>
</tr>
<tr>
- <td><h5>lookup.cache.ttl</h5></td>
+ <td><h5>lookup.partial-cache.expire-after-write</h5></td>
<td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>Duration</td>
- <td>lookup cache 中每一行记录的最大存活时间，若超过该时间，则最老的行记录将会过期。
- 默认情况下，lookup cache 是未开启的。请参阅下面的 <a href="#lookup-cache">Lookup Cache</a>
部分了解更多详情。</td>
+ <td>在记录写入缓存后该记录的最大保留时间。
+ 使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。请参阅下面的 <a
href="#lookup-cache">Lookup Cache</a> 部分了解更多详情。</td>
</tr>
<tr>
- <td><h5>lookup.cache.caching-missing-key</h5></td>
+ <td><h5>lookup.partial-cache.expire-after-access</h5></td>
+ <td>可选</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>在缓存中的记录被访问后该记录的最大保留时间。
+ 使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。请参阅下面的 <a
href="#lookup-cache">Lookup Cache</a> 部分了解更多详情。</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.caching-missing-key</h5></td>
<td>可选</td>
<td style="word-wrap: break-word;">true</td>
<td>Boolean</td>
- <td>标记缓存丢失的键，默认为true</td>
+ <td>是否缓存维表中不存在的键，默认为true。
+ 使用该配置时 "lookup.cache" 必须设置为 "PARTIAL”。</td>
</tr>
<tr>
<td><h5>lookup.max-retries</h5></td>
@@ -262,6 +278,47 @@ ON myTopic.key = MyUserTable.id;
</tbody>
</table>
+### 已弃用的配置
+这些弃用配置已经被上述的新配置代替，而且最终会被弃用。请优先考虑使用新配置。
+<table>
+ <thead>
+ <tr>
+ <th class="text-left" style="width: 25%">Option</th>
+ <th class="text-left" style="width: 8%">Required</th>
+ <th class="text-left" style="width: 8%">Forwarded</th>
+ <th class="text-left" style="width: 7%">Default</th>
+ <th class="text-left" style="width: 10%">Type</th>
+ <th class="text-left" style="width: 42%">Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><h5>lookup.cache.max-rows</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Integer</td>
+ <td>请配置 "lookup.cache" = "PARTIAL" 并使用
"lookup.partial-cache.max-rows" 代替</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.cache.ttl</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>请配置 "lookup.cache" = "PARTIAL" 并使用
"lookup.partial-cache.expire-after-write" 代替</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.cache.caching-missing-key</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">true</td>
+ <td>Boolean</td>
+ <td>请配置 "lookup.cache" = "PARTIAL" 并使用
"lookup.partial-cache.caching-missing-key" 代替</td>
+ </tr>
+ </tbody>
+<table>
+
<a name="features"></a>
特性
@@ -297,14 +354,14 @@ ON myTopic.key = MyUserTable.id;
JDBC 连接器可以用在时态表关联中作为一个可 lookup 的 source (又称为维表)，当前只支持同步的查找模式。
-默认情况下，lookup cache 是未启用的，你可以设置 `lookup.cache.max-rows` and `lookup.cache.ttl`
参数来启用。
+默认情况下，lookup cache 是未启用的，你可以将 `lookup.cache` 设置为 `PARTIAL` 参数来启用。
lookup cache 的主要目的是用于提高时态表关联 JDBC 连接器的性能。默认情况下，lookup cache
不开启，所以所有请求都会发送到外部数据库。
当 lookup cache 被启用时，每个进程（即 TaskManager）将维护一个缓存。Flink
将优先查找缓存，只有当缓存未查找到时才向外部数据库发送请求，并使用返回的数据更新缓存。
-当缓存命中最大缓存行 `lookup.cache.max-rows` 或当行超过最大存活时间 `lookup.cache.ttl`
时，缓存中最老的行将被设置为已过期。
-缓存中的记录可能不是最新的，用户可以将 `lookup.cache.ttl`
设置为一个更小的值以获得更好的刷新数据，但这可能会增加发送到数据库的请求数。所以要做好吞吐量和正确性之间的平衡。
+当缓存命中最大缓存行 `lookup.partial-cache.max-rows` 或当行超过
`lookup.partial-cache.expire-after-write` 或
`lookup.partial-cache.expire-after-access` 指定的最大存活时间时，缓存中的行将被设置为已过期。
+缓存中的记录可能不是最新的，用户可以将缓存记录超时设置为一个更小的值以获得更好的刷新数据，但这可能会增加发送到数据库的请求数。所以要做好吞吐量和正确性之间的平衡。
-默认情况下，flink 会缓存主键的空查询结果，你可以通过将 `lookup.cache.caching-missing-key` 设置为 false
来切换行为。
+默认情况下，flink 会缓存主键的空查询结果，你可以通过将 `lookup.partial-cache.caching-missing-key` 设置为
false 来切换行为。
<a name="idempotent-writes"></a>
diff --git a/docs/content/docs/connectors/table/hbase.md
b/docs/content/docs/connectors/table/hbase.md
index be36cdaaf0c..af41811b306 100644
--- a/docs/content/docs/connectors/table/hbase.md
+++ b/docs/content/docs/connectors/table/hbase.md
@@ -188,20 +188,48 @@ Connector Options
<td>Whether async lookup are enabled. If true, the lookup will be async.
Note, async only supports hbase-2.2 connector.</td>
</tr>
<tr>
- <td><h5>lookup.cache.max-rows</h5></td>
+ <td><h5>lookup.cache</h5></td>
<td>optional</td>
<td>yes</td>
- <td style="word-wrap: break-word;">-1</td>
+ <td style="word-wrap: break-word;">NONE</td>
+ <td><p>Enum</p>Possible values: NONE, PARTIAL</td>
+ <td>The cache strategy for the lookup table. Currently supports NONE (no
caching) and PARTIAL (caching entries on lookup operation in external
database).</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.max-rows</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
<td>Long</td>
- <td>The max number of rows of lookup cache, over this value, the oldest
rows will be expired. Note, "lookup.cache.max-rows" and "lookup.cache.ttl"
options must all be specified if any of them is specified. Lookup cache is
disabled by default.</td>
+ <td>The max number of rows of lookup cache, over this value, the oldest
rows will be expired.
+ "lookup.cache" must be set to "PARTIAL" to use this option.</td>
</tr>
<tr>
- <td><h5>lookup.cache.ttl</h5></td>
+ <td><h5>lookup.partial-cache.expire-after-write</h5></td>
<td>optional</td>
<td>yes</td>
- <td style="word-wrap: break-word;">0 s</td>
+ <td style="word-wrap: break-word;">(none)</td>
<td>Duration</td>
- <td>The max time to live for each rows in lookup cache, over this time,
the oldest rows will be expired. Note, "cache.max-rows" and "cache.ttl" options
must all be specified if any of them is specified.Lookup cache is disabled by
default.</td>
+ <td>The max time to live for each rows in lookup cache after writing
into the cache
+ "lookup.cache" must be set to "PARTIAL" to use this option. </td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.expire-after-access</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>The max time to live for each rows in lookup cache after accessing
the entry in the cache.
+ "lookup.cache" must be set to "PARTIAL" to use this option. </td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.caching-missing-key</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">true</td>
+ <td>Boolean</td>
+ <td>Whether to store an empty value into the cache if the lookup key
doesn't match any rows in the table.
+ "lookup.cache" must be set to "PARTIAL" to use this option.</td>
</tr>
<tr>
<td><h5>lookup.max-retries</h5></td>
@@ -224,6 +252,39 @@ Connector Options
</tbody>
</table>
+### Deprecated Options
+These deprecated options has been replaced by new options listed above and
will be removed eventually. Please consider using new options first.
+<table>
+ <thead>
+ <tr>
+ <th class="text-left" style="width: 25%">Option</th>
+ <th class="text-left" style="width: 8%">Required</th>
+ <th class="text-left" style="width: 8%">Forwarded</th>
+ <th class="text-left" style="width: 7%">Default</th>
+ <th class="text-left" style="width: 10%">Type</th>
+ <th class="text-left" style="width: 42%">Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><h5>lookup.cache.max-rows</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Integer</td>
+ <td>Please set "lookup.cache" = "PARTIAL" and use
"lookup.partial-cache.max-rows" instead.</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.cache.ttl</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>Please set "lookup.cache" = "PARTIAL" and use
"lookup.partial-cache.expire-after-write" instead.</td>
+ </tr>
+ </tbody>
+<table>
+
Data Type Mapping
diff --git a/docs/content/docs/connectors/table/jdbc.md
b/docs/content/docs/connectors/table/jdbc.md
index 9f38f44bd82..3fb2db2250b 100644
--- a/docs/content/docs/connectors/table/jdbc.md
+++ b/docs/content/docs/connectors/table/jdbc.md
@@ -210,30 +210,48 @@ Connector Options
<a
href="https://jdbc.postgresql.org/documentation/head/query.html#query-with-cursor";>Postgres</a>,
may require this to be set to false in order to stream results.</td>
</tr>
<tr>
- <td><h5>lookup.cache.max-rows</h5></td>
+ <td><h5>lookup.cache</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">NONE</td>
+ <td><p>Enum</p>Possible values: NONE, PARTIAL</td>
+ <td>The cache strategy for the lookup table. Currently supports NONE (no
caching) and PARTIAL (caching entries on lookup operation in external
database).</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.partial-cache.max-rows</h5></td>
<td>optional</td>
<td>yes</td>
<td style="word-wrap: break-word;">(none)</td>
- <td>Integer</td>
+ <td>Long</td>
<td>The max number of rows of lookup cache, over this value, the oldest
rows will be expired.
- Lookup cache is disabled by default. See the following <a
href="#lookup-cache">Lookup Cache</a> section for more details.</td>
+ "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.cache.ttl</h5></td>
+ <td><h5>lookup.partial-cache.expire-after-write</h5></td>
<td>optional</td>
<td>yes</td>
<td style="word-wrap: break-word;">(none)</td>
<td>Duration</td>
- <td>The max time to live for each rows in lookup cache, over this time,
the oldest rows will be expired.
- Lookup cache is disabled by default. See the following <a
href="#lookup-cache">Lookup Cache</a> section for more details. </td>
+ <td>The max time to live for each rows in lookup cache after writing
into the cache.
+ "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.cache.caching-missing-key</h5></td>
+ <td><h5>lookup.partial-cache.expire-after-access</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>The max time to live for each rows in lookup cache after accessing
the entry in the cache.
+ "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>optional</td>
<td>yes</td>
<td style="word-wrap: break-word;">true</td>
<td>Boolean</td>
- <td>Flag to cache missing key, true by default</td>
+ <td>Whether to store an empty value into the cache if the lookup key
doesn't match any rows in the table.
+ "lookup.cache" must be set to "PARTIAL" to use this option.</td>
</tr>
<tr>
<td><h5>lookup.max-retries</h5></td>
@@ -278,6 +296,47 @@ Connector Options
</tbody>
</table>
+### Deprecated Options
+These deprecated options has been replaced by new options listed above and
will be removed eventually. Please consider using new options first.
+<table>
+ <thead>
+ <tr>
+ <th class="text-left" style="width: 25%">Option</th>
+ <th class="text-left" style="width: 8%">Required</th>
+ <th class="text-left" style="width: 8%">Forwarded</th>
+ <th class="text-left" style="width: 7%">Default</th>
+ <th class="text-left" style="width: 10%">Type</th>
+ <th class="text-left" style="width: 42%">Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><h5>lookup.cache.max-rows</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Integer</td>
+ <td>Please set "lookup.cache" = "PARTIAL" and use
"lookup.partial-cache.max-rows" instead.</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.cache.ttl</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>Please set "lookup.cache" = "PARTIAL" and use
"lookup.partial-cache.expire-after-write" instead.</td>
+ </tr>
+ <tr>
+ <td><h5>lookup.cache.caching-missing-key</h5></td>
+ <td>optional</td>
+ <td>yes</td>
+ <td style="word-wrap: break-word;">true</td>
+ <td>Boolean</td>
+ <td>Please set "lookup.cache" = "PARTIAL" and use
"lookup.partial-cache.caching-missing-key" instead.</td>
+ </tr>
+ </tbody>
+<table>
+
Features
--------
@@ -305,14 +364,14 @@ The `scan.partition.column` must be a numeric, date, or
timestamp column from th
JDBC connector can be used in temporal join as a lookup source (aka. dimension
table). Currently, only sync lookup mode is supported.
-By default, lookup cache is not enabled. You can enable it by setting both
`lookup.cache.max-rows` and `lookup.cache.ttl`.
+By default, lookup cache is not enabled. You can enable it by setting
`lookup.cache` to `PARTIAL`.
The lookup cache is used to improve performance of temporal join the JDBC
connector. By default, lookup cache is not enabled, so all the requests are
sent to external database.
When lookup cache is enabled, each process (i.e. TaskManager) will hold a
cache. Flink will lookup the cache first, and only send requests to external
database when cache missing, and update cache with the rows returned.
-The oldest rows in cache will be expired when the cache hit to the max cached
rows `lookup.cache.max-rows` or when the row exceeds the max time to live
`lookup.cache.ttl`.
-The cached rows might not be the latest, users can tune `lookup.cache.ttl` to
a smaller value to have a better fresh data, but this may increase the number
of requests send to database. So this is a balance between throughput and
correctness.
+The oldest rows in cache will be expired when the cache hit to the max cached
rows `lookup.partial-cache.max-rows` or when the row exceeds the max time to
live specified by `lookup.partial-cache.expire-after-write` or
`lookup.partial-cache.expire-after-access`.
+The cached rows might not be the latest, users can tune expiration options to
a smaller value to have a better fresh data, but this may increase the number
of requests send to database. 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.cache.caching-missing-key` to false.
+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.
### Idempotent Writes
