paul-rogers commented on issue #11929: URL: https://github.com/apache/druid/issues/11929#issuecomment-1083548580
Druid does time-range based replacement. [MySQL does row-based replacement](https://dev.mysql.com/doc/refman/8.0/en/replace.html). So, the Druid syntax has to specify the time range to be replaced: ```sql REPLACE [INTO] table WHERE __time IN (<start>, <end>) -- Added -- FOR <partitionSpec | (partitionSpec, partitionSpec, ...)> -- Removed [insert-style column list] SELECT ... PARTITION BY ... ``` SQL says *what* is to be done, not *how* to do it. That the time range corresponds to a partition is an implementation detail for us to sort out. The SQL planner can analyze the `WHERE` clause to ensure it contains only `__time` and that the start, end are valid. Who knows, maybe we will support some other kind of replacement at some point: let's not encode the rules in the syntax. -- 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]
