search

flyteorg / flyte

Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
https://flyte.org
Apache License 2.0
5.47k stars 584 forks source link

Add a rate limiter to Hive Client #213

Open EngHabu opened 4 years ago

EngHabu commented 4 years ago

Motivation: Why do you think this is important? Implement this TODO: https://github.com/lyft/flyteplugins/blob/master/go/tasks/plugins/hive/client/qubole_client.go#L70

Goal: What should the final outcome look like, ideally? A configurable rate limiter for qubole/hive client

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Flyte component

[Optional] Propose: Link/Inline If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document.

Additional context Add any other context or screenshots about the feature request here.

Is this a blocker for you to adopt Flyte Please let us know if this makes it impossible to adopt Flyte

kumare3 commented 4 years ago

@EngHabu I think we should add all of this to a ServiceAPI, that way this can be easily extended to all clients

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 2 months ago

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏