vaidikgarg-bit opened a new issue, #3407: URL: https://github.com/apache/hugegraph/issues/3407
In the review of #3404, @bitflicker64 found that `MapLimitIterator` keeps each emitted `RocksDBSession.BackendColumn` in its dedup set and passes the same object downstream. On an id-only `PRIMARY_SCAN` (`null_property = true`, no property list, condition, order-by or aggregation) with `dedup_option = LIMIT_DEDUP`, `ProjectionStage.handle()` then sets `column.value = new byte[0]` in place (`ProjectionStage.java`, the `BACKEND_COLUMN` branch). The stored key changes after insertion, so it no longer equals a later byte-equal row, and the duplicate is emitted again. Their probe gave 100 rows without the reset and 200 with it. Only a gRPC client that sets `dedup_option` reaches this today, since `StoreQueryParam` fixes it to `NONE`. Proposed fix: have `ProjectionStage` replace the column instead of mutating it (`result.setColumn(BackendColumn.of(column.name, new byte[0]))`), plus a regression test that runs each emitted row through the projection before reading the next. I'd like to work on this. -- 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]
