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
I was tinkering with building an EntitySource implementation, and as I was trying to build out the Filter, GroupBy, and Iterate functions, and I realized I always needed to List into memory and then iterate to support these other functions because the backend in my case had no iterator/cursor sort of API.
I wonder if we should relax the base EntitySource API to be justGet and List, and then have an additive interface that callers can type check, to see if the more performant methods could be delegated to the entity source.
If so, call the entity source's methods
If not, List(), and then do the filtering, grouping, iterating at the call site.
The text was updated successfully, but these errors were encountered:
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.
github-actionsbot
added
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jun 20, 2023
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.
I was tinkering with building an EntitySource implementation, and as I was trying to build out the
Filter
,GroupBy
, andIterate
functions, and I realized I always needed toList
into memory and then iterate to support these other functions because the backend in my case had no iterator/cursor sort of API.I wonder if we should relax the base
EntitySource
API to be justGet
andList
, and then have an additive interface that callers can type check, to see if the more performant methods could be delegated to the entity source.List()
, and then do the filtering, grouping, iterating at the call site.The text was updated successfully, but these errors were encountered: