PDGGK commented on issue #19178: URL: https://github.com/apache/iotdb/issues/19178#issuecomment-6742746629
Yes, it's up as #19195. Schema fragments now get the same deadline as data fragments, and `COUNT DEVICES` passes the `IoTDBLocal` context to its filter, so the TAG/ATTRIBUTE predicates and `SHOW`/`COUNT DEVICES` from this issue work, with or without `IoTDBLocal`. `UPDATE` isn't touched. For the regression case on the rejection, you only need a scalar UDF and the table from the description: the `StrF` class there, or `DeviceNameFunction` from the IT module, which also takes and returns a string. These are the forms I'd cover. All three fail with `305: null` today, on master and with the PR: ```sql UPDATE db.t SET attr1 = str_f(device_id) WHERE device_id = 'd2'; UPDATE db.t SET attr1 = 'x' WHERE str_f(device_id) = 'd2'; UPDATE db.t SET attr1 = upper(str_f(device_id)) WHERE device_id = 'd2'; ``` `UPDATE db.t SET attr1 = upper(device_id) WHERE device_id = 'd2'` works and should keep working. `DELETE DEVICES` already rejects a UDF at analysis time in all eight forms I tried, so that one seems fine. -- 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]
