architch opened a new pull request, #1380: URL: https://github.com/apache/cassandra-spark-connector/pull/1380
# Description This change optimises byte array to hex string conversion Current implementation uses string formatting which needs to parse the format for every byte. This takes a lot of time and CPU causing, hence we observed a lot of threads occupied with formatting operation. New implementation uses bit operations. ## How did the Spark Cassandra Connector Work or Not Work Before this Patch Describe the problem, or state of the project that this patch fixes. Explain why this is a problem if this isn't obvious. ## General Design of the patch How the fix is accomplished, were new parameters or classes added? Why did you pursue this particular fix? Example: "I removed the incorrect assertion which would throw the ThreeIntException. This exception was incorrectly added and the assertion is not actually needed." Fixes: [Put JIRA Reference HERE](https://issues.apache.org/jira/projects/CASSANALYTICS) # How Has This Been Tested? Almost all changes and especially bug fixes will require a test to be added to either the integration or Unit Tests. Any tests added will be automatically run on travis when the pull request is pushed to github. Be sure to run suites locally as well. # Checklist: - [ ] I have a ticket in the [JIRA](https://issues.apache.org/jira/projects/CASSANALYTICS) - [ ] I have performed a self-review of my own code - [ ] Locally all tests pass (make sure tests fail without your patch) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org For additional commands, e-mail: pr-h...@cassandra.apache.org
