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

Robert Metzger commented on FLINK-13598:
----------------------------------------

Thanks again for your answers.

Till, Andrey and I had an offline discussion about this ticket, and we came to 
the conclusion that we currently don't have the resources to address or mentor 
this change into Flink. My original intention when asking was to figure out 
what was missing from the RocksDB side to allow Flink on ARM ... but I didn't 
consider all the long-term implications of it (CI support, follow up 
maintenance).
We (the three of us) decided to wait until (another) committer or PMC member 
has some ARM hardware (Apple will make that happen some time soon), so that 
they can properly review the changes, and also address new issues on the ARM 
architecture.
This does obviously not mean that somebody else can take/mentor this ticket 
(for example Yu Li). We also believe it makes sense to discuss this again on 
the dev@ list to check if there's commitment to maintain another 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)

Reply via email to