Multiple kafka topics to BigQuery

[benitaclarissa]

Allow user to use 1 Dataflow for multiple Kafka topics and stream the messages to multiple BigQuery tables. Messages from a topic would be exported to one table.

Usage:

bootstrapServers=myhost:9092
inputTopicRegex=topicPrefix(.*)
outputTableRegexPattern=topicPrefix(.*)
outputTableReplacement=BigQueryProjectID:dataset.tblPrefix$1Suffix
javascriptTextTransformGcsPath=gs://mybucket/my_udf_file.js
javascriptTextTransformFunctionName=my_transform_function

Example:
you have 3 topics in Kafka, named: topicPrefixFirst, topicPrefixSecond, and topicPrefixThird
Messages from all topics would be streamed to 3 tables.

• Messages in topicPrefixFirst would be streamed to BigQueryProjectID:dataset.tblPrefixFirstSuffix
• Messages in topicSecondFirst would be streamed to BigQueryProjectID:dataset.tblPrefixSecondSuffix
• Messages in topicThirdFirst would be streamed to BigQueryProjectID:dataset.tblPrefixThirdSuffix

I know this modification is still far from perfect. But, I am very glad to hear your suggestions and advice so we could make it perfect together.

Thanks in advance

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[benitaclarissa]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.