Amazon kinesis hook contains firehose class

[xchwan]

Apache Airflow Provider(s)

amazon

Versions of Apache Airflow Providers

issue #52712 request to build kinesis provider, which means kinesis data stream.
But, the current kinesis hook in providers/amazon/src/airflow/providers/amazon/aws/hooks/kinesis.py
only has firehose hook.
Base on
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html
boto3 doc. Firehose and Kinesis is not in the same category. The kinesis file should not have filehose hook.
I think the filehose hook should exist in filehose.py independently for kinesis data stream hook set up.

Apache Airflow version

3

Operating System

MacOS26

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

What happened

No response

What you think should happen instead

No response

How to reproduce

Only filename need to modify

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[jroachgolf84]

Thanks for submitting the issue! Can you please update the title to be "firehouse" instead of "filehose"? Please feel free to open up a PR for this issue. Thanks!

[xchwan]

Thanks for submitting the issue! Can you please update the title to be "firehouse" instead of "filehose"? Please feel free to open up a PR for this issue. Thanks!

It is firehose. I'm wonder that should I modify file name directly or do deprecation warning?

[jroachgolf84]

Sorry - in the issue title that you're created, you've called it "filehouse" (an "l" instead of an "r").

[xchwan]

Sorry - in the issue title that you're created, you've called it "filehouse" (an "l" instead of an "r").

Modify done. Thanks.

[yash1thsa]

I would like to help/assist on this. Let me know if help needed

[xchwan]

I would like to help/assist on this. Let me know if help needed

Thanks for your help, but as I said, I’ll make the PR myself. Appreciate it!

[jason810496]

I think it would better to separate to 2 releases.

1. Add Firehouse Hook ( by just import from existed Kinesis Hook ) and add deprecation warning to Kinesis Hook that user should switch to Firehouse Hook.
2. After 1. is released, then replace Kinesis Hook implementation with "Kinesis Data Stream"

cc @eladkal

Any comment for this approach?

[eladkal]

I think this is more of a question to the AWS team @vincbeck @o-nikolas

[vincbeck]

I think it would better to separate to 2 releases.

1. Add Firehouse Hook ( by just import from existed Kinesis Hook ) and add deprecation warning to Kinesis Hook that user should switch to Firehouse Hook.
2. After 1. is released, then replace Kinesis Hook implementation with "Kinesis Data Stream"

cc @eladkal

Any comment for this approach?

Yes and no :) I agree with 1. but I disagree with 2. Doing 2 would means creating a major version for Amazon provider package, but even more importantly having a very short deprecation period for users. We cannot do that. I think we should:

• Do 1 as suggested by @jason810496
• Create Kinesis hook either in providers/amazon/src/airflow/providers/amazon/aws/hooks/kinesis.py or providers/amazon/src/airflow/providers/amazon/aws/hooks/kinesis_analytics.py