Skip to content

Fork test: PR #1492 - Add allow_nulls option to comparison checks - #1496

Open
mwojtyczka wants to merge 4 commits into
mainfrom
fork-test/pr-1492
Open

Fork test: PR #1492 - Add allow_nulls option to comparison checks#1496
mwojtyczka wants to merge 4 commits into
mainfrom
fork-test/pr-1492

Conversation

@mwojtyczka

Copy link
Copy Markdown
Contributor

Automated sync from fork PR for CI testing.

Original PR: #1492

All tests, including unit and integration tests run on this PR (they are skipped for fork PRs).

alvaromoureupm and others added 3 commits August 31, 2026 23:20
Comparison checks (is_equal_to, is_not_equal_to, is_not_less_than,
is_not_greater_than, is_in_range, is_not_in_range) follow Spark's
null-comparison semantics, so null values always pass them. Combining
them with a separate is_not_null rule splits the failure metadata
across two checks.

Add an allow_nulls argument (default True, fully backwards compatible)
so null values can fail these checks directly. When allow_nulls=False,
the condition also fails on nulls with a dedicated message and an
_is_null_or_-prefixed alias, mirroring is_not_null_and_is_in_list.

Resolves #1395

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…checks

Add test_col_comparison_checks_with_nulls_failing_column_expression, which
exercises the allow_nulls=False path with a column expression (a + b). It
verifies that nullness is reported against the whole expression when any
operand is null, and that non-null out-of-bounds values still fail with the
expression rendered in the message.

Co-authored-by: Isaac <no-reply@databricks.com>
@mwojtyczka
mwojtyczka requested a review from a team as a code owner September 1, 2026 15:25
@mwojtyczka
mwojtyczka removed the request for review from a team September 1, 2026 15:25
@mwojtyczka mwojtyczka added the do-not-merge The PR is blocked, e.g. being worked on and not ready. Not using draft to be able to test changes. label Sep 1, 2026
@mwojtyczka
mwojtyczka requested a review from grusin-db September 1, 2026 15:25
@mwojtyczka mwojtyczka added fork-test do-not-merge The PR is blocked, e.g. being worked on and not ready. Not using draft to be able to test changes. labels Sep 1, 2026
@codecov

codecov Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.44%. Comparing base (fe3a9ea) to head (d5caa7e).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1496      +/-   ##
==========================================
+ Coverage   92.28%   92.44%   +0.15%     
==========================================
  Files         141      141              
  Lines       13655    13690      +35     
  Branches      151      151              
==========================================
+ Hits        12602    12656      +54     
+ Misses        986      967      -19     
  Partials       67       67              
Flag Coverage Δ
anomaly 51.74% <10.00%> (-0.04%) ⬇️
anomaly-serverless 51.75% <10.00%> (-0.05%) ⬇️
integration 47.63% <90.00%> (+1.12%) ⬆️
integration-serverless 48.85% <90.00%> (+0.01%) ⬆️
mcp 75.41% <ø> (+0.77%) ⬆️
unit 65.93% <100.00%> (+0.09%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

✅ 1000/1000 passed, 49 skipped, 6h37m59s total

Running from acceptance #5720

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

✅ 1/1 passed, 25m17s total

Running from mcp #469

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

✅ 195/195 passed, 1 skipped, 6h53m38s total

Running from anomaly #1834

is_in_range gained an allow_nulls parameter, so build_profiling_rule now
enumerates it as a non-column parameter. Unsupplied by the profiler, it
freezes to None (its unset default), matching the built-in seeder shape.
Update the stale expectation in test_freezes_non_column_parameter_values.

Co-authored-by: Isaac <no-reply@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge The PR is blocked, e.g. being worked on and not ready. Not using draft to be able to test changes. fork-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants