[
https://issues.apache.org/jira/browse/USERGRID-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340351#comment-14340351
]
Todd Nine commented on USERGRID-429:
------------------------------------
I'm all for 2. That's the direction we need to move to anyway. If we can do
this without too much pain, this would be ideal. It gets us ahead of the
refactor process on the REST tier as well that will happen in a couple of
months. If we can do it and not de-stablize the rest tier, lets go for it.
> two-dot-o Entity returned in improper format
> --------------------------------------------
>
> Key: USERGRID-429
> URL: https://issues.apache.org/jira/browse/USERGRID-429
> Project: Usergrid
> Issue Type: Bug
> Components: Stack
> Reporter: David Johnson
> Attachments: jsonprettyprint_com_json-pretty-printer_php 2.png,
> jsonprettyprint_com_json-pretty-printer_php.png
>
>
> In the two-dot-o branch entities are returned with some additional fields
> "properties" and "dynamicProperties" that are not supposed to be there. Check
> out the two attached screenshots. The one with the redundant info is the
> two-dot-o one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
