gopidesupavan opened a new pull request, #42555: URL: https://github.com/apache/airflow/pull/42555
The Kafka ConsumeFromTopicOperator and ProduceToTopicOperator are failing to resolve callable template fields. For a callable to work with template functions, it must accept both the context and jinja_env. If we include `producer_function` and `apply_function` in the template fields, all current users will need to modify their scripts to accept both `context` and `jinja_env`. and some minor updates require in kafka operator. I also tested another scenario where the function does accept context and jinja_env, but in the UI template field, it appears as a generated type object(please check below screenshot). Since there isn’t much value in displaying this field as a generated type object, I believe it's better to remove these from the template fields altogether. Any other suggestion please? <img width="1345" alt="image" src="https://github.com/user-attachments/assets/c957818c-81e7-4d56-bbbc-303270287b4a";> Removed the fields and executed kafka system test.  <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> <!-- Please keep an empty line above the dashes. --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). 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](https://github.com/apache/airflow/tree/main/newsfragments). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
