Remove unused _OPERATOR_EXTRA_LINKS in serialized_objects

[gopidesupavan]

In AF2 , get_operator_extra_links was used to get the extra links, and they were handled in webserver. In AF3 a new XComOperatorLink class added and extra links are no longer processed in the webserver. Instead when a taks runs, the get_link result is pushed to XCom . The webserver then reads it from the XCom.

For plugins defined links, They are converted to XComOperatorLink during deserialization so the webserver can read them too. https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/serialization/serialized_objects.py#L1607

---

^ 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 airflow-core/newsfragments.

[gopidesupavan]

Added these links to standard provider section #49447

[gopidesupavan]

In AF2 this is being used part of _deserialize_operator_extra_links . Is there any reason not using this method in AF3? to my understand for AF3 its referring new class XComOperatorLink could this be reason ?

[amoghrajesh]

Yeah @gopidesupavan thats the reason. Now the operator extra links do not run in the webserver anymore.

We push the value generated by get_link function to xcom when a task is running instead (for operator_extra_links at operator / task level) and the webserver reads that off. For operator links in plugins defined, during deserialisation, we convert that object to a xcomoperatorlink instead and webserver just reads the xcom

[gopidesupavan]

Yeah @gopidesupavan thats the reason. Now the operator extra links do not run in the webserver anymore.

We push the value generated by get_link function to xcom when a task is running instead (for operator_extra_links at operator / task level) and the webserver reads that off. For operator links in plugins defined, during deserialisation, we convert that object to a xcomoperatorlink instead and webserver just reads the xcom

Thanks yeah, Alright we can cleanup these methods.

[amoghrajesh]

Yeah i think we can do this now. Looks fine to me, but would like a second set of eyes too in case we miss something obvious.

[gopidesupavan]

Yeah i think we can do this now. Looks fine to me, but would like a second set of eyes too in case we miss something obvious.

fine :)

[gopidesupavan]

Anyone would like to have a look into this?

[kaxil]

Could you add a tldr in PR description of What's the problem or if they are unused -- i.e. motivation behind the change

[kaxil]

Once you add PR description, you are good to go :)

[gopidesupavan]

Could you add a tldr in PR description of What's the problem or if they are unused -- i.e. motivation behind the change

Yeah added pretty much the understand from the amogh comment i have added there :)