Remove _id in sink

Answered

Follow

Marius Dammen

• January 21, 2020 07:22

Is it possible to create a feature that will remove the "_id" property for data passing out of Sesam through a sink? It seems that it cannot be removed, and it may cause issues for receiving systems in some scenarios.

4

• Official comment

  

  Geir Ove Grønmo

  • October 13, 2020 10:58

  Do you have a specific sink in mind? This behaviour varies from sink to sink.

  Comment actions Permalink
• 

  Marius Dammen

  • October 13, 2020 13:49

  Json and rest are typical sinks that would benefit here. We see that some url/http based services run validation on the json payload they receive, and the "_id" field typically makes it non-valid.

  1

  Comment actions Permalink
• 

  Geir Ove Grønmo

  • October 16, 2020 11:45

  The "json" sink is a sink that implements Sesam's JSON Push Protocol[1]. It follows strict rules for the payload. The "http_endpoint" receiver is symmetrical to the sink and it support entities without an "_id" property, but in this case you can add DTL to add it for you before the entity reaches the sink. We don't think there is a limitation in the "json" or "rest" sink that require you to send the "_id" as part of the payload. If you think otherwise, then please create a support ticket.

  [1] https://docs.sesam.io/json-push.html

  0

  Comment actions Permalink

Please sign in to leave a comment.