The current PR refers to bumping go-pinot-api version to 0.3.0, allowing terraform provider to manage the property in question. Since this is a configuration for dimension fields only, I'm also suggesting the splitting fieldSpec in dimensionFieldSpec and metricFieldSpec.
Other than that, I also needed to refactor notNull property usage, given json encoder limitation @gbrlcustodio mentioned in https://github.com/azaurus1/go-pinot-api/pull/126 when it comes to omitted falsy values.
Please be thoughtful about this being my first go at Golang 🥁, so probably this one requires a thorough review before moving on. :sweat_smile:
In order to address #56, https://github.com/azaurus1/go-pinot-api/pull/126 introduced
singleValueField
schema's property management.The current PR refers to bumping
go-pinot-api
version to 0.3.0, allowing terraform provider to manage the property in question. Since this is a configuration for dimension fields only, I'm also suggesting the splittingfieldSpec
indimensionFieldSpec
andmetricFieldSpec
.Other than that, I also needed to refactor
notNull
property usage, given json encoder limitation @gbrlcustodio mentioned in https://github.com/azaurus1/go-pinot-api/pull/126 when it comes to omitted falsy values.Please be thoughtful about this being my first go at Golang 🥁, so probably this one requires a thorough review before moving on. :sweat_smile: