When a column is removed, the incremental schema change ignore option fails to function and results in a failure.

[case-k-git]

Describe the bug

When processing incrementally, adding new columns is ignored by the ignore setting. However, when a SQL model is modified to remove columns, it fails despite the ignore setting. This is because it attempts to query a column that does not exist in the created temp table. According to the dbt documentation, the job should be designed not to fail when ignored, so it has been corrected.
Dbt documentation

Dbt documentation

Similarly, if you remove a column from your incremental model, and execute a dbt run, this column will not be removed from your target table.

So this should not happen
https://docs.getdbt.com/docs/build/incremental-models#default-behavior

Steps To Reproduce

When executed with the ignore option in an incremental strategy, a table is created on the first run. Removing a column from the SQL leads to a job failure when dbt is executed.

Expected behavior

A clear and concise description of what you expected to happen.
schema change will be ignore and inset into null value

Screenshots and log output

If applicable, add screenshots or log output to help explain your problem.

I will update

System information

The output of dbt --version:

The operating system you're using:

The output of python --version:

Additional context

Add any other context about the problem here.

[case-k-git]

This has been merged so I will close this issue