aaltay commented on a change in pull request #13365:
URL: https://github.com/apache/beam/pull/13365#discussion_r558743540



##########
File path: website/www/site/content/en/blog/kafka-to-pubsub-example.md
##########
@@ -0,0 +1,89 @@
+---
+layout: post
+title:  "Example to ingest data from Apache Kafka to Google Cloud Pub/Sub"
+date:   2021-01-15 00:00:01 -0800
+categories:
+  - blog
+  - java
+authors:
+  - arturkhanin
+  - ilyakozyrev
+  - alexkosolapov
+---
+<!--
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+In this blog post we present an example that creates a pipeline to read data 
from a single topic or
+multiple topics from [Apache Kafka](https://kafka.apache.org/) and write data 
into a topic
+in [Google Pub/Sub](https://cloud.google.com/pubsub). The example provides 
code samples to implement
+simple yet powerful pipelines and also provides an out-of-the-box solution 
that you can just _"
+plug'n'play"_.
+
+This end-to-end example is included
+in [Apache Beam release 
2.27](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12349380)

Review comment:
       For 2.27.0 - I would suggest linking to 
https://beam.apache.org/blog/beam-2.27.0/ and adding a line item to that 
release post about this template.




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to