Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
Hi @Willie
Were you able to find any solution for this?
I have come across similar issue where multiple entries are being updated simultaneously and UpdateStreamEntry leaks few of the entries.
Note: My Stream datashape has String,Number and Infotable type columns.
Solved! Go to Solution.
Hi Sathish,
I have segregated the nested infotables into separate infotables and using only AddStreamEntry and UpdateStreamEntry is not required anymore which actually was causing issue. Hence the issue is resolved.
Hi @TanmeyTWX
The use case was scrapped so I did not need the stream anymore. According to @abhiramk , you can have the same timestamp in a stream if the source is different, but in my case, I had the same source so I was adding random milliseconds. It might be possible to make the milliseconds less random if you have a property on the stream to act as a counter for milliseconds that resets to 0 after 999, but I haven't tried it so I don't know if it would work. The threads might (probably) access and increment the property simultaneously. As @nmilleson mentioned, maybe you could have a staging area for your data before adding them to a stream so you could ensure they are added. Stage the data then change the timestamp one by one before adding.
Hi @TanmeyTWX
I asked ChatGPT. Here's the response:
I think a combination of #1 and #2/#4 could work.
Hi Sathish,
I have segregated the nested infotables into separate infotables and using only AddStreamEntry and UpdateStreamEntry is not required anymore which actually was causing issue. Hence the issue is resolved.