Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

elasticsearch-croneval shouldn't dump a stacktrace for invalid patterns #49642

Closed
pugnascotia opened this issue Nov 27, 2019 · 2 comments
Closed

Comments

@pugnascotia
Copy link
Contributor

Elasticsearch version

7.4.2, master

Description of the problem including expected versus actual behavior:

When elasticsearch-croneval is run with a malformed cron pattern, it dumps a stacktrace to the terminal.

The tool ought to simply report that the pattern is malformed and either direct the user to the documentation or print a brief summary of the expected input (I'd vote for the latter).

Steps to reproduce:

  1. `bin/elasticsearch-croneval "*"
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Watcher)

@gaobinlong
Copy link
Contributor

Hi @pugnascotia , this issue can be closed as the related PR #49744 has been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants