[
https://issues.apache.org/jira/browse/FLINK-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176196#comment-17176196
]
Stephan Ewen commented on FLINK-13598:
--------------------------------------
Maybe [~liyu] could share some of his plans. As far as I know, they are trying
to get rid of a full frocksdb build, rather using a vanilla rocksdb and an
additional shared library (like a plugin) with the custom mergers and
compaction filters. I guess those would need to be build per processor
architecture, but at least we would not need to build rocksdb itself per target
architecture.
> frocksdb doesn't have arm release
> ----------------------------------
>
> Key: FLINK-13598
> URL: https://issues.apache.org/jira/browse/FLINK-13598
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / State Backends
> Affects Versions: 1.9.0, 2.0.0
> Reporter: wangxiyuan
> Priority: Major
>
> Flink now uses frocksdb which forks from rocksdb for module
> *flink-statebackend-rocksdb*. It doesn't contain arm release.
> Now rocksdb supports ARM from
> [v6.2.2|https://search.maven.org/artifact/org.rocksdb/rocksdbjni/6.2.2/jar]
> Can frocksdb release an ARM package as well?
> Or AFAK, Since there were some bugs for rocksdb in the past, so that Flink
> didn't use it directly. Have the bug been solved in rocksdb already? Can
> Flink re-use rocksdb again now?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
