brachipa commented on issue #30498: URL: https://github.com/apache/beam/issues/30498#issuecomment-2035444619
It looks more like a bug, I tried to debug it and all the time I see the alias until it dropped at some unknown point. Which I couldn't identify. In the examples above, same query, behaves differently, depends on the columns exist in the schema. Regarding the workaround, I wonder what will be the impact on the cpu utilization, we have huge scale and many different queries Also, this workaround applied on this specific query, and we have many different queries provided by different teams, It doesn't scale to examine each query case and try find workaround for any query for any change. ( Even working query can break by some minor change) I hope this can be addressed and fixed. I will be happy to help. But need some hints where to be focused since I couldn't find it myself. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
