mirror of
https://github.com/apache/impala.git
synced 2026-01-10 09:00:16 -05:00
The containers are essentially the same except for -is_executor and -is_coordinator flags and the open ports (executors don't need to expose HS2 and Beeswax). Over time we may want to specialize the configurations further. Building separate containers on top of impala_base is lightweight enough and this a) reduces the amount of configuration required and b) makes it clear which ports should open. It will also nudge people in the direction of using dedicated coordinators and executors in Kubernetes, which I believe is the right approach. The previous impalad container was renamed to impalad_coord_exec to be unambiguous. Change-Id: I22f8ded167179478d7556f612b8b3e9d1b019a7a Reviewed-on: http://gerrit.cloudera.org:8080/12228 Reviewed-by: Tim Armstrong <tarmstrong@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>