[
https://issues.apache.org/jira/browse/ARROW-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324577#comment-17324577
]
Matt Topol commented on ARROW-8621:
-----------------------------------
[~kszucs] This is the JIRA issue I was referring to on the arrow-dev mailing
list. If I knew more about how the tags are created in the release scripts I'd
offer to make the change myself. This would significantly improve keeping the
versioning the same across the different modules for languages.
Also with the addition of the go parquet library, this would involve both the
tags:
`go/arrow/v4.0.0` / `go/arrow/v4.0.0-rc0` for release candidates
`go/parquet/v4.0.0`
Thanks
> [Go] Add Module support by creating tags
> ----------------------------------------
>
> Key: ARROW-8621
> URL: https://issues.apache.org/jira/browse/ARROW-8621
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Go
> Reporter: Kyle Brandt
> Priority: Minor
>
> Arrow has a go.mod, but the go modules system expects a certain git tag for
> Go modules to work.
> Based on
> [https://github.com/golang/go/wiki/Modules#faqs--multi-module-repositories] I
> believe the tag would be
> {code}
> go/arrow/v0.17.0
> {code}
> Currently:
> {code}
> $ go get github.com/apache/arrow/go/arrow@v0.17.0
> go get github.com/apache/arrow/go/arrow@v0.17.0:
> github.com/apache/arrow/go/arrow@v0.17.0: invalid version: unknown revision
> go/arrow/v0.17.0
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
