Hey Ayush, Thanks for bringing this up.
This is clearly a bug and not the expected behavior so I logged HIVE-29180. It has been working fine for quite some time so some recent change must have caused this. Let's continue the discussion/investigation under HIVE-29180. Best, Stamatis [1] https://issues.apache.org/jira/browse/HIVE-29180 On Wed, Sep 3, 2025 at 9:54 AM Ayush Saxena <[email protected]> wrote: > > Hi All, > > I’ve been reviewing the Sonar builds running in CI, and I’ve noticed > that at times it reports a large number of warnings that are > completely unrelated to the code touched by a PR. > > In some cases, I’ve seen 100+ warnings raised for PRs with fewer than > 100 lines of change, which defeats the purpose of having such checks > in place. Reviewing these irrelevant warnings is neither practical nor > productive—personally, I don’t think anyone would want to sift through > them just to identify the handful that may actually be relevant. > > I believe we should either: configure Sonar to flag only the issues > directly related to the changes in the PR, if there is any way to do > so or disable this check to avoid unnecessary use of CI resources. > > For example, [1] is a report in [2] where a simple 3-line POM change > resulted in ~100 warnings. > > Thoughts? > > -Ayush > > [1] https://github.com/apache/hive/pull/6049#issuecomment-3237772048 > [2] https://github.com/apache/hive/pull/6049
