You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/01 17:07:06 UTC

[jira] [Commented] (BEAM-4115) Go SDK - Vanity Import Path

    [ https://issues.apache.org/jira/browse/BEAM-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188670#comment-17188670 ] 

Beam JIRA Bot commented on BEAM-4115:
-------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> Go SDK - Vanity Import Path
> ---------------------------
>
>                 Key: BEAM-4115
>                 URL: https://issues.apache.org/jira/browse/BEAM-4115
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>    Affects Versions: Not applicable
>            Reporter: Robert Burke
>            Priority: P3
>
> Proposal Doc: [https://s.apache.org/go-beam-vanity-import]
> Go has the ability to specify custom import paths for a prefix of packages. This has benefits of avoiding generic GitHub paths, and avoids breaking users in the event of infrastructure events such as moving off of GitHub, or even splitting the repo into per language components.
>  
> Currently users need to import paths like:
>  
> import "[github.com/apache/beam/sdks/go/pkg/beam/io/textio|http://github.com/apache/beam/sdks/go/pkg/beam/io/textio]"
>  
> to get at SDK packages. If we implement this proposal, they would look like:
> import "[beam.apache.org/sdks/go/pkg/beam/io/textio|http://beam.apache.org/sdks/go/pkg/beam/io/textio]"
> which are a bit shorter, a bit more stable, and a bit nicer, with the benefits outlined above.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)