This issue can't be edited

Because it belongs to an archived project. Jira admins can restore projects from the archive.

Offer option to decide how aggressively removing a nested element

Description

Today after OGM-674, a nested element with no property left is fully nullified. This is a natural approach in most case except if the document is shared between several application and if unknown properties (to OGM) are involved. We could envision offering a option overridable per entity and maybe even per property to up the standard and be extra conservative.
Depending on how MongoDB projection works (today filtered by selectable columns), we could

  • load the whole document and not remove non empty elements

  • or project the top nested properties (if MongoDB supports that) which would load the whole nested structure. This would load partially the document and would be preferable.

This is probably only useful for MongoDB (I think Neo4J already does that as we load the whole node already).

Environment

None

Activity

Show:

Details

Assignee

Reporter

Participants

Emmanuel Bernard

Components

Priority

Created March 10, 2015 at 7:15 AM
Updated March 10, 2015 at 7:16 AM