fix(XCom): /xcom/list got exception when applying filter on the value column

[wei-juncheng]

closes: #42720

• Implementation
• E2E Test
• Unit Test

What does this PR do?

• Fix the error on the XCom filter page in the UI, which is preventing users from using values as filter conditions to select the XCom records they want.

Change details

• airflow/www/utils.py:

  • Add XComFilterStartsWith, XComFilterEndsWith, XComFilterEqual, XComFilterContains, XComFilterNotStartsWith, XComFilterNotEndsWith, XComFilterNotContains, and XComFilterNotEqual classes to handle different types of filtering for XCom values.

    • Since the value is stored in the xcom table in PostgreSQL's bytea format, we first need to convert it into a UTF-8 string. Additionally, because the value content is enclosed in double quotes before being encoded as bytea and stored in the database, we also need to remove the leading and trailing double quotes from the UTF-8 formatted value in order to compare it with the user's input filter condition.
      • describe xcom table:
        • 
        • 
        • 

  • Updated the AirflowFilterConverter class to include the new XCom filters in its conversion table.

  • Add the is_xcom_value method to check if a column name corresponds to an XCom value.

• tests/www/test_utils.py:
  • Add a unit test case TestXComFilter to test whether the SQLAlchemy call sequence behaves as expected.

How did you test?

• Unit Test in tests/www/test_utils.py
• E2E Test

  • I used the example code provided by Airflow to push the XCom content to the database during DAG execution, and then I operated the XCom filter on the Web UI.

    • 

  • Below are the demo screenshots for each of the functionalities.

    • Demo screenshots:

      • Starts With:

      • 

      • Ends With:

      • 

      • Equal:

      • 

      • Contains:

      • 

      • Not Starts With:

      • 

      • Not Ends With:

      • 

      • Not Contains With:

      • 

      • Not Equal:

      • 

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[eladkal]

AI spam

[wei-juncheng]

Hi @eladkal
I apologize. I am the new contributor to this project. Over the past few days, I had an offline handover with @josix regarding this issue, and I will be responsible moving forward. However, while preparing the PR, I accidentally clicked on "create PR." I’m sorry for the disruption. Once the PR is ready, I will re-open it for your review. 🙏🏽

[josix]

Hi @eladkal, sorry to bother you. I’m trying to have @wei-juncheng take over the testing part for #45679 as his first contribution to Airflow. Since he’s new to OSS contributions, his profile doesn’t have many contribution records yet.

@wei-juncheng could you help add more information about what the PR has made and also correct the status to Draft if it is not ready, I'll also close my original PR to avoid confusion, thanks!

[Lee-W]

Hi @eladkal,

Thank you for working on filtering potential AI spam. 😊

I wanted to give you a quick heads-up. I know @josix personally, and he has already created a few pull requests (PRs) and even presented them at the Airflow Town Hall. Additionally, @wei-juncheng is a local community member from Taiwan who is interested in contributing to Airflow and has just started his journey in OSS contributions. I've asked @wei-juncheng to create another PR with more details so he can continue working on this issue and avoid making his PR look like spam. Sorry for the disruption. 🙏

[eladkal]

Ah cool :)

[Lee-W]

Ah cool :)

ah... yes, we can just reopen it haha. Thanks so much for helping out!

[Lee-W]

It mostly looks good to me, but I have some nitpicks. I propose a new way to implement the utility function; however, I'm not sure if it actually simplifies things. If it doesn't, we can just resolve those f-strings once.

[Lee-W]

LGTM. will keep it for a few days so that others can take a look

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.