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

ASF GitHub Bot commented on CALCITE-1948:
-----------------------------------------

Github user F21 commented on the issue:

    https://github.com/apache/calcite-avatica/pull/35
  
    Thanks for the review @joshelser. I ran into the issue with dependent 
images before as well. I think a script as you mentioned in the best way. 
Perhaps we can even use our CI to run the script when a tag is created for 
automation.


> Publish avatica-hypersql, avatica-mysql and avatica-postgres to docker hub
> --------------------------------------------------------------------------
>
>                 Key: CALCITE-1948
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1948
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>            Reporter: Francis Chuang
>            Assignee: Josh Elser
>            Priority: Major
>
> I am currently making a port of the tests in calcite-avatica-go to test 
> against the calcite-avatica image in docker hub.
> Unfortunately, the calcite-avatica image only includes the avatica-server, 
> which makes it difficult to stand up a test environment.
> It would be nice if the docker images for HyperSQL, MySQL and Postgres can be 
> published as well.
> This can be achieved by configuring docker hub's automatic build to look in 
> the appropriate subfolders for the dockerfile and push tags with the 
> appropriate backing db, for example 1.10.0-hypersql, 1.10.0-mysql etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to