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

Destination Oracle: custom JDBC parameters #10719

Closed
girarda opened this issue Feb 28, 2022 · 7 comments
Closed

Destination Oracle: custom JDBC parameters #10719

girarda opened this issue Feb 28, 2022 · 7 comments

Comments

@girarda
Copy link
Contributor

girarda commented Feb 28, 2022

Tell us about the problem you're trying to solve

Add support for Oracle Destinations to take in a JDBC URL Params input to specify any additional JDBC parameters for the connection.

This is a follow up to #10421
This is part of #9501

Describe the solution you’d like

AbstractJdbcDestination can already handle jdbc parameters via the jdbc_url_params field, but the OracleDestination spec does not specify that field. We should update the spec to support additional jdbc parameters for Oracle destination

@grishick
Copy link
Contributor

Hey team! Please add your planning poker estimate with ZenHub @tuliren @edgao @subodh1810

@pcsoni89
Copy link
Contributor

pcsoni89 commented May 4, 2022

Need to make changes under destination-oracle/OracleDestination.java class & spec.json file.

@oustynova
Copy link

Please add your planning poker estimate with ZenHub @pcsoni89

@grishick
Copy link
Contributor

What's the points estimate on this issue? IMHO Scoping Finished implies that we assigned the estimate.

@pcsoni89
Copy link
Contributor

pcsoni89 commented May 11, 2022

Tried setting up different source and GCS destination connector.
Not able to reproduce the issue (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch;).
Looks like there was some issue while entering value for Access ID/secret key/GCS Bucket Path parameters.
Able to create connection for GCS destination with MySQL source and data sync is done successfully.

@grishick
Copy link
Contributor

Tried setting up different source and GCS destination connector. Not able to reproduce the issue (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch;). Looks like there was some issue while entering value for Access ID/secret key/GCS Bucket Path parameters. Able to create connection for GCS destination with MySQL source and data sync is done successfully.

@pcsoni89 was this comment meant for a different issue? I don't see anything related to GCS, S3, or SignatureDoesNotMatch in this issue.

@pcsoni89
Copy link
Contributor

Hi @grishick ,
By mistake i added comment here from a different ticket.
Sorry for inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Scoping Finished
Development

No branches or pull requests

6 participants