homatthew opened a new pull request, #3758: URL: https://github.com/apache/gobblin/pull/3758
Dear Gobblin maintainers, Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below! ### JIRA - [X] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR" - https://issues.apache.org/jira/browse/GOBBLIN-XXX ### Description - [ ] Here are some details about my PR, including screenshots (if applicable): Kafka source is commonly used to ETL from Kafka to HDFS as part of Fast Ingest. This data is later exposed via Hive / Iceberg to be queried via Spark / Trino. Hive does not support `.` to be part of the table name. This means that in order to keep consistency between Hive and Kafka names, it requires some conversion. This is a high toil and low reward process. It would be great to have a flag to just outright ignore these topics altogether. Especially if the Gobblin operator does not control who creates Kafka topics. ### Tests - [X] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: <img width="394" alt="image" src="https://github.com/apache/gobblin/assets/35702680/8d2c95ad-d6da-426d-ba35-ee1f0eca1a45";> ### Commits - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 2. Subject is limited to 50 characters 3. Subject does not end with a period 4. Subject uses the imperative mood ("add", not "adding") 5. Body wraps at 72 characters 6. Body explains "what" and "why", not "how" -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
