DynamoDbMapper ISSUE

There were multiple pojos which maps with one of our DynamoDb table with slightly different schema (leveraging nosql).

For one of the pojos, while populating one of the attributes, it was always throwing some weird exception and no one had any idea about it.
An intern was assigned to fix it in case some new pair of eyes can observe something weird about the pojo.

Later, I realized that the way DynamoDbMapper behaves inside a pojo is very particular and hidden.
A method was declared as public instead of private in the pojo, and DynamoDbMapper while mapping the pojo to the table with reflection, it said that this attribute (a substring of the method name) cannot be converted.

Finally, it was just a single word change from PUBLIC TO PRIVATE.