This article provides information on why the Vertica query provides inconsistency results after upgrading to 25.x and how to resolve the issue.
Environment:
Vertica Analytics Database: v25.1.x
Situation:
Logically equivalent self-join queries on the same table return drastically different results when only the table alias order in the FROM clause is changed. The queries are semantically identical but produce different row counts.
Cause:
The root cause has been identified as the Distributed SIPS feature. This feature was disabled by default in version 24 but became enabled by default in version 25, which led to the issue.