Open li-boxuan opened 4 months ago
I've noticed that an error is intentionally thrown when specifying 'Not Null' in the code. This decision should be by design , especially during schema alterations where the default value for new columns is logically null.
This decision should be by design , especially during schema alterations where the default value for new columns is logically null.
Yeah I agree with that. I would consider it as a glitch in the doc to be improved.
@li-boxuan - thanks for creating this issue. Would you like to submit a pull request to update the language of the docs?
I understand this might be by design, but https://docs.delta.io/latest/delta-batch.html#add-columns could be made more clear. It currently says,
which gives me an impression that one can override the nullability, but I got
Also, note that due to #831, you cannot change an existing nullable column to non-nullable. This means the ONLY way to have a non-nullable column is to do so when creating the table.
Version: