Remove thrift as a core dependency

[kaxil]

thrift is a dependency for Apache Hive and it is not required by Core Airflow:

airflow/providers/apache/hive/hooks/hive.py:489:        # This is for pickling to work despite the thrift hive client not
airflow/providers/apache/hive/hooks/hive.py:500:        """Returns a Hive thrift client."""
airflow/providers/apache/hive/hooks/hive.py:502:        from thrift.protocol import TBinaryProtocol
airflow/providers/apache/hive/hooks/hive.py:503:        from thrift.transport import TSocket, TTransport
airflow/providers/apache/hive/hooks/hive.py:531:            from thrift_sasl import TSaslClientTransport
airflow/providers/apache/hive/sensors/hive_partition.py:41:    :param metastore_conn_id: reference to the metastore thrift service
airflow/providers/apache/hive/sensors/metastore_partition.py:28:    queries generated by the Metastore thrift service when hitting
airflow/providers/apache/hive/sensors/named_hive_partition.py:36:    :param metastore_conn_id: reference to the metastore thrift service

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[kaxil]

Test failure is unrelated -- Master is broken

[github-actions]

The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Backport packages$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*.

[XD-DENG]

This change itself is good to me.

One more point (not sure if we should cover together here): dependency thrift_sasl is under kerberos currently, but actually its only usage (imported) is in Hive Hook. Is a fix needed for that?

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest master at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[potiuk]

When we remove (and only when you remove) anything from the list here, we should increase PIP_DEPENDENCIES_EPOCH_NUMBER approproately. I updated the outdated description in in #13409 and we should update increase the PIP_DEPENDENCIES_EPOCH_NUMBER number to point to both Dockerfile and Dockerfile.ci and to the right name. Let's merge #13409 first and then we can rebase on top of it, change the EPOCH and get it removed.

[ashb]

When we remove (and only when you remove) anything from the list here, we should increase PIP_DEPENDENCIES_EPOCH_NUMBER approproately. I updated the outdated description in in #13409 and we should update increase the PIP_DEPENDENCIES_EPOCH_NUMBER number to point to both Dockerfile and Dockerfile.ci and to the right name. Let's merge #13409 first and then we can rebase on top of it, change the EPOCH and get it removed.

Except in this case we haven't actually removed the dep, at least not what is installed via the extras ;)

[potiuk]

Except in this case we haven't actually removed the dep, at least not what is installed via the extras ;)

True. I just prefer to be cautious and do it always. The way how PIP treats install requires when doing eager dependency update (so after it gets merged) might work in unexpected ways - depending if thrift is pre-installed before or not.

But yeah, probably in this case there are no scenarios where it would hurt us.

[potiuk]

It's OK for me. Just do it on your own risk ;)