You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/10/14 02:49:00 UTC

[jira] [Commented] (AIRFLOW-6786) Adding KafkaConsumerHook, KafkaProducerHook, and KafkaSensor

    [ https://issues.apache.org/jira/browse/AIRFLOW-6786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213544#comment-17213544 ] 

ASF GitHub Bot commented on AIRFLOW-6786:
-----------------------------------------

dferguson992 opened a new pull request #11520:
URL: https://github.com/apache/airflow/pull/11520


   Dear Airflow Maintainers,
   
   Please accept the following PR that
   
   Add the KafkaProducerHook.
   Add the KafkaConsumerHook.
   Add the KafkaSensor which listens to messages with a specific topic.
   Related Issue:
   #1311
   
   Issue link: AIRFLOW-6786
   
   Make sure to mark the boxes below before creating PR: [x]
   
   Description above provides context of the change
   Commit message/PR title starts with [AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID*
   Unit tests coverage for changes (not needed for documentation changes)
   Commits follow "How to write a good git commit message"
   Relevant documentation is updated including usage instructions.
   I will engage committers as explained in Contribution Workflow Example.
   For document-only changes commit message can start with [AIRFLOW-XXXX].
   Reminder to contributors:
   
   You must add an Apache License header to all new files
   Please squash your commits when possible and follow the 7 rules of good Git commits
   I am new to the community, I am not sure the files are at the right place or missing anything.
   
   The sensor could be used as the first node of a dag where the second node can be a TriggerDagRunOperator. The messages are polled in a batch and the dag runs are dynamically generated.
   
   Thanks!
   
   Note, as per denied PR #1415, it is important to mention these integrations are not suitable for low-latency/high-throughput/streaming. For reference, #1415 (comment).
   
   Co-authored-by: Dan Ferguson dferguson992@gmail.com
   Co-authored-by: YuanfΞi Zhu
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Adding KafkaConsumerHook, KafkaProducerHook, and KafkaSensor
> ------------------------------------------------------------
>
>                 Key: AIRFLOW-6786
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6786
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: contrib, hooks
>    Affects Versions: 1.10.9
>            Reporter: Daniel Ferguson
>            Assignee: Daniel Ferguson
>            Priority: Minor
>
> Add the KafkaProducerHook.
>  Add the KafkaConsumerHook.
>  Add the KafkaSensor which listens to messages with a specific topic.
>  Related Issue:
>  #1311 (Pre-dates Jira Migration)
> Reminder to contributors:
> You must add an Apache License header to all new files
>  Please squash your commits when possible and follow the 7 rules of good Git commits
>  I am new to the community, I am not sure the files are at the right place or missing anything.
> The sensor could be used as the first node of a dag where the second node can be a TriggerDagRunOperator. The messages are polled in a batch and the dag runs are dynamically generated.
> Thanks!
> Note, as per denied PR [#1415|https://github.com/apache/airflow/pull/1415], it is important to mention these integrations are not suitable for low-latency/high-throughput/streaming. For reference, [#1415 (comment)|https://github.com/apache/airflow/pull/1415#issuecomment-484429806].
> Co-authored-by: Dan Ferguson [dferguson992@gmail.com|mailto:dferguson992@gmail.com]
>  Co-authored-by: YuanfΞi Zhu



--
This message was sent by Atlassian Jira
(v8.3.4#803005)