Re: the number of rowsFiltered is increased, even not filtered

13일 수요일 13:45 받는 사람: user@hbase.apache.org 제목: Re: the number of rowsFiltered is increased, even not filtered Thank you for your reply. I will check if I can make UT and create it. But before that, in the following section, if (isEmptyRow || ret == FilterWrapper.FilterRowRetCode.EXCLUDE

Re: the number of rowsFiltered is increased, even not filtered

(scannerContext); } } Thanks. 보낸 사람: 张铎(Duo Zhang) 보낸 날짜: 2024년 11월 11일 월요일 22:28 받는 사람: user@hbase.apache.org 제목: Re: the number of rowsFiltered is increased, even not filtered Could you provide a UT to represent this behavior? Looking at the code, I agree with

Re: the number of rowsFiltered is increased, even not filtered

Could you provide a UT to represent this behavior? Looking at the code, I agree with you that this seems like a bug. But the scan logic is a bit complicated, I'm not sure whether we have other ways to make the result correct... Thanks. Kang Minwoo 于2024年11月11日周一 20:16写道： > > Hello Community, >

the number of rowsFiltered is increased, even not filtered

Hello Community, According to the HBASE-5980[1], rowsFiltered should only count the number of rows filtered by the filter. However, if the current row is DeleteFamily, the number of rowsFiltered increases because there are no results in populateResult. // HRegion.RegionScannerImpl