[Bug Fix] Fix TableMetadataV1 Validators#544
Conversation
That's a great idea! Shall we create a 0.6.1 milestone or a 0.6.1 proposal in dev-mail-list? I have just opened another bug-fix PR: #547 and I also saw other bug-fix PR may be worth to be added (e.g. #545 ). BTW, If we finally decide to do the release, I am interested in becoming the release manager. :) |
|
@HonahX Yes, that sounds good. There is no formal process for starting a release, just someone needs to take the time to drive the process. Great that you want to become a release manager :D I would also be open to just running 0.7.0 from the main branch. There is already a lot of cool stuff that would be great to get out to the public. |
(cherry picked from commit cc8552d)
When working on #498, I noticed that
new_table_metadatacannot correctly initializepartition_specsandsort_odersfields for V1 Metadata. For example:We may update the validators to consider both the field name and its alias. (ex "sort_orders" and "sort-orders") so that the validators won't override any initialized fields.
cc: @Fokko @amogh-jahagirdar