[
https://issues.apache.org/jira/browse/ARROW-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17387392#comment-17387392
]
Matt Topol commented on ARROW-8621:
-----------------------------------
[~kou] To my knowledge, because the go.mod is not at the root of the repo, we
have to use the `go/arrow/v${VERSION}` format in order for it to get recognized
by go.
Even if pointing at the individual tags like that did work, it would prevent
being able to use `go get -u github.com/apache/arrow/go/arrow` to
upgrade/update the dependency and wouldn't show the versions on pkg.go.dev for
the docs. All in all, we are going to want to create two tags:
go/arrow/v${VERSION}
go/parquet/v${VERSION} (now that i've been merging in the parquet
implementation for Go).
> [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/[email protected]
> go get github.com/apache/arrow/go/[email protected]:
> github.com/apache/arrow/go/[email protected]: invalid version: unknown revision
> go/arrow/v0.17.0
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
