calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From risdenk <>
Subject [GitHub] calcite-avatica pull request #3: CALCITE-1364 Docker images for an avatica s...
Date Wed, 05 Apr 2017 20:41:00 GMT
Github user risdenk commented on a diff in the pull request:
    --- Diff: docker/ ---
    @@ -0,0 +1,46 @@
    +{% comment %}
    +Licensed to the Apache Software Foundation (ASF) under one or more
    +contributor license agreements.  See the NOTICE file distributed with
    +this work for additional information regarding copyright ownership.
    +The ASF licenses this file to you under the Apache License, Version 2.0
    +(the "License"); you may not use this file except in compliance with
    +the License.  You may obtain a copy of the License at
    +Unless required by applicable law or agreed to in writing, software
    +distributed under the License is distributed on an "AS IS" BASIS,
    +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +See the License for the specific language governing permissions and
    +limitations under the License.
    +{% endcomment %}
    +This module contains a number of Docker images to ease testing of
    +Avatica clients against a known-server.
    +## Docker
    +`src/main/docker` contains a number of Docker images and Docker-compose
    +configuration files to launch a standalone-Avatica server. Maven automation
    +exists for the base Docker image "avatica-server" which can be invoked with
    +the "-Pdocker" Maven profile.
    +The other Docker images must be built by hand.
    +### Provided Images
    +A number of Docker images for different databases are provided. Presently, they include:
    --- End diff --
    Not sure images is the correct term here. Dockerfiles maybe? Because the images must be

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message