You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "Michael Russo (JIRA)" <ji...@apache.org> on 2015/11/20 01:10:11 UTC
[jira] [Updated] (USERGRID-1125) Create tests that walks a
collection with cursors at the Entity Manager level
[ https://issues.apache.org/jira/browse/USERGRID-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Russo updated USERGRID-1125:
------------------------------------
Description:
Ensure there is a test at the entity manager level which inserts enough data that's 2-3x the usergrid.graph.shard.size configuration used during the test. After data is inserted, it should traverse the collection with page size at least 500 (same as GET /org/app/collection?limit=500) until the end, utilizing the cursor provided. This traverse should be repeated at least 3-4 times to ensure the count of entities returned each time exactly matches and nothing is missing.
This should effectively validate that the sharding that exists in lower levels within graph is working as expected.
was:
Ensure we have a test at the entity manager level which inserts enough data that's 2-3x the usergrid.graph.shard.size configuration used during the test. After data is inserted, it should traverse the collection with page size at least 500 (same as GET /org/app/collection?limit=500) until the end, utilizing the cursor provided. This traverse should be repeated at least 3-4 times to ensure the count of entities returned each time exactly matches and nothing is missing.
This should effectively validate that the sharding that exists in lower levels within graph is working as expected.
> Create tests that walks a collection with cursors at the Entity Manager level
> -----------------------------------------------------------------------------
>
> Key: USERGRID-1125
> URL: https://issues.apache.org/jira/browse/USERGRID-1125
> Project: Usergrid
> Issue Type: Story
> Reporter: Michael Russo
>
> Ensure there is a test at the entity manager level which inserts enough data that's 2-3x the usergrid.graph.shard.size configuration used during the test. After data is inserted, it should traverse the collection with page size at least 500 (same as GET /org/app/collection?limit=500) until the end, utilizing the cursor provided. This traverse should be repeated at least 3-4 times to ensure the count of entities returned each time exactly matches and nothing is missing.
> This should effectively validate that the sharding that exists in lower levels within graph is working as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)