AdHoc StreamSet actions fail if there is at least one bad WebId
Currently calling any of the AdHoc StreamSet actions causes the entire call to fail if the request includes at least one bad WebId. It would be better if the response came back successful and only the sub-items with bad WebIds included an error message.
We have reviewed this idea, and it’s not something we plan to implement at this time. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!
Kevin, thank you for reviewing this issue. I hope you will reconsider this one as in my opinion it is a pretty major bug with the web API that is preventing us from realizing the full potential of the performance improvements streamsets offer. Without a fix for this we are resorted to using only one webID per streamset, otherwise there is a potential for major data loss in our applications.
Chitra Ranganathan Sabapathy commented
"we are trying to build a telemetry catalog for on-demand bulk ETL for data scientists and this request being fulfilled would allow us to remove the costly and annoying web_id verification process."
I wanted to add to this issue. The entire streamset request will also fail if any of the streams return data that isn't supported by the PI Web API. This makes it very difficult to debug in production systems because we cannot determine which stream is the culprit.