You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yun Tang (JIRA)" <ji...@apache.org> on 2019/08/06 08:37:00 UTC

[jira] [Commented] (FLINK-13598) frocksdb doesn't have arm release

    [ https://issues.apache.org/jira/browse/FLINK-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900774#comment-16900774 ] 

Yun Tang commented on FLINK-13598:
----------------------------------

As far as I know, we use frocksDB mainly because of RocksDB community did not accept our feature of [Flink compaction filter|https://github.com/facebook/rocksdb/pull/4463] instead of some bugs in rocksDB. However, compaction filter would be very useful to evict state entries when out of time to live for Flink.

> 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
(v7.6.14#76016)