Hi, everyone.
I've come across an "interesting" behavior with the Storage Write API in the Java library. I'm currently testing my application, and here are the steps I follow:
- Drop the table if it exists.
- Create a new table.
- Open a JsonStreamWriter and write one row.
- Read and validate the content of the table.
Everything works fine on the first run. However, on consecutive runs, I receive a message stating that {omitted}/_default stream hasn't been found when the app is trying to open the JsonStreamWriter. Strangely, if we wait for some minutes, everything "resets," and the problem goes away for one run.
I'm seeking assistance in understanding what is happening.
My current theory is that when we delete a table with a recently accessed _default stream, that stream continues to "hang" in some way for a certain period. This lingering state may be preventing the app from accessing the new _default stream of the recreated table.
Please help me understand what is going on.
LinkedIn
Twitter
