You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Damien Raude-Morvan (JIRA)" <ji...@apache.org> on 2014/10/19 19:57:33 UTC
[jira] [Created] (GORA-389) MongoStore: Document or List mapping
change cause NPE in clearDirty()
Damien Raude-Morvan created GORA-389:
----------------------------------------
Summary: 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)