Fix schema removal issue from DROP VIEW and get_insert_overwrite_sql strategy

[erikachen19]

resolves #550

Description

schema needs to be removed when dropping a temporary view (file format = Parquet) and when applying the get_insert_overwrite_sql strategy

Checklist

• I have signed the CLA

• I have run this code in development and it appears to resolve the stated issue

• This PR includes tests, or tests are not required/relevant for this PR

• I have updated the CHANGELOG.md and added information about my change to the "dbt-glue next" section.

[moomindani]

It seems that the integration test failed. Could you please fix it?

Plz ignore Python model test as it's newly added test yesterday. If you fetch the upstream change, it will start succeeding.

[moomindani]

The integ test still failed. Can you make sure that your local integ test succeeded?

[erikachen19]

Hi @moomindani,
the local integration test ran successfully.
The upstream change (support for Python model) has been fetched.

[moomindani]

Thanks. Can you clean up your PR in the diff without including the other Python model support by git rebase?

[erikachen19]

sorry, i am afraid that i dont know how to use git rebase,
did i add extra files that i should not have had to?

would be easier if i create new feature branch from main?

[moomindani]

Thanks for thinking about that.

To reflect latest changes happening in the main branch, I usually do like...

1. Switch to your branch

$ git checkout your_branch

2. Reflect changes

$ git pull origin your_branch

3. Rebase your PR branch onto main

$ git rebase main

If you are not familiar with the commands, it may be easier for you to use LLM like Amazon Q CLI to help this. I used Amazon Q CLI asking it and it worked pretty well.

Here's the sample prompt I used:

In this repo, I am working on PR in `your_branch` branch. As the gap between upstream and this branch became bigger, I want to reflect the latest changes to `your_branch` branch. I already updated main branch with the latest changes. How can I merge the changes without messing up the PR?

Make sure that you amend the commit before that. If making a new PR is easier for you, that will be totally fine as well.

[erikachen19]

Hi @moomindani,
Thank you for sharing the commands.
The PR has been cleaned up.

[moomindani]

Thank you for your contribution! Merged.

[erikachen19]

hi @moomindani ,
Thank you for your help!
Is there any plan to make a new release with those updates?

[moomindani]

Yes, but we still have some action items need to be addressed.