[
https://issues.apache.org/jira/browse/CASSANDRA-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756342#comment-13756342
]
Jonathan Ellis commented on CASSANDRA-5958:
-------------------------------------------
does HashSet.toString actually give us a human-readable error?
> "Unable to find property" errors from snakeyaml are confusing
> -------------------------------------------------------------
>
> Key: CASSANDRA-5958
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5958
> Project: Cassandra
> Issue Type: Bug
> Reporter: J.B. Langston
> Priority: Minor
> Attachments: trunk-5958-skip-missing-properties.patch,
> trunk-5958-v2-print-all-invalid-properties.patch
>
>
> When an unexpected property is present in cassandra.yaml (e.g. after
> upgrading), snakeyaml outputs the following message:
> {code}Unable to find property 'some_property' on class:
> org.apache.cassandra.config.Config{code}
> The error message is kind of counterintuitive because at first glance it
> seems to suggest the property is missing from the yaml file, when in fact the
> error is caused by the *presence* of an unrecognized property. I know if you
> read it carefully it says it can't find the property on the class, but this
> has confused more than one user.
> I think we should catch this exception and wrap it in another exception that
> says something like this:
> {code}Please remove 'some_property' from your cassandra.yaml. It is not
> recognized by this version of Cassandra.{code}
> Also, it might make sense to make this a warning instead of a fatal error,
> and just ignore the unwanted property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
