[
https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770069#comment-17770069
]
Brandon Williams commented on CASSANDRA-18891:
----------------------------------------------
The rationale for going to 4.1 in CASSANDRA-17019 was the [removal of 32 bit
Darwin|https://github.com/java-native-access/jna/blob/master/CHANGES.md#breaking-changes]
support. I'm not sure this is the right tradeoff; I don't think we support
32bit JVMs as it is, and the appeal of the arm64 architecture is clear. We
have vetted 5.7.0 fairly well at this point so I don't think there's too much
risk of regression there.
> Cassandra 4.0 - JNA 5.6.0 does not support arm64
> ------------------------------------------------
>
> Key: CASSANDRA-18891
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18891
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
> Reporter: Thomas Steinmaurer
> Priority: Normal
> Fix For: 4.0.x
>
>
> As discussed on Slack:
> [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489]
> Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA
> library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS
> Gravition instances e.g. m7g already with Cassandra 4.0.
> From linked ticket:
> "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native
> binding into the C library. JNA 5.6.0 does not support arm64 architecture
> (Apple M1 devices), causing cassandra to fail on bootstrap."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
