[DAE-133] Removing types-comparison when dropping a column

[felipemiquelim]

Why? 📖

When running an ALTER TABLE Hive stores the types of columns from table schema in sequential order to enforce the same types after the ALTER TABLE. However when performing our abstraction of DROP COLUMN, the types may change, since the schema will definitely change.

Currently, if we try to drop a column that changes this 'types order', the following error returns:

thrift_files.libraries.thrift_hive_metastore_client.ttypes.InvalidOperationException: InvalidOperationException(message='The following columns have types incompatible with the existing columns in their respective positions :\ncolumn_name')

What? 🔧

• Adding a call to change metastore settings while in drop_columns_from_table:
  Allowing, in the current execution, the changing of types when comparing the table schema prior and after ALTER TABLE.
• Adjusting tests

Type of change 🗄️

• Bug fix (non-breaking change which fixes an issue)

How everything was tested? 📏

Ran the config command both alone and together with the drop_columns_from_table and it only succeed in the same 'transaction'.

Checklist 📝

• I have added labels to distinguish the type of pull request.
• My code follows the style guidelines of this project (docstrings, type hinting and linter compliance);
• I have performed a self-review of my own code;
• I have made corresponding changes to the documentation;
• I have added tests that prove my fix is effective or that my feature works;
• I have made sure that new and existing unit tests pass locally with my changes;

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication