Skip to content

Kafka to PubSub template #176

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

Merged

Conversation

KhaninArtur
Copy link
Contributor

This PR adds Kafka to PubSub Flex template.

@google-cla
Copy link

google-cla bot commented Oct 6, 2020

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no The PR submitter does not have a CLA label Oct 6, 2020
@ilya-kozyrev
Copy link
Contributor

@googlebot I fixed it.

@google-cla
Copy link

google-cla bot commented Oct 6, 2020

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@ilya-kozyrev
Copy link
Contributor

@googlebot I consent.

@google-cla google-cla bot added cla: yes The PR submitter has a CLA and removed cla: no The PR submitter does not have a CLA labels Oct 6, 2020
Copy link
Contributor

@prathapreddy123 prathapreddy123 left a comment

Choose a reason for hiding this comment

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

Didn't notice any changes based on review comments but however marked as fixed. Please revisit all review comments.

@KhaninArtur
Copy link
Contributor Author

@prathapreddy123, hi, thank you very much for your review! It helps us a lot.
Seems like something went wrong with changes notices, sorry for that. Could you please take a look at these commits:

  1. We tried to resolve your comments here.
  2. After your review we added new functionality, could you please take a look at the last actual version of the PR.

@google-cla
Copy link

google-cla bot commented Oct 15, 2020

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no The PR submitter does not have a CLA and removed cla: yes The PR submitter has a CLA labels Oct 15, 2020
@AKosolapov
Copy link
Contributor

@googlebot I fixed it.

@google-cla google-cla bot added cla: yes The PR submitter has a CLA and removed cla: no The PR submitter does not have a CLA labels Oct 15, 2020
@KhaninArtur KhaninArtur changed the title (WIP) Kafka to PubSub template Kafka to PubSub template Oct 26, 2020
Copy link
Contributor

@prathapreddy123 prathapreddy123 left a comment

Choose a reason for hiding this comment

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

Thanks for addressing earlier comments. Left few additional comments.

Copy link
Contributor

@prathapreddy123 prathapreddy123 left a comment

Choose a reason for hiding this comment

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

Thanks for addressing all changes.

Copy link
Contributor

@prathapreddy123 prathapreddy123 left a comment

Choose a reason for hiding this comment

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

I do see limited options for scope of unit tests. Can you check if any tests can be added.
Note: Unit tests should not have any external resource dependencies (e.g: GCS, Pub/Sub)

@KhaninArtur
Copy link
Contributor Author

I do see limited options for scope of unit tests. Can you check if any tests can be added.
Note: Unit tests should not have any external resource dependencies (e.g: GCS, Pub/Sub)

I've checked and managed to add unit tests for Utils.

Copy link
Contributor

@prathapreddy123 prathapreddy123 left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution.

@prathapreddy123 prathapreddy123 added the Google LGTM Approval of a pull request to be merged into the repository label Nov 17, 2020
@google-cla google-cla bot added cla: yes The PR submitter has a CLA and removed cla: no The PR submitter does not have a CLA labels Nov 20, 2020
@KhaninArtur KhaninArtur force-pushed the KafkaToPubsubTemplate branch from 7aceebf to 5603d21 Compare November 20, 2020 13:44
@google-cla
Copy link

google-cla bot commented Nov 20, 2020

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no The PR submitter does not have a CLA and removed cla: yes The PR submitter has a CLA labels Nov 20, 2020
Copy link
Member

@sabhyankar sabhyankar left a comment

Choose a reason for hiding this comment

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

Hello - Please add the missing license headers, rebase and squash commits so we can try this again.

@@ -0,0 +1,70 @@
package com.google.cloud.teleport.v2.templates;
Copy link
Member

Choose a reason for hiding this comment

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

Please add a license header.

@@ -0,0 +1,32 @@
package com.google.cloud.teleport.v2.templates;
Copy link
Member

Choose a reason for hiding this comment

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

Please add a license header.

@@ -0,0 +1,151 @@
package com.google.cloud.teleport.v2.kafka.consumer;
Copy link
Member

Choose a reason for hiding this comment

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

Please add a license header.

@sabhyankar sabhyankar removed the Google LGTM Approval of a pull request to be merged into the repository label Nov 20, 2020
Co-authored-by: Ilya Kozyrev <[email protected]>
Co-authored-by: Alex Kosolapov <[email protected]>
@KhaninArtur KhaninArtur force-pushed the KafkaToPubsubTemplate branch from 5603d21 to 13570b5 Compare November 20, 2020 15:37
@google-cla
Copy link

google-cla bot commented Nov 20, 2020

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@KhaninArtur
Copy link
Contributor Author

Hello - Please add the missing license headers, rebase and squash commits so we can try this again.

@sabhyankar Added missing licenses

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@sabhyankar
Copy link
Member

Thank you @KhaninArtur - Can you also see if "[email protected]" can sign the CLA since they are one of the commit authors?

@KhaninArtur
Copy link
Contributor Author

@googlebot I fixed it.

@google-cla
Copy link

google-cla bot commented Nov 20, 2020

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@AKosolapov
Copy link
Contributor

@googlebot I consent.

@google-cla
Copy link

google-cla bot commented Nov 20, 2020

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: yes The PR submitter has a CLA and removed cla: no The PR submitter does not have a CLA labels Nov 20, 2020
@KhaninArtur
Copy link
Contributor Author

@sabhyankar done.

@ilya-kozyrev
Copy link
Contributor

@googlebot I consent.

@google-cla
Copy link

google-cla bot commented Nov 20, 2020

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

Copy link
Member

@sabhyankar sabhyankar left a comment

Choose a reason for hiding this comment

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

LGTM

Thank you all!

@sabhyankar sabhyankar added the Google LGTM Approval of a pull request to be merged into the repository label Nov 20, 2020
prathapreddy123 pushed a commit that referenced this pull request Dec 3, 2020
Please approve this CL. It will be submitted automatically, and its GitHub pull request will be marked as merged.

Imported from GitHub PR #176

This PR adds Kafka to PubSub Flex template.

Copybara import of the project:

  - 7aceebf9219d17becb789b6ccff647ee6ded6420 Implemented Kafka to Pub/Sub template by Artur Khanin <[email protected]>

COPYBARA_INTEGRATE_REVIEW=#176 from akvelon:KafkaToPubsubTemplate 7aceebf9219d17becb789b6ccff647ee6ded6420
PiperOrigin-RevId: 343484865
@prathapreddy123 prathapreddy123 merged commit 3c1cda6 into GoogleCloudPlatform:master Dec 3, 2020
ryanmcdowell pushed a commit that referenced this pull request Dec 3, 2020
Please approve this CL. It will be submitted automatically, and its GitHub pull request will be marked as merged.

Imported from GitHub PR #176

This PR adds Kafka to PubSub Flex template.

PiperOrigin-RevId: 345486564
asthamohta pushed a commit that referenced this pull request Apr 23, 2025
* Wide Row IT for Forward Migration (#170)

* Added Missing Datastream Private Connectivity

* Review comments fixes (#176)

* Move to generic to Base Class

* Rename method

* Moved Spanner Check to base class

* Added Ignore For 5000 Tables

* FM code Refactored (#188)

* Added FM Low Priority WIde Row Fixws

* Added Code Refectored

* Code Refecoting Fixes

* removed 5K table test

fix compilation error

* revert changes

* Added IT PR Stuck Fixes and Ignore 100MB test as it is holding our Pipeline

* removed 100MB flaky test

---------

Co-authored-by: taherkl <[email protected]>
Co-authored-by: Akash Thawait <[email protected]>
ron-gal pushed a commit to ron-gal/DataflowTemplates that referenced this pull request Apr 25, 2025
* Wide Row IT for Forward Migration (GoogleCloudPlatform#170)

* Added Missing Datastream Private Connectivity

* Review comments fixes (GoogleCloudPlatform#176)

* Move to generic to Base Class

* Rename method

* Moved Spanner Check to base class

* Added Ignore For 5000 Tables

* FM code Refactored (GoogleCloudPlatform#188)

* Added FM Low Priority WIde Row Fixws

* Added Code Refectored

* Code Refecoting Fixes

* removed 5K table test

fix compilation error

* revert changes

* Added IT PR Stuck Fixes and Ignore 100MB test as it is holding our Pipeline

* removed 100MB flaky test

---------

Co-authored-by: taherkl <[email protected]>
Co-authored-by: Akash Thawait <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes The PR submitter has a CLA Google LGTM Approval of a pull request to be merged into the repository
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants