[
https://issues.apache.org/jira/browse/GORA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193140#comment-14193140
]
ASF GitHub Bot commented on GORA-389:
-------------------------------------
Github user drazzib commented on the pull request:
https://github.com/apache/gora/pull/15#issuecomment-61367523
Merged into master
https://git-wip-us.apache.org/repos/asf?p=gora.git;a=commit;h=f267370f1bb3a3bc3c69550be8c2d9d7d33affc7
> MongoStore: Document or List mapping change cause NPE in clearDirty()
> ---------------------------------------------------------------------
>
> Key: GORA-389
> URL: https://issues.apache.org/jira/browse/GORA-389
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-mongodb
> Affects Versions: 0.5
> Reporter: Damien Raude-Morvan
>
> I've found an issue in current implementation of MongoStore on [Document or
> List|http://gora.apache.org/current/gora-mongodb.html] mapping type handling.
> If your schema contains a field like this :
> {noformat}
> { "name": "keywords",
> "type": { "type": "array", "items": "string"},
> "default": null
> }
> {noformat}
> If you choose to latter defaults to an empty array instead of null value like
> this
> {noformat}
> { "name": "keywords",
> "type": { "type": "array", "items": "string"},
> "default": []
> }
> {noformat}
> loading old data will fail because of clearDirty method will try to also
> clear a null object.
> {code}
> persistent.clearDirty();
> {code}
> I implemented and tested a fix which always return a DirtyListWrapper or
> DirtyMapWrapper instead of previous null value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
