-
Notifications
You must be signed in to change notification settings - Fork 710
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
Comma no longer works in schedule (cron syntax) #299
Comments
Can you show the cron expression you use? |
Sure: "0 5,35 * * * ?" gives the error, but the "0 35 * * * ?" works fine |
I have added a "comma test" in JDBC river 1.3.0.1 with your expression, it works fine. |
I had the same issue. As a workaround I had used an array of cron expression as the schedule params support this. |
Is the comma issue on Windows? |
@jprante no. Its occuring in linux as well. sorry for the delayed response |
Just confirming that I'm seeing the same issue with the latest elasticsearch-river-jdbc-1.4.0.8 "schedule": "0 1,16,31,46 * * * ? *", |
Comma no longer works in schedule (cron syntax).
java.lang.IllegalArgumentException: invalid cron expression format: Unexpected end of expression
at org.xbib.cron.CronExpression.buildExpression(CronExpression.java:287)
at org.xbib.cron.CronExpression.(CronExpression.java:101)
at org.xbib.elasticsearch.plugin.feeder.AbstractFeeder.schedule(AbstractFeeder.java:177)
at org.xbib.elasticsearch.plugin.river.jdbc.JDBCRiver.start(JDBCRiver.java:94)
at org.elasticsearch.river.RiversService.createRiver(RiversService.java:148)
The text was updated successfully, but these errors were encountered: