youngoli commented on a change in pull request #13456: URL: https://github.com/apache/beam/pull/13456#discussion_r539644754
########## File path: website/www/site/content/en/blog/splittable-do-fn-is-available.md ########## @@ -0,0 +1,88 @@ +--- +title: "Splittable DoFn in Apache Beam is Ready to Use" +date: 2020-12-16 00:00:01 -0800 +categories: + - blog +aliases: + - /blog/2020/12/16/splittable-do-fn-is-available.html +authors: + - boyuanzz +--- +<!-- +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 2017, [Splittable DoFn Blog Post](https://beam.apache.org/blog/splittable-do-fn/) proposed +to build [Splittable DoFn](https://s.apache.org/splittable-do-fn) APIs as the new recommended way of +building I/O connectors. Splittable DoFn is a generalization of `DoFn` that gives it the core +capabilities of `Source` while retaining `DoFn`'s syntax, flexibility, modularity, and ease of +coding. Thus, it becomes much easier to develop complex I/O connectors with simpler and reusable +code. Review comment: It's moreso to help the flow of the post. It makes sense to go background info -> main point -> details. Plus, from my experience it's relatively common for articles/blog posts to restate the title. So while the title is great, I still think having this sentence helps. ---------------------------------------------------------------- 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]
