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

Use of quarkus-agroal with GCP CloudSQL #5901

Closed
wants to merge 602 commits into from
Closed

Use of quarkus-agroal with GCP CloudSQL #5901

wants to merge 602 commits into from

Conversation

jtama
Copy link
Contributor

@jtama jtama commented Dec 2, 2019

This pull request contains code to ease the use of GCP CloudSQL as well as documentation to use it without any code amendments.

@Sanne
Copy link
Member

Sanne commented Dec 2, 2019

hey, many thanks for proposing this. It's exciting to see more support for CGP!

I hope you could help me figure out if we can make it really easy and slick to run on GCP, so without needing any additional configuration flags? Please see my review comments for details.

It would also be great as to not have configuration properties which only apply to a single cloud.

@jtama
Copy link
Contributor Author

jtama commented Dec 3, 2019

Links to #5824

@jtama jtama requested a review from Sanne December 10, 2019 08:07
@jtama
Copy link
Contributor Author

jtama commented Dec 13, 2019

Hi,
@Sanne I am not sure about the merge request process, do I need to do something more ?

@jtama jtama closed this Dec 13, 2019
@jtama jtama reopened this Dec 13, 2019
@Mihai-B
Copy link

Mihai-B commented Dec 23, 2019

After this is merged, in what version will it be available ?

throw new RuntimeException("Cloud sql instance should match the pattern project-id:zone:cloudSqlInstance");
}
agroalConnectionFactoryConfigurationSupplier.jdbcUrl(
MessageFormat.format("{0}?socketFactory=com.google.cloud.sql.postgres.SocketFactory&cloudSqlInstance={1}"
Copy link

Choose a reason for hiding this comment

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

The socketFactory is bound to postgres driver and if you would like to use a different driver is not possible with current implementation. Is it possible to make this configurable from a property as well ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Currently there are only two supported SGBD postgres and mysql, but yes I should make this configurable.

Copy link

Choose a reason for hiding this comment

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

But I think @Sanne is correct, this implementation is very GCP integrated. maybe we should switch a little bit the way we make the implementation for this.

I think the easiest way is to use the agroalConnectionFactoryConfigurationSupplier.jdbcProperty(<property_name>, <value>) method

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried this but it didn't worked. I will re-take a loot at it.

In fact I think I should create a separate extension for gcp sql datasources.

Copy link

Choose a reason for hiding this comment

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

Can you check: #6634 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it won't work (i tried this already)

Copy link

@Mihai-B Mihai-B left a comment

Choose a reason for hiding this comment

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

just added some ideas

gwenneg and others added 17 commits January 20, 2020 15:09
Co-authored-by: Stéphane Épardaud <[email protected]>
Do not enhance generic/abstract repos
Use proper generics resolution when looking up the repository type
arguments
This means both Servlet and standalone will both
use the main thread pool, and it will avoid Vert.x
blocked thread warnings. These warnings are useless
as blocking IO can potentially block a thread for
a long time if request or response is large and the
connection is slow.
sberyozkin and others added 23 commits January 20, 2020 15:10
Fatal error: Failed to leave the current IsolateThread context and to detach the current thread. (code 12)
- resolves #6396
- also add TemplateData#ignoreSubclasses()
@boring-cyborg boring-cyborg bot added area/core area/dependencies Pull requests that update a dependency file labels Jan 20, 2020
@jtama jtama requested a review from gsmet January 20, 2020 14:17
@gsmet
Copy link
Member

gsmet commented Apr 22, 2020

This PR is invalid and contains a lot of unrelated commits.

Closing. Please open a new PR to pursue this.

@gsmet gsmet closed this Apr 22, 2020
@gsmet gsmet added the triage/invalid This doesn't seem right label Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core area/dependencies Pull requests that update a dependency file triage/invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.