-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Please update the below figure. The filter strategy should come after the data resource strategy in the pipeline:
This is conceptually important. We have the partial pipeline documenting the data source (typically
DataResource >> Parse >> Mapping
). That should be treated as one unit and always come first in the pipeline. The filter is not a part of the documentation of the data resource, but is a part of our application that selects the subset of all the data in the data resource we are interested in. It should use theinitialize()
method to specify the query such that only the information we need is fetched from the data resource.I did this originally, but unfortunately the
session
object is not returned correctly from the "filter strategy", so I had to switch them around. I believe this issue is being resolved in OTElib, but this is an issue.
Furthermore, retrieving the data from thesession
object is plain wrong and should not be done like this. But that's out-of-scope of this tutorial to fix.
Originally posted by @CasperWA in #125 (comment)