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

Adding fetch configuration option to hibernate-orm module #11950

Merged
merged 1 commit into from
Sep 19, 2020

Conversation

mkrzywanski
Copy link

This pull request should resolve #11527. New fetch configuration category has been added. If those properties are not set, fallback for older depracted properties is done (if configured).

@machi1990 machi1990 requested review from gsmet and Sanne September 8, 2020 10:28
@machi1990
Copy link
Member

@gsmet @Sanne would you have some cycle to review this one?

* @asciidoclet
*/
@ConfigItem(defaultValue = "-1")
public int batchFetchSize;

Choose a reason for hiding this comment

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

Does this make the property name .fetch.batch-fetch-size? Can we eliminate the redundancy and call it .fetch.batch-size?

Copy link
Author

Choose a reason for hiding this comment

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

Yes, new properties' names would be .fetch.batch-fetch-size and .fetch.max-fetch-depth. I am okay with removing the fetch keyword as far as redundancy is concerned. Shall we also do the same for maxFetchDepth so that it is .fetch.max-depth ?

Choose a reason for hiding this comment

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

Right, I mean for both of them.

Copy link
Member

Choose a reason for hiding this comment

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

@mkrzywanski can you adjust the names and squash everything?

Thanks!

Copy link
Author

Choose a reason for hiding this comment

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

@gsmet done.

@mkrzywanski mkrzywanski force-pushed the issue-11527 branch 3 times, most recently from 68a1dd2 to 6f0e2b7 Compare September 14, 2020 18:41
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.

This one looks good to go. I rebased and force pushed, let's wait for CI and merge.

Thanks!

@gsmet gsmet added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Sep 18, 2020
@gsmet gsmet added this to the 1.9.0 - master milestone Sep 18, 2020
@gsmet gsmet merged commit 5613ea6 into quarkusio:master Sep 19, 2020
@gsmet
Copy link
Member

gsmet commented Sep 19, 2020

Merged, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/waiting-for-ci Ready to merge when CI successfully finishes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a new config category quarkus.hibernate-orm.fetch
5 participants