DaZuiZui commented on issue #17939: URL: https://github.com/apache/iotdb/issues/17939#issuecomment-4901146030
Correction to the earlier V1 design note about `TIMECOL`: V1 should support a `TIMECOL` argument, with default value `time`. The table model already supports custom TIME column names, e.g. `CREATE TABLE t(event_time TIMESTAMP TIME, value DOUBLE FIELD)`. If FFT only accepts a column literally named `time`, then valid table-model tables with custom TIME column names cannot use FFT directly. Supporting optional `TIMECOL` keeps backward/default usage unchanged while making FFT consistent with the table model and existing TVFs that identify the time column explicitly. Updated V1 expectation: - `TIMECOL` is optional and defaults to `time`. - `DATA ... ORDER BY` must order by the column specified by `TIMECOL`. - FFT should exclude that selected time column, not only a hard-coded `time` column, from numeric value columns. -- 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]
