[ 
https://issues.apache.org/jira/browse/FLINK-35573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weijie Guo updated FLINK-35573:
-------------------------------
    Fix Version/s: 2.0.0
                       (was: 2.0-preview)

> [FLIP-447] Upgrade FRocksDB from 6.20.3 to 8.10.0
> -------------------------------------------------
>
>                 Key: FLINK-35573
>                 URL: https://issues.apache.org/jira/browse/FLINK-35573
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>    Affects Versions: 2.0.0
>            Reporter: Yue Ma
>            Assignee: Yue Ma
>            Priority: Major
>             Fix For: 2.0.0
>
>
> The FLIP: 
> [https://cwiki.apache.org/confluence/display/FLINK/FLIP-447%3A+Upgrade+FRocksDB+from+6.20.3++to+8.10.0]
>  
> RocksDBStateBackend is widely used by Flink users in large state 
> scenarios.The last upgrade of FRocksDB was in version Flink-1.14, which 
> mainly supported features such as support arm platform, deleteRange API, 
> period compaction, etc. It has been a long time since then, and RocksDB has 
> now been released to version 8.x. The main motivation for this upgrade is to 
> leverage the features of higher versions of Rocksdb to make Flink 
> RocksDBStateBackend more powerful. While RocksDB is also continuously 
> optimizing and bug fixing, we hope to keep FRocksDB more or less in sync with 
> RocksDB and upgrade it periodically.
> The plan is as follows
> *Release Frocksdb-8.10.0 official products*
>  # Prepare the compiled frocksdb branch
>  # Support Disable PERF-CONTEXT in compilation
>  # Cherry pick IngestDB requires  commit
>  # Setup the CI environment for FRocksDB-8.10
>  # Release Frocksdb-8.10.0 official products
>  # Update the dependency of FRocksDB in pom file of Flink-RocksDB-Statebackend
> *Make ingestDB available* 
>  # Flink ingestDB code related bug fixes
>  # Remove comments from the code related to ingestDB and mark the 
> functionality of ingestDB as available (perhaps we can mark ingestDB as an 
> experimental feature first)
>  # Using ingestDB as the default recovery mode for rescaling
> (已编辑)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to