[
https://issues.apache.org/jira/browse/CASSANALYTICS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANALYTICS-187:
------------------------------------
Test and Documentation Plan: ci; unit test
Status: Patch Available (was: Open)
PR: [https://github.com/apache/cassandra-analytics/pull/228]
CI:
[https://app.circleci.com/pipelines/gh/yifan-c/cassandra-analytics/272/details?useNewPipelines=true&job=2b04fec9-a0e5-4c59-9382-090adb23cb70&workflowId=4ec41554-b89c-488d-97cc-eb8e2d1091cb&buildNumber=2287&jobType=build]
> Fix FastByteOperations Silently Falling Back to Pure-Java Comparator
> --------------------------------------------------------------------
>
> Key: CASSANALYTICS-187
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-187
> Project: Apache Cassandra Analytics
> Issue Type: Bug
> Components: Writer
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> FastByteOperations.java, copied from the Cassandra codebase, looked up the
> Unsafe singleton using the field name "UNSAFE" instead of the actual
> "theUnsafe" field, so the reflective lookup always threw NoSuchFieldException
> and the class silently fell back to PureJavaOperations instead of the
> Unsafe-based fast path. This change corrects the field name to "theUnsafe"
> and realigns the rest of the class with the upstream Cassandra implementation
> it was copied from, restoring the intended fast-path byte comparison.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
