[
https://issues.apache.org/jira/browse/CALCITE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120734#comment-16120734
]
Josh Elser commented on CALCITE-1240:
-------------------------------------
bq. CI is important, but let's deal with it in a separate case. I think adding
Apache headers is the only change necessary before this PR can go in.
Agreed.
bq. Jenkins uses a jenkinsfile which is stored in the project repo, but I do
not see the jenkinsfile in the calcite or kafka repos. How are builds
configured?
You can do it this route if you'd like, but I don't have much experience. For
the other Jenkins jobs for Calcite and Avatica, I've just created the jobs by
hand. It is just an administrative task to get you an account.
I believe there's at least one person in HBase who has experience doing this
against their master branch.
> Avatica client written in Golang
> --------------------------------
>
> Key: CALCITE-1240
> URL: https://issues.apache.org/jira/browse/CALCITE-1240
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Add a client for Avatica written in the Go language (aka "Golang").
> There is one at https://github.com/Boostport/avatica and the author has
> offered to contribute it.
> The driver is currently somewhat specialized for Phoenix but our goal should
> be to allow it to work against any Avatica provider (without diminishing its
> value to Phoenix users).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
