This code was developed outside of the ASF, so it’s possible that we need to go
through the IP clearance process [1]. Can a PMC member please figure out the
answer to that question, and answer on this list.
Has the Helm project given any indication whether they approve or disapprove of
the code
I did two tests this morning.
1. Docker Desktop was downgraded to 3.2.0/3.0.0, this problem still exists
2. Druid cluster successfully started based on 0.20.0 image on the same
macbook.
And I see there's a change about Docker file by #10506 (included in 0.21.0
release) which has something to do wi
Hi Senlan,
Thank you very much for your message and support. I have created a PR to do the
migration, referring to the experience of Apache Superset. FYI,
https://github.com/apache/druid/pull/11163 and
https://github.com/apache/superset/tree/master/helm/superset .
Regards,
Benedict Jin
On 202
Hi Suneet, thanks for your suggestion.
However, the Apache release policy [1] explicitly says the below.
> Before casting +1 binding votes, individuals are REQUIRED to download all
> signed source code packages onto their own hardware, verify that they meet
> all requirements of ASF policy on r
This vote is closed now. The vote result can be found in [1].
Jihoon
[1]
https://lists.apache.org/thread.html/rb6b649650d26ce2e3901d8bb38d06475f845b43a25f997ff40b3e50a%40%3Cdev.druid.apache.org%3E
On Mon, Apr 26, 2021 at 9:56 AM Jihoon Son wrote:
>
> Frank, thanks for looking into it.
>
> I'm
Thanks to everyone who participated in the vote! The vote has passed
with 3 binding +1s and 1 non-binding +1.
Clint Wylie: +1 (binding)
Atul Mohan: +1 (non-binding)
Jon Wei: +1 (binding)
Jihoon Son: +1 (binding)
-
To unsubscribe,
Frank, thanks for looking into it.
I'm not sure why it fails in your testing environment. But it seems
like an issue in running the docker image rather than an issue in the
image itself because it passed tests in other people's environment. As
a result, it doesn't seem a release blocker to me, so
Thanks @Benedict Jin,
It is a good idea to maintain the Druid Helm's Chart in the Apache repository.
Since "https://github.com/helm/charts"; repo has been deprecation, we can't
maintain the chart, and the k8s user can't find druid chart package from
"https://artifacthub.io/packages/search?page=1&
Thanks @Benedict Jin,
It is a good idea to maintain the Druid Helm's Chart in the Apache repository.
Since "https://github.com/helm/charts"; repo has been deprecation, we can't
maintain the chart, and the k8s user can't find druid chart package from
"https://artifacthub.io/packages/search?page=1&
Thanks Benedict,
It is a good idea to maintain the Druid Helm's Chart in the Apache repository.
Since "https://github.com/helm/charts"; repo has been deprecation, we can't
maintain the chart, and the k8s user can't find druid chart package from
"https://artifacthub.io/packages/search?page=1&ts_qu
I tried to start druid in docker on two MacBookPro(both are running BigSur
11.2.3), both failed due to the same reason.
To determine what happened, DRUID_DIRS_TO_CREATE was set in the environment
file to skip the directory creation so that druid nodes could start up,
and then I checked the directo
11 matches
Mail list logo
