imay commented on issue #2195: why storage medium setting only supports the path extension? URL: https://github.com/apache/incubator-doris/issues/2195#issuecomment-555048927 @vagetablechicken > > And if other property is added to this path later, the what will the format be? > > It's a good question. The format like "path,medium=xxx,capacity=xxx" looks like the best choice. > But now, config's pattern is "key = value", so it'll look like: > > `storage_root_path = /home/disk1/palo.HDD,capacity=50,medium=HDD;/home/disk2/palo.SSD,capacity=1;/home/disk2/palo, medium=SSD` > > It's difficult to punctuate. And it's difficult to discriminate one pattern from another. > If `=` is difficult to punctuate, how about `:`, like `storage_root_path = /home/disk1/palo.HDD,capacity:50,medium:HDD` > How about support one more pattern? We can set a obvious format marker '('. If we read '(', that means we use the new pattern to parse path. Otherwise, we use the old pattern "< path.extension >, < capacity >;< path.extension >". > The new pattern can be: > `storage_root_path = ( { path = < path >;capacity = < capacity >;medium = < medium >;},{ path = < path >;} );` > > We don't need to mix the patterns up, right? Unless one format is not suitable, otherwise it is better not to introduce anthor format.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
