nsivabalan commented on issue #5717:
URL: https://github.com/apache/hudi/issues/5717#issuecomment-1305142246
I see. If you would like to understand any details on hudi, or need help w/
any Poc or onboarding let us know. CC @bhasudha
--
This is an automated message from the Apache Git Ser
nsivabalan commented on issue #5717:
URL: https://github.com/apache/hudi/issues/5717#issuecomment-1299681626
@jdiebold : hmm, gotcha, sorry we couldn't help yo much. if you can help us
understand on what grounds hudi lost to something else, would help us make hudi
better for others.
nsivabalan commented on issue #5717:
URL: https://github.com/apache/hudi/issues/5717#issuecomment-1289936485
@jdiebold : gentle ping.
if you got the issue resolved, feel free to close the issue.
--
This is an automated message from the Apache Git Service.
To respond to the message
nsivabalan commented on issue #5717:
URL: https://github.com/apache/hudi/issues/5717#issuecomment-1229358405
@jdiebold : can you respond when you can.
--
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 g
nsivabalan commented on issue #5717:
URL: https://github.com/apache/hudi/issues/5717#issuecomment-1216142966
guess the root cause is that, when you upgraded the table schema w/ new
columns, it should have been nullable. likely in your case it was non-nullable
column. Which is not backwards
nsivabalan commented on issue #5717:
URL: https://github.com/apache/hudi/issues/5717#issuecomment-1152632282
when your schema was upgraded for the first time in the table, you need to
ensure new fields added have defaults set to "null". If not, its going to be
tough. you have to manually ad
