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

Add quarkus table prefix prop #11074

Merged
merged 1 commit into from
Jul 30, 2020

Conversation

cpowicki
Copy link

This PR allows us to optionally set the org.quartz.jobStore.tablePrefix (quartz docs here) config property, as opposed to hardcoding 'QRTZ'.

This is useful for situations where there are multiple schedulers that need to use different sets of tables.

* Optional - defaults to `QRTZ_` if not specified.
* Ignored if using a `ram` store.
*/
@ConfigItem
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor but you should use defaultValue = "QRTZ_" in this annotation.

This has several advantages: you can drop the doc about the default value above and it being optional: it will be automatically documented. You can also simplify the configuration code below.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushed changes - thank you for the review!

@gsmet
Copy link
Member

gsmet commented Jul 30, 2020

Thanks! If you can get my comment applied soon, I'll try to get that one into 1.7.0.CR1 that I release today.

@cpowicki cpowicki force-pushed the quartz-table-prefix-prop branch from b81ca11 to 1c4e41a Compare July 30, 2020 16:36
@gsmet gsmet removed this from the 1.7.0.Final milestone Jul 30, 2020
Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thanks!

@gsmet gsmet merged commit 3b18de9 into quarkusio:master Jul 30, 2020
@gsmet gsmet added this to the 1.7.0.CR1 milestone Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants