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

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

This issue was marked "stale-assigned" and has not received a public comment in 
7 days. It is now automatically unassigned. If you are still working on it, you 
can assign it to yourself again. Please also give an update about the status of 
the work.

> 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: P2
>
> 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)

Reply via email to