b From the perspective of user usage, maintaining consistency is important. If only aligned and nonAligned behaviors are distinguished in the tree model, it will lead to more misunderstandings among users. If the tree model needs to be modified, I think it would be better not to automatically filter null for both aligned and nonAligned queries.
Best Xuan Wang 发件人: Yuan Tian <jackietie...@gmail.com> 日期: 星期一, 2024年9月2日 09:52 收件人: dev <dev@iotdb.apache.org> 主题: [VOTE] Whether to automatically filter out rows that are entirely null in the result set during a scan by the storage engine Hi all, As we discussed in [1], we need to decide whether to automatically filter out rows that are entirely null in the result set during a scan by the storage engine. There are three reasonable options: [a] keep table model same as tree model ( automatically filter out rows that are entirely null ) [b] table model don't automatically filter out rows that are entirely null, but keep the tree model same as before. [c] table model and aligned time series in tree model don't automatically filter out rows that are entirely null, but keep nonAligned time series in tree model same as before Personally, I prefer [c], because in the storage engine, table model shares the same things as aligned time series in tree model, [b] will break it up while scanning. Feel free to vote for the option you personally want to choose. [1] https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2F40gk1k1q3styjsf4s95ydlm5f2l2lcr4&data=05%7C02%7C%7Cf5e5d4a520fc4281420d08dccaf1d37b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638608387199818339%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=%2BCq3wbSemNrKCLW1xidJ2gHFyXBi1GSGrWo6YLWmDEg%3D&reserved=0<https://lists.apache.org/thread/40gk1k1q3styjsf4s95ydlm5f2l2lcr4> Best regards, -------------------------- Yuan Tian
