Fix subset so previous entity versions are skipped

Completed

Follow

eivind.engeseter

• March 15, 2023 13:06

The subset implemented for source dataset now includes all the entities from the subset, both latest and previous. This results in unwanted updates that will propagate to all receivers and can cause undesired effects. The subset feature should not have other versions than the latest. Optionally there could be a 

include_previous_versions_in_subsets

with default value: false

If this fix is not prioritized there should quickly come a warning in the portal that this is the current behavior for subsets - a note in the docs are easily missed.

ttps://support.sesam.io/hc/en-us/requests/7999?page=1

1

• Official comment

  

  Geir Ove Grønmo

  • April 14, 2023 12:07

  Yes, we've been aware of this limitation for a while. We are currently working on implementing support for getting only the latest versions of entities out of a subset. A dataset source with a subset would then respect the value of `include_previous_versions_in_subsets` – which is false by default.

  Comment actions Permalink
• 

  Geir Ove Grønmo

  • May 31, 2023 08:50

  This has now been implemented. See https://docs.sesam.io/hub/changelog.html#changelog-2023-05-02

  0

  Comment actions Permalink

Please sign in to leave a comment.