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
Currently the Last Executed relation is outer joined to the Data Source. It usually makes sense unless at least one of the Execution related filters is applied to the query. In that case the logic should correspond to an inner join instead.
For example, when I as a user enable the datetime filter I expect to only see those data sources whose associated Last Executed event satisfies the given date time criteria. The same holds for other Execution related filters like writeMode for instance.
The text was updated successfully, but these errors were encountered:
wajda
changed the title
Consumer API: Data Source "writeMode" and "datetime" filters are counter-intuitive
Consumer API: Data Source filters are counter-intuitive
Oct 4, 2021
Currently the Last Executed relation is outer joined to the Data Source. It usually makes sense unless at least one of the Execution related filters is applied to the query. In that case the logic should correspond to an inner join instead.
For example, when I as a user enable the
datetime
filter I expect to only see those data sources whose associated Last Executed event satisfies the given date time criteria. The same holds for other Execution related filters likewriteMode
for instance.The text was updated successfully, but these errors were encountered: