EntitySource API Question

[joelanford]

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 just Get 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.

1. If so, call the entity source's methods
2. If not, List(), and then do the filtering, grouping, iterating at the call site.

[github-actions]

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-actions]

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.

[joelanford]

This is no longer irrelevant. EntitySource was removed in #108.