0003548: Fix NPE on processing schema only batches #85
Conversation
|
Lukas, can you provide a simple test case to help us reproduce this one? |
|
Mark, this bug has been detected in our internal test environment. I'll reach back to you as soon as I have a better description to reproduce this on your side. What I can tell right now, is that it happens where a lot of single table schema reloads, and sync triggers are happening in a very short time frame. The error happens on the client side. I'll backout the changes and will send you the the failing batch content. This especially happened (the NPE) if the table modification fails due to a deadlock situation. |
|
Closing as author has not responded in 3 years. Feel free to rebase to 3.12, reproduce, and open a new PR if this is still an issue. |
|
Super disappoining, closing this for me not responding whereas you are the one who is not responding 👎🏼 |
If you process schema only batches you sometimes get NPE at random places. We need to open the context and batch on the datawriter as those will be accessed at later steps (
errorFilter,statisticsetc.)