[
https://issues.apache.org/jira/browse/CASSANDRA-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166766#comment-13166766
]
Zoltan Farkas commented on CASSANDRA-3605:
------------------------------------------
Hmm, as long as the JDK implementation of String does not change it would not
be a bug.
I assume this optimization is quite important, the fact the the optimization
actually is not used is lost...
would it be worth to add a test in a static initialization of this class to
test the existence and functionality of the private constructor and log a
warning that optimization is not used?
cheers!
> Exception swallowing in Hex.java
> --------------------------------
>
> Key: CASSANDRA-3605
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3605
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.5
> Environment: all
> Reporter: Zoltan Farkas
> Priority: Minor
>
> org.apache.cassandra.utils.Hex line 94:
> try
> {
> s = stringConstructor.newInstance(0, c.length, c);
> }
> catch (Exception e)
> {
> // Swallowing as we'll just use a copying constructor
> }
> this code does not comply with coding standard, caught exception needs to be
> rethrown as RuntimeException
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
