kestra-io / kestra-io/plugin-huawei
plugin-huawei: kill()/stop() not implemented on killable/pollable tasks
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
Sub-issue of kestra-io/kestra-ee#10964.
**Tasks:** io.kestra.plugin.huawei.dis.Consume, io.kestra.plugin.huawei.dms.kafka.Consume, io.kestra.plugin.huawei.dms.rocketmq.Consume
**Why:** Long-lived stream consume loops with no kill()/stop() override.
**Fix:** override `kill()` and/or `stop()` on these task classes to cancel the poll loop / close the consumer / cancel the remote job. See `io.kestra.plugin.gcp.bigquery.AbstractBigquery` for a reference implementation.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate io.kestra.plugin.huawei.dis.Consume, io.kestra.plugin.huawei.dms.kafka.Consume, and io.kestra.plugin.huawei.dms.rocketmq.Consume, then read io.kestra.plugin.gcp.bigquery.AbstractBigquery for the lifecycle reference. Verify how each long-lived consume loop, consumer, or remote job is stopped, and confirm that kill()/stop() cancels or closes the relevant work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- backend, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 63/100