This is an automated email from the ASF dual-hosted git repository.
danny0405 pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hudi.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 22f8e052575e docs: update supported instant time formats for
incremental and time travel queries (#18443)
22f8e052575e is described below
commit 22f8e052575e15e00c9437d58bda55cd3203281b
Author: yaojiejia <[email protected]>
AuthorDate: Wed Apr 1 21:54:29 2026 -0400
docs: update supported instant time formats for incremental and time travel
queries (#18443)
---
website/docs/basic_configurations.md | 4 ++--
website/docs/configurations.md | 8 ++++----
website/docs/table_types.md | 6 +++---
website/versioned_docs/version-1.1.1/basic_configurations.md | 4 ++--
website/versioned_docs/version-1.1.1/configurations.md | 8 ++++----
website/versioned_docs/version-1.1.1/table_types.md | 6 +++---
6 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/website/docs/basic_configurations.md
b/website/docs/basic_configurations.md
index 16fb55d1ac71..b4e5bf93fc23 100644
--- a/website/docs/basic_configurations.md
+++ b/website/docs/basic_configurations.md
@@ -92,8 +92,8 @@ Options useful for reading tables via
`read.format.option(...)`
| Config Name
| Default | Description
[...]
|
--------------------------------------------------------------------------------------------
| --------- |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
-|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
+|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
+|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
|
[hoodie.datasource.read.incr.table.version](#hoodiedatasourcereadincrtableversion)
| (N/A) | The table version assumed for incremental read<br
/>`Config Param: INCREMENTAL_READ_TABLE_VERSION`
[...]
|
[hoodie.datasource.read.streaming.table.version](#hoodiedatasourcereadstreamingtableversion)
| (N/A) | The table version assumed for streaming read<br />`Config Param:
STREAMING_READ_TABLE_VERSION`
[...]
| [hoodie.datasource.query.type](#hoodiedatasourcequerytype)
| snapshot | Whether data needs to be read, in `incremental`
mode (new data since an instantTime) (or) `read_optimized` mode (obtain latest
view, based on base files) (or) `snapshot` mode (obtain latest view, by merging
base and (if any) log files)<br />`Config Param: QUERY_TYPE`
[...]
diff --git a/website/docs/configurations.md b/website/docs/configurations.md
index 6b34689f6d60..298fa5fde6e3 100644
--- a/website/docs/configurations.md
+++ b/website/docs/configurations.md
@@ -120,8 +120,8 @@ Options useful for reading tables via
`read.format.option(...)`
| Config Name
| Default | Description
[...]
|
--------------------------------------------------------------------------------------------
| --------- |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
-|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
+|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
+|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
|
[hoodie.datasource.read.incr.table.version](#hoodiedatasourcereadincrtableversion)
| (N/A) | The table version assumed for incremental read<br
/>`Config Param: INCREMENTAL_READ_TABLE_VERSION`
[...]
|
[hoodie.datasource.read.streaming.table.version](#hoodiedatasourcereadstreamingtableversion)
| (N/A) | The table version assumed for streaming read<br />`Config Param:
STREAMING_READ_TABLE_VERSION`
[...]
| [hoodie.datasource.query.type](#hoodiedatasourcequerytype)
| snapshot | Whether data needs to be read, in `incremental`
mode (new data since an instantTime) (or) `read_optimized` mode (obtain latest
view, based on base files) (or) `snapshot` mode (obtain latest view, by merging
base and (if any) log files)<br />`Config Param: QUERY_TYPE`
[...]
@@ -131,7 +131,7 @@ Options useful for reading tables via
`read.format.option(...)`
| Config Name
| Default | Description
[...]
|
-------------------------------------------------------------------------------------------------------------------------------------------------------------
| -------------------------------------- |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel.
Without specified this option, we query the latest snapshot.<br />`Config
Param: TIME_TRAVEL_AS_OF_INSTANT`
[...]
+| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel.
Without specified this option, we query the latest snapshot. Accepted formats:
`yyyyMMddHHmmss[SSS]`, `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss[.SSS]`,
`yyyy-MM-ddTHH:mm:ss[.SSS]`, epoch seconds (10-digit), epoch millis (13-digit).
Invalid values throw an error [...]
| [hoodie.datasource.read.paths](#hoodiedatasourcereadpaths)
| (N/A) | Comma separated list of file paths
to read within a Hudi table.<br />`Config Param: READ_PATHS`
[...]
| [hoodie.datasource.merge.type](#hoodiedatasourcemergetype)
| payload_combine | For Snapshot query on merge on read
table. Use this key to define how the payloads are merged, in 1) skip_merge:
read the base file records plus the log file records without merging; 2)
payload_combine: read the base file records first, for each record in base
file, checks whether the key [...]
|
[hoodie.datasource.query.incremental.format](#hoodiedatasourcequeryincrementalformat)
|
latest_state | This config is used alone with the
'incremental' query type.When set to 'latest_state', it returns the latest
records' values.When set to 'cdc', it returns the cdc data.<br />`Config Param:
INCREMENTAL_FORMAT`<br />`Since Version: 0.13.0`
[...]
@@ -456,7 +456,7 @@ The following set of configurations are common across Hudi.
| Config Name
| Default | Description
[...]
|
----------------------------------------------------------------------------------------
| ---------- |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel. Without specified
this option, we query the latest snapshot.<br />`Config Param: TIMESTAMP_AS_OF`
[...]
+| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel. Without specified
this option, we query the latest snapshot. Accepted formats:
`yyyyMMddHHmmss[SSS]`, `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss[.SSS]`,
`yyyy-MM-ddTHH:mm:ss[.SSS]`, epoch seconds (10-digit), epoch millis (13-digit).
Invalid values throw an error immediately.<br />`Config Param: TIMESTAMP_AS_OF`
[...]
| [hoodie.memory.compaction.max.size](#hoodiememorycompactionmaxsize)
| (N/A) | Maximum amount of memory used in bytes for
compaction operations in bytes , before spilling to local storage.<br />`Config
Param: MAX_MEMORY_FOR_COMPACTION`
[...]
|
[hoodie.common.diskmap.compression.enabled](#hoodiecommondiskmapcompressionenabled)
| true | Turn on compression for BITCASK disk map used by the
External Spillable Map<br />`Config Param:
DISK_MAP_BITCASK_COMPRESSION_ENABLED`
[...]
| [hoodie.common.spillable.diskmap.type](#hoodiecommonspillablediskmaptype)
| BITCASK | When handling input data that cannot be held in
memory, to merge with a file on storage, a spillable diskmap is employed. By
default, we use a persistent hashmap based loosely on bitcask, that offers O(1)
inserts, lookups. Change this to `ROCKS_DB` to prefer using rocksDB, for
handling the spill.<br />`Config Param: SPILLABLE_DISK_MAP_TYPE`
[...]
diff --git a/website/docs/table_types.md b/website/docs/table_types.md
index b2da087bac43..dcc118338aba 100644
--- a/website/docs/table_types.md
+++ b/website/docs/table_types.md
@@ -181,10 +181,10 @@ Following are the configs relevant to different query
types.
| Config Name
| Default | Description
[...]
|----------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
| hoodie.datasource.query.type | snapshot (Optional) |
Whether data needs to be read, in `incremental` mode (new data since an
instantTime) (or) `read_optimized` mode (obtain latest view, based on base
files) (or) `snapshot` mode (obtain latest view, by merging base and (if any)
log files)<br /><br />`Config Param: QUERY_TYPE`
[...]
-| hoodie.datasource.read.begin.instanttime | N/A **(Required)** | Required
when `hoodie.datasource.query.type` is set to `incremental`. Represents the
instant time to start incrementally pulling data from. The instanttime here
need not necessarily correspond to an instant on the timeline. New data written
with an instant_time > BEGIN_INSTANTTIME are fetched out. For e.g:
‘20170901080000’ will get all new data written after Sep 1, 2017 08:00AM. Note
that if `hoodie.datasource.read.han [...]
-| hoodie.datasource.read.end.instanttime | N/A **(Required)** | Used when
`hoodie.datasource.query.type` is set to `incremental`. Represents the instant
time to limit incrementally fetched data to. When not specified latest commit
time from timeline is assumed by default. When specified, new data written with
an instant_time <= END_INSTANTTIME are fetched out. Point in time type
queries make more sense with begin and end instant times specified. Note that
if `hoodie.datasource.re [...]
+| hoodie.datasource.read.begin.instanttime | N/A **(Required)** | Required
when `hoodie.datasource.query.type` is set to `incremental`. Represents the
instant time to start incrementally pulling data from. The instanttime here
need not necessarily correspond to an instant on the timeline. New data written
with an instant_time > BEGIN_INSTANTTIME are fetched out. For e.g:
‘20170901080000’ will get all new data written after Sep 1, 2017 08:00AM. Note
that if `hoodie.datasource.read.han [...]
+| hoodie.datasource.read.end.instanttime | N/A **(Required)** | Used when
`hoodie.datasource.query.type` is set to `incremental`. Represents the instant
time to limit incrementally fetched data to. When not specified latest commit
time from timeline is assumed by default. When specified, new data written with
an instant_time <= END_INSTANTTIME are fetched out. Point in time type
queries make more sense with begin and end instant times specified. Note that
if `hoodie.datasource.re [...]
| hoodie.datasource.query.incremental.format
| latest_state (Optional) | This
config is used alone with the 'incremental' query type.When set to
`latest_state`, it returns the latest records' values. When set to `cdc`, it
returns the cdc data.<br /><br />`Config Param: INCREMENTAL_FORMAT`<br />`Since
Version: 0.13.0`
[...]
-| as.of.instant
| N/A
**(Required)** | The query instant for time travel. Required only in
the context of time travel queries. If not specified, query will return the
latest snapshot.<br /><br />`Config Param: TIME_TRAVEL_AS_OF_INSTANT`
[...]
+| as.of.instant
| N/A
**(Required)** | The query instant for time travel. Required only in
the context of time travel queries. If not specified, query will return the
latest snapshot. Accepted formats: `yyyyMMddHHmmss[SSS]`, `yyyy-MM-dd`,
`yyyy-MM-dd HH:mm:ss[.SSS]`, `yyyy-MM-ddTHH:mm:ss[.SSS]`, epoch seconds
(10-digit), epoch millis (13-digit). Invalid valu [...]
Refer [here](https://hudi.apache.org/docs/next/configurations#Read-Options)
for more details
diff --git a/website/versioned_docs/version-1.1.1/basic_configurations.md
b/website/versioned_docs/version-1.1.1/basic_configurations.md
index 1b888eb9d6ed..88b08ed14822 100644
--- a/website/versioned_docs/version-1.1.1/basic_configurations.md
+++ b/website/versioned_docs/version-1.1.1/basic_configurations.md
@@ -92,8 +92,8 @@ Options useful for reading tables via
`read.format.option(...)`
| Config Name
| Default | Description
[...]
|
--------------------------------------------------------------------------------------------
| --------- |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
-|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
+|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
+|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
|
[hoodie.datasource.read.incr.table.version](#hoodiedatasourcereadincrtableversion)
| (N/A) | The table version assumed for incremental read<br
/>`Config Param: INCREMENTAL_READ_TABLE_VERSION`
[...]
|
[hoodie.datasource.read.streaming.table.version](#hoodiedatasourcereadstreamingtableversion)
| (N/A) | The table version assumed for streaming read<br />`Config Param:
STREAMING_READ_TABLE_VERSION`
[...]
| [hoodie.datasource.query.type](#hoodiedatasourcequerytype)
| snapshot | Whether data needs to be read, in `incremental`
mode (new data since an instantTime) (or) `read_optimized` mode (obtain latest
view, based on base files) (or) `snapshot` mode (obtain latest view, by merging
base and (if any) log files)<br />`Config Param: QUERY_TYPE`
[...]
diff --git a/website/versioned_docs/version-1.1.1/configurations.md
b/website/versioned_docs/version-1.1.1/configurations.md
index 702fb5b61efe..101c5e1aa547 100644
--- a/website/versioned_docs/version-1.1.1/configurations.md
+++ b/website/versioned_docs/version-1.1.1/configurations.md
@@ -120,8 +120,8 @@ Options useful for reading tables via
`read.format.option(...)`
| Config Name
| Default | Description
[...]
|
--------------------------------------------------------------------------------------------
| --------- |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
-|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
+|
[hoodie.datasource.read.begin.instanttime](#hoodiedatasourcereadbegininstanttime)
| (N/A) | Required when `hoodie.datasource.query.type` is set
to `incremental`. Represents the completion time to start incrementally pulling
data from. The completion time here need not necessarily correspond to an
instant on the timeline. New data written with completion_time >=
START_COMMIT are fetched out. For e.g: ‘20170901080000’ will get all new data
written on or after Sep 1, 201 [...]
+|
[hoodie.datasource.read.end.instanttime](#hoodiedatasourcereadendinstanttime)
| (N/A) | Used when `hoodie.datasource.query.type` is set to
`incremental`. Represents the completion time to limit incrementally fetched
data to. When not specified latest commit completion time from timeline is
assumed by default. When specified, new data written with completion_time <=
END_COMMIT are fetched out. Point in time type queries make more sense with
begin and end completion [...]
|
[hoodie.datasource.read.incr.table.version](#hoodiedatasourcereadincrtableversion)
| (N/A) | The table version assumed for incremental read<br
/>`Config Param: INCREMENTAL_READ_TABLE_VERSION`
[...]
|
[hoodie.datasource.read.streaming.table.version](#hoodiedatasourcereadstreamingtableversion)
| (N/A) | The table version assumed for streaming read<br />`Config Param:
STREAMING_READ_TABLE_VERSION`
[...]
| [hoodie.datasource.query.type](#hoodiedatasourcequerytype)
| snapshot | Whether data needs to be read, in `incremental`
mode (new data since an instantTime) (or) `read_optimized` mode (obtain latest
view, based on base files) (or) `snapshot` mode (obtain latest view, by merging
base and (if any) log files)<br />`Config Param: QUERY_TYPE`
[...]
@@ -131,7 +131,7 @@ Options useful for reading tables via
`read.format.option(...)`
| Config Name
| Default | Description
[...]
|
-------------------------------------------------------------------------------------------------------------------------------------------------------------
| -------------------------------------- |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel.
Without specified this option, we query the latest snapshot.<br />`Config
Param: TIME_TRAVEL_AS_OF_INSTANT`
[...]
+| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel.
Without specified this option, we query the latest snapshot. Accepted formats:
`yyyyMMddHHmmss[SSS]`, `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss[.SSS]`,
`yyyy-MM-ddTHH:mm:ss[.SSS]`, epoch seconds (10-digit), epoch millis (13-digit).
Invalid values throw an error [...]
| [hoodie.datasource.read.paths](#hoodiedatasourcereadpaths)
| (N/A) | Comma separated list of file paths
to read within a Hudi table.<br />`Config Param: READ_PATHS`
[...]
| [hoodie.datasource.merge.type](#hoodiedatasourcemergetype)
| payload_combine | For Snapshot query on merge on read
table. Use this key to define how the payloads are merged, in 1) skip_merge:
read the base file records plus the log file records without merging; 2)
payload_combine: read the base file records first, for each record in base
file, checks whether the key [...]
|
[hoodie.datasource.query.incremental.format](#hoodiedatasourcequeryincrementalformat)
|
latest_state | This config is used alone with the
'incremental' query type.When set to 'latest_state', it returns the latest
records' values.When set to 'cdc', it returns the cdc data.<br />`Config Param:
INCREMENTAL_FORMAT`<br />`Since Version: 0.13.0`
[...]
@@ -456,7 +456,7 @@ The following set of configurations are common across Hudi.
| Config Name
| Default | Description
[...]
|
----------------------------------------------------------------------------------------
| ---------- |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel. Without specified
this option, we query the latest snapshot.<br />`Config Param: TIMESTAMP_AS_OF`
[...]
+| [as.of.instant](#asofinstant)
| (N/A) | The query instant for time travel. Without specified
this option, we query the latest snapshot. Accepted formats:
`yyyyMMddHHmmss[SSS]`, `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss[.SSS]`,
`yyyy-MM-ddTHH:mm:ss[.SSS]`, epoch seconds (10-digit), epoch millis (13-digit).
Invalid values throw an error immediately.<br />`Config Param: TIMESTAMP_AS_OF`
[...]
| [hoodie.memory.compaction.max.size](#hoodiememorycompactionmaxsize)
| (N/A) | Maximum amount of memory used in bytes for
compaction operations in bytes , before spilling to local storage.<br />`Config
Param: MAX_MEMORY_FOR_COMPACTION`
[...]
|
[hoodie.common.diskmap.compression.enabled](#hoodiecommondiskmapcompressionenabled)
| true | Turn on compression for BITCASK disk map used by the
External Spillable Map<br />`Config Param:
DISK_MAP_BITCASK_COMPRESSION_ENABLED`
[...]
| [hoodie.common.spillable.diskmap.type](#hoodiecommonspillablediskmaptype)
| BITCASK | When handling input data that cannot be held in
memory, to merge with a file on storage, a spillable diskmap is employed. By
default, we use a persistent hashmap based loosely on bitcask, that offers O(1)
inserts, lookups. Change this to `ROCKS_DB` to prefer using rocksDB, for
handling the spill.<br />`Config Param: SPILLABLE_DISK_MAP_TYPE`
[...]
diff --git a/website/versioned_docs/version-1.1.1/table_types.md
b/website/versioned_docs/version-1.1.1/table_types.md
index b2da087bac43..dcc118338aba 100644
--- a/website/versioned_docs/version-1.1.1/table_types.md
+++ b/website/versioned_docs/version-1.1.1/table_types.md
@@ -181,10 +181,10 @@ Following are the configs relevant to different query
types.
| Config Name
| Default | Description
[...]
|----------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
| hoodie.datasource.query.type | snapshot (Optional) |
Whether data needs to be read, in `incremental` mode (new data since an
instantTime) (or) `read_optimized` mode (obtain latest view, based on base
files) (or) `snapshot` mode (obtain latest view, by merging base and (if any)
log files)<br /><br />`Config Param: QUERY_TYPE`
[...]
-| hoodie.datasource.read.begin.instanttime | N/A **(Required)** | Required
when `hoodie.datasource.query.type` is set to `incremental`. Represents the
instant time to start incrementally pulling data from. The instanttime here
need not necessarily correspond to an instant on the timeline. New data written
with an instant_time > BEGIN_INSTANTTIME are fetched out. For e.g:
‘20170901080000’ will get all new data written after Sep 1, 2017 08:00AM. Note
that if `hoodie.datasource.read.han [...]
-| hoodie.datasource.read.end.instanttime | N/A **(Required)** | Used when
`hoodie.datasource.query.type` is set to `incremental`. Represents the instant
time to limit incrementally fetched data to. When not specified latest commit
time from timeline is assumed by default. When specified, new data written with
an instant_time <= END_INSTANTTIME are fetched out. Point in time type
queries make more sense with begin and end instant times specified. Note that
if `hoodie.datasource.re [...]
+| hoodie.datasource.read.begin.instanttime | N/A **(Required)** | Required
when `hoodie.datasource.query.type` is set to `incremental`. Represents the
instant time to start incrementally pulling data from. The instanttime here
need not necessarily correspond to an instant on the timeline. New data written
with an instant_time > BEGIN_INSTANTTIME are fetched out. For e.g:
‘20170901080000’ will get all new data written after Sep 1, 2017 08:00AM. Note
that if `hoodie.datasource.read.han [...]
+| hoodie.datasource.read.end.instanttime | N/A **(Required)** | Used when
`hoodie.datasource.query.type` is set to `incremental`. Represents the instant
time to limit incrementally fetched data to. When not specified latest commit
time from timeline is assumed by default. When specified, new data written with
an instant_time <= END_INSTANTTIME are fetched out. Point in time type
queries make more sense with begin and end instant times specified. Note that
if `hoodie.datasource.re [...]
| hoodie.datasource.query.incremental.format
| latest_state (Optional) | This
config is used alone with the 'incremental' query type.When set to
`latest_state`, it returns the latest records' values. When set to `cdc`, it
returns the cdc data.<br /><br />`Config Param: INCREMENTAL_FORMAT`<br />`Since
Version: 0.13.0`
[...]
-| as.of.instant
| N/A
**(Required)** | The query instant for time travel. Required only in
the context of time travel queries. If not specified, query will return the
latest snapshot.<br /><br />`Config Param: TIME_TRAVEL_AS_OF_INSTANT`
[...]
+| as.of.instant
| N/A
**(Required)** | The query instant for time travel. Required only in
the context of time travel queries. If not specified, query will return the
latest snapshot. Accepted formats: `yyyyMMddHHmmss[SSS]`, `yyyy-MM-dd`,
`yyyy-MM-dd HH:mm:ss[.SSS]`, `yyyy-MM-ddTHH:mm:ss[.SSS]`, epoch seconds
(10-digit), epoch millis (13-digit). Invalid valu [...]
Refer [here](https://hudi.apache.org/docs/next/configurations#Read-Options)
for more details
