You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Description
Dear Doris Development Team,
I hope this message finds you well. I am writing to request a feature enhancement for the CREATE-JOB functionality within Doris, specifically to accommodate real-time metric analysis.
Currently, the CREATE-JOB feature allows for the scheduling of jobs with specific execution intervals, which is incredibly useful for various use cases. However, to better facilitate real-time analytics, we propose the addition of a 10-second execution frequency option. This would enable users to run jobs more frequently, capturing data in near real-time and providing immediate insights.
The SCHEDULE statement is a powerful tool for defining when and how often a job should be executed, whether it's a one-time task or a recurring one. The interval parameter within the SCHEDULE statement is particularly important as it dictates the frequency of job execution. It currently supports intervals in days, hours, minutes, and weeks, with examples such as:
1 DAY: Execute the job once every day.
1 HOUR: Execute the job once every hour.
1 MINUTE: Execute the job once every minute.
1 WEEK: Execute the job once every week.
Our proposed enhancement would add another option to this list:
10 SECONDS: Execute the job once every 10 seconds.
This addition would be invaluable for users who require high-frequency data processing and analysis, such as in financial trading, network monitoring, or any application where rapid response to data changes is critical.
We believe that this feature would significantly enhance the capabilities of Doris, making it an even more versatile and powerful tool for data management and analysis.
Thank you for considering this feature request. We look forward to the possibility of seeing this enhancement in future releases of Doris.
Best regards
Use case
specifically to accommodate real-time metric analysis
Search before asking
Description
Dear Doris Development Team,
I hope this message finds you well. I am writing to request a feature enhancement for the CREATE-JOB functionality within Doris, specifically to accommodate real-time metric analysis.
Currently, the CREATE-JOB feature allows for the scheduling of jobs with specific execution intervals, which is incredibly useful for various use cases. However, to better facilitate real-time analytics, we propose the addition of a 10-second execution frequency option. This would enable users to run jobs more frequently, capturing data in near real-time and providing immediate insights.
The SCHEDULE statement is a powerful tool for defining when and how often a job should be executed, whether it's a one-time task or a recurring one. The interval parameter within the SCHEDULE statement is particularly important as it dictates the frequency of job execution. It currently supports intervals in days, hours, minutes, and weeks, with examples such as:
1 DAY: Execute the job once every day.
1 HOUR: Execute the job once every hour.
1 MINUTE: Execute the job once every minute.
1 WEEK: Execute the job once every week.
Our proposed enhancement would add another option to this list:
10 SECONDS: Execute the job once every 10 seconds.
This addition would be invaluable for users who require high-frequency data processing and analysis, such as in financial trading, network monitoring, or any application where rapid response to data changes is critical.
We believe that this feature would significantly enhance the capabilities of Doris, making it an even more versatile and powerful tool for data management and analysis.
Thank you for considering this feature request. We look forward to the possibility of seeing this enhancement in future releases of Doris.
Best regards
Use case
specifically to accommodate real-time metric analysis
Related issues
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: