For schema history, is it intended that a change i...
# ingestionb
better-orange-49102
07/28/2022, 12:50 PMFor schema history, is it intended that a change in field TYPE for an existing column do not get a version increment in the history?
When adding new fields/removing new fields I see the version increment, but not for type changes. (Though, my schema changes are done it via MCP emits, so not sure if that is the cause)
e
echoing-airport-49548
08/01/2022, 11:47 PMHey @better-orange-49102 the version should be incremented for type changes as well
echoing-airport-49548
08/01/2022, 11:47 PMWould you mind telling me what the type change was from/to?
b
better-orange-49102
08/01/2022, 11:54 PMHmm I need to double check again later, but I changed the native type of the field and emited a MCP. The MCP is programmatically created though.
e
echoing-airport-49548
08/01/2022, 11:55 PMAh I see, let me see if I can repro this then
b
better-orange-49102
08/02/2022, 1:20 AMhmm tested it on my v0.8.38-ish version (cos i pulled merge from master branch into my implementation):
1. adding/removing a new field increments the version
2. changing the nativetype does increment
3. Change the field type of the field without changing the nativeType does not increment.
better-orange-49102
08/02/2022, 1:23 AMi guess it is logical that a fieldType change would be accompanied by a nativeType change, if Datahub were to query it in the database (and thus incrementing it) but my use case is for users to edit it manually in UI.