[
https://issues.apache.org/jira/browse/USERGRID-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382206#comment-14382206
]
Todd Nine commented on USERGRID-509:
------------------------------------
After thinking about this a bit more, I think we should completely remove
CollectionScope. It is redundant, scope of our types is encapsulated within
our Id object. Therefore, we do not need scope. Scope can be inferred from
the type in the Id. This scope would need to be passed during search by field.
Otherwise, it can be removed from the API, and from storage.
> Cardinality of the EntityCollectionManager is incorrect and may need
> refactored
> -------------------------------------------------------------------------------
>
> Key: USERGRID-509
> URL: https://issues.apache.org/jira/browse/USERGRID-509
> Project: Usergrid
> Issue Type: Story
> Components: Stack
> Reporter: Todd Nine
> Assignee: Todd Nine
>
> An entity can only exist in a single scope. However, this makes it impossible
> to batch fetch entities from multiple scopes in a single network request.
> This interface needs changed. Our EntityCollectionManagerFactory needs to
> change to return an EntityCollectionManager by ApplicationScope. Further
> read/write requests would then need to take an encapsulating CollectionScope.
> This would allow us to batch write and batch fetch multiple entities across
> different collections in a single request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
