[
https://issues.apache.org/jira/browse/CALCITE-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446731#comment-15446731
]
Josh Elser commented on CALCITE-1364:
-------------------------------------
Thanks for the feedback, Julian.
bq. So I think you should make sure that
https://github.com/joshelser/avatica-hsqldb-docker is a valid Apache-licensed
open source project, with explicit license, notices, headers, and instructions.
Ya caught me ;) I need to clean up this stuff as well as the repo that I
created to support the older Avatica versions before I introduced that
standalone-server module to Avatica.
bq. We can't rely on https://hub.docker.com/ being always available but someone
should be able to achieve the same effect by forking your project.
My line of thinking was that we would have the Dockerfile available in Apache
source. People could build the image themselves -- this is a similar analogy to
Java source and jar files. I think of Docker Hub in the same way as I think of
Maven central in that regard -- a convenient canonical location to pull the
pre-built image from. As such, I was also hoping that users would have the
ability to {{docker pull apache/avatica-hsqldb:1.8.0}} (or similar).
That said, I wasn't explicit in writing, but there is a latent question with
filing this: is this something we want to own in Apache?
I admin that I'm not super excited about figuring out how to do this in Apache.
I can move must faster no my own :). However, my next steps here are to
automate running the TCK against these docker images (use docker swarm or
something to launch them, and create a new image to invoke the TCK
automatically). As such, I have an interest in making this simple execution
"owned" by Apache since the intended audience are the Apache developers
(although, it does not invalidate the ability for devs to run the TCK -- just
makes it harder). I am still thinking through this all.
> Bring Docker image for avatica-standalone-server into Apache
> ------------------------------------------------------------
>
> Key: CALCITE-1364
> URL: https://issues.apache.org/jira/browse/CALCITE-1364
> Project: Calcite
> Issue Type: Task
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: avatica-1.9.0
>
>
> I worked on making some Docker images for the standalone Avatica Server with
> HSQLDB.
> https://hub.docker.com/r/joshelser/avatica-hsqldb/
> These greatly simplify running the Avatica TCK and also provide a portable
> server that developers can use when testing custom Avatica clients.
> For >=1.9.0, we should an image into Avatica (upstream). There are a couple
> of open questions on my mind already:
> 1. What are the release-ability concerns (do we provide SNAPSHOT Dockerfiles
> but not built images as they may be interpreted as "releases")?
> 2. What ASF integrations exist (do we need to ask Infra for things?)
> 3. Are there any maven plugins we should consider for automation?
> (https://github.com/spotify/docker-maven-plugin)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
