abhishekagarwal87 commented on issue #11929: URL: https://github.com/apache/druid/issues/11929#issuecomment-1026552672
I prefer separate clauses for time partitioning and secondary partitioning. It would have been fine if the distinction between primary and secondary partitioning was only an internal detail. But it is not and requires users to pass the input/argument dimension in a very different way depending on what kind of partitioning the input is for. For example for the primary partitioning, we accept special keywords like ALL (or None) but not for the secondary partitioning. Similarly for secondary partitioning, we support multiple schemes such as range, hash, etc. Specifying these additional properties that go beyond column names/expressions makes syntax unwieldy if both cluster-by and partition-by are under one clause. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
