This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push: new e7eb80d Publishing website 2020/03/27 19:03:41 at commit 2b3180e e7eb80d is described below commit e7eb80d29307c029cd91d1be95429bc6d58d65b5 Author: jenkins <bui...@apache.org> AuthorDate: Fri Mar 27 19:03:41 2020 +0000 Publishing website 2020/03/27 19:03:41 at commit 2b3180e --- .../generated-content/roadmap/go-sdk/index.html | 35 ++++++++++++---------- 1 file changed, 20 insertions(+), 15 deletions(-) diff --git a/website/generated-content/roadmap/go-sdk/index.html b/website/generated-content/roadmap/go-sdk/index.html index 73a15f0..bc401db 100644 --- a/website/generated-content/roadmap/go-sdk/index.html +++ b/website/generated-content/roadmap/go-sdk/index.html @@ -228,7 +228,6 @@ <ul class="nav"> <li><a href="#usability">Usability</a></li> - <li><a href="#performance">Performance</a></li> <li><a href="#integrating-with-the-go-ecosystem">Integrating with the Go ecosystem</a></li> <li><a href="#implement-portability-features">Implement Portability features</a></li> </ul> @@ -257,26 +256,32 @@ limitations under the License. by the status of the <a href="https://beam.apache.org/roadmap/portability/">Beam Portabillity Framework</a> and the existence of portable runners.</p> -<p>With that in mind present work on the Go SDK has the following goals:</p> - -<h2 id="usability">Usability</h2> - -<p>The Go SDK should not block users from writing the pipelines they need to run.</p> +<p><strong>April 2020 Update</strong> +This year we hope to move the SDK out of experimental at least for Batch usage.</p> +<p>To do so, there are a few blocking changes:</p> <ul> - <li>Support large elements <a href="https://issues.apache.org/jira/browse/BEAM-4124">BEAM-4124</a></li> - <li>Coder Registry to support complex user elements <a href="https://issues.apache.org/jira/browse/BEAM-3306">BEAM-3306</a></li> + <li>Support Interoperability with other SDKs</li> + <li>Scalable IOs</li> + <li>Portability Proto stability</li> + <li>Go Ecosystem integration improvements</li> </ul> -<h2 id="performance">Performance</h2> +<p>Interoperability while not a blocking feature in itself, requires Beam Schema support, which +the SDK could then use as it’s default coder. Batch Splittable DoFns are nearly ready for +playing with on Flink, and the Python Direct Runner, answering the scalable batch IO question. +There’s much work getting the portability protos to a stable baseline. This will allow runner +and SDK independance, so they don’t need to be updated in lockstep. Finally, the Go SDK should +adopt Go Modules as it’s versioning solution, and officially “catch up” with the current beam +version.</p> -<p>Since the Go SDK has no official runner support at this time, this gives us the chance to work on the performance -of the SDK harness. When portable runners are ready, the Go SDK should be ready as well.</p> +<p>The Go SDK has the following goals for the next few months:</p> + +<h2 id="usability">Usability</h2> <ul> - <li>Reducing framework overhead on the SDK Harness side <a href="https://issues.apache.org/jira/browse/BEAM-4726">BEAM-4726</a></li> - <li>Tooling to enable and verify pipeline performance <a href="https://issues.apache.org/jira/browse/BEAM-3612">BEAM-3612</a></li> - <li>Measure the performance of the SDK at scale.</li> + <li>Beam Schema Support <a href="https://issues.apache.org/jira/browse/BEAM-4124">BEAM-9615</a></li> + <li>Improvements to starcgen <a href="https://issues.apache.org/jira/browse/BEAM-9616">BEAM-9616</a></li> </ul> <h2 id="integrating-with-the-go-ecosystem">Integrating with the Go ecosystem</h2> @@ -316,7 +321,7 @@ Contributions are welcome. Please contact the <a href="mailto:d...@beam.apache.or for assistance in finding a place to help out.</p> <ul> - <li>JIRA: <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20component%20%3D%20sdk-go">sdk-go</a> / <a href="https://issues.apache.org/jira/browse/BEAM-2083">BEAM-2083</a></li> + <li>JIRA: <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20component%20%3D%20sdk-go">sdk-go</a></li> <li>Contact: Robert Burke (@lostluck) <a href="mailto:lostl...@apache.org?subject=%5BGo%20SDK%20Roadmap%5D">Email</a> - Please also cc the d...@beam.apache.org list. I strongly prefer public discussion of Go SDK matters.</li> </ul>