PDGGK commented on PR #19152:
URL: https://github.com/apache/iotdb/pull/19152#issuecomment-6823906206

   Thanks for explaining. I hadn't thought about the two scans seeing different 
rows, and with no shared snapshot that does sound worse than a size limit.
   
   I built 726a2a6 and checked the empty-string change on a standalone server. 
The dynamic and static forms both give an `empty_string` column, and `SELECT 
empty_string FROM (PIVOT ...)` works now. With two aggregates the columns are 
`empty_string_sum(v)` and `empty_string_count(v)`, and with a second ON item 
`empty_string_d1`. When the data also has the value `'EMPTY_STRING'`, that 
column becomes `EMPTY_STRING_1`, because the names are compared 
case-insensitively, and both columns can be selected. All 33 tests in 
`IoTDBPivotIT` pass for me with `-PTableSimpleIT` and `-PTableClusterIT` (1C3D).
   


-- 
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]

Reply via email to