You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 18, 2019. It is now read-only.
Issue #18 has laid the groundwork for this feature by allowing any counter to specify its own indexing choices. To finish this feature, we need to add method to CounterService to return a pagable list of all counters, with options for sorting and filtering.
In addition, this feature needs to add methods to allow finding counters by CounterGroup. See issue #6 for more details.
The counter group information, while present in the datastore, is not currently bing updated. As part of completing this issue, we'll want to update the eventually consistent count of a counter in the CounterGroup entity. To do this, we can async-shedule a task to increment the CounterGroup data at a later point in time. We'll want to accumulate these for high-traffic counters, so consider using the "one scheduled ticket" pattern either using a named task or by using the toolset used by UpSwell.
The text was updated successfully, but these errors were encountered:
sappenin
changed the title
Enhance CounterService interface to allow for returning all Counters, as well as sorting and filtering
Enhance CounterService interface to allow for returning all Counters (plus sorting and filtering) using CounterGroups
Nov 29, 2015
sappenin
changed the title
Enhance CounterService interface to allow for returning all Counters (plus sorting and filtering) using CounterGroups
Enhance CounterService interface to allow for returning all Counters (plus sorting using CounterGroups and filtering)
Nov 29, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue #18 has laid the groundwork for this feature by allowing any counter to specify its own indexing choices. To finish this feature, we need to add method to CounterService to return a pagable list of all counters, with options for sorting and filtering.
In addition, this feature needs to add methods to allow finding counters by CounterGroup. See issue #6 for more details.
The counter group information, while present in the datastore, is not currently bing updated. As part of completing this issue, we'll want to update the eventually consistent count of a counter in the CounterGroup entity. To do this, we can async-shedule a task to increment the CounterGroup data at a later point in time. We'll want to accumulate these for high-traffic counters, so consider using the "one scheduled ticket" pattern either using a named task or by using the toolset used by UpSwell.
The text was updated successfully, but these errors were encountered: