apurtell commented on PR #2527: URL: https://github.com/apache/phoenix/pull/2527#issuecomment-4699615439
## Test Results ### Unit tests | Test | Tests run | Failures | Errors | Skipped | | --- | --- | --- | --- | --- | | `ExplainPlanTest` | 105 | 0 | 0 | 0 | | `ExplainJsonOutputTest` | 2 | 0 | 0 | 0 | | `ExplainOptionsParserTest` | 16 | 0 | 0 | 0 | | `StatementHintsCompilationTest` | 4 | 0 | 0 | 0 | | **Total** | **127** | **0** | **0** | **0** | ### Integration tests | Test | Tests run | Failures | Errors | Skipped | | --- | --- | --- | --- | --- | | `ExplainPlanWithStatsEnabledIT` | 30 | 0 | 0 | 0 | | `ExplainPlanWithStatsDisabledIT` | 17 | 0 | 0 | 0 | | **Total** | **47** | **0** | **0** | **0** | ## Notes - `ExplainJsonOutputTest` validates the end-to-end `Statement.executeQuery` path for both `(FORMAT JSON)` and `(REGIONS, FORMAT JSON)`: exactly one result-set row, pretty-printed (two-space) indentation present in the raw cell, and deep equality of the normalized JSON against the in-process `ExplainPlanAttributes` for the same query. - `regionLocations` is elided by `ExplainJsonNormalizer`, so the `(REGIONS, FORMAT JSON)` case confirms the combination produces one well-formed JSON row rather than asserting on cluster-specific region content. -- 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]
