The early table-conf passed a Map<String, String> as a parameter, and the parameters included not only the PROPERTIES() attributes that can be directly used to create doris tables, but also the data that needs to be parsed as a table creation statement. Such as table-buckets.
As a result, in our actual use process, these mixed parameters need to be parsed at various stages, and the logic is also very complicated, because we abstract the parameters of table-conf as a DorisTableConfig object
Checklist(Required)
Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...
Proposed changes
Issue Number: close #xxx
Problem Summary:
The early table-conf passed a
Map<String, String>as a parameter, and the parameters included not only thePROPERTIES()attributes that can be directly used to create doris tables, but also the data that needs to be parsed as a table creation statement. Such astable-buckets. As a result, in our actual use process, these mixed parameters need to be parsed at various stages, and the logic is also very complicated, because we abstract the parameters of table-conf as aDorisTableConfigobjectChecklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...