Rushabh Shah created PHOENIX-7057: ------------------------------------- Summary: Potential bug in MetadataEndpointImpl#updateIndexState. Key: PHOENIX-7057 URL: https://issues.apache.org/jira/browse/PHOENIX-7057 Project: Phoenix Issue Type: Bug Reporter: Rushabh Shah
This is the relevant [code snippet|https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java#L4067-L4073]. {code} try (RegionScanner countScanner = region.getScanner(new Scan(get))) { List<Cell> countCells = new ArrayList<>(); scanner.next(countCells); count = Result.create(countCells) .getValue(TABLE_FAMILY_BYTES, PhoenixDatabaseMetaData.PENDING_DISABLE_COUNT_BYTES); } {code} Instead of scanner.next, should it have been countScanner.next? This is the change that have introduced a potential bug. PHOENIX-6658 [~stoty] WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)