Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

> > Let's collect all the platforms that have reported having problems, create > a table for it at GitHub, and check whether they have fixed or not? > I agree we should file individual docker issues *with detailed environment and steps to reproduce*. However, I don't think this should be discussed

Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

Hi Frank, Let's collect all the platforms that have reported having problems, create a table for it at GitHub, and check whether they have fixed or not? Kind Regards, Furkan KAMACI On Tue, May 25, 2021 at 2:07 PM frank chen wrote: > Hi Xavier, > > I have a question, does the problem reported b

Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

Hi Xavier, I have a question, does the problem reported by Clint could be reproduced when executing the k8s integration test ? Thanks. Xavier Léauté 于2021年5月21日周五 下午11:41写道： > > I agree with you that the root cause is lack of some automated tests > > against released docker images. > > > > Sin

Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

Hi all, Whether or not we release the RC1, we have to resolve the issues ASAP. I have submitted a PR https://github.com/apache/druid/pull/11299 , and I'm still testing these changes on different platforms(macOS and centos). But since the reported problems are platform-related, any help to verify t

Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

Do we see Unable to use AWS Fargate bind mounts with Dockerfile · Issue #11278 · apache/druid (github.com) as a regression test failure for https://github.com/apache/druid/pull/11167 Furkan KAMACI 于2021年5月25日周二 下午3:31写道： > Hi, > > Here is my opinio

Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

Hi, Here is my opinion: Druid has had problems with docker for a while now. We use Druid on a dockerized environment and manually solve this problem via setting permissions. It is not a blocker issue, and we can release the artifact. However, this is a bugfix release that aims to cover Docker vo

Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

I agree that this probably isn't a blocker, but also agree based on the number of reports that we should consider either fixing so that the docker-compose quickstart instructions work as is, or adjust the docs so that the instructions at least include something about setting the permissions so that