[CRON] Broken: apache/druid#39260 (master - cc10350)
Build Update for apache/druid - Build: #39260 Status: Broken Duration: 1 hr, 24 mins, and 35 secs Commit: cc10350 (master) Author: cristian-popa Message: Collocated processes instructions (#13224) Co-authored-by: Victoria Lim Co-authored-by: Frank Chen View the changeset: https://github.com/apache/druid/compare/6aca61763ef16f232c0059c4eaade0e59acf774a...cc10350870dbe22f74aef0bb500c6e7894b916dd View the full build log and details: https://app.travis-ci.com/github/apache/druid/builds/256783355?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/druid repository going to https://app.travis-ci.com/account/preferences/unsubscribe?repository=16806911&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://app.travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Re: [DISCUSS] Release 24.0.1
Thank you for volunteering! On Mon, Oct 17, 2022 at 7:00 AM Kashif Faraz wrote: > Hi Abhishek > > If you haven't started with the release process already, I would like to > volunteer to perform this release so that we can expedite it. > Please let me know if that works for you. > > Regards > Kashif > > On Mon, Sep 26, 2022 at 3:41 PM Abhishek Agarwal < > abhishek.agar...@imply.io> > wrote: > > > Hi All, > > Recently we discovered a regression ( > > https://github.com/apache/druid/pull/13138) in the 24.0.0 release. > Because > > of this regression, Hadoop ingestion will not work if the user has > > overridden any of the `druid.extensions.*` config. Some examples below > > - If a custom load list is specified, Hadoop ingestion task will still > pick > > up all the extensions in "extension" directory. > > - If a custom Hadoop dependency directory is being used, those jars will > no > > longer be available for Hadoop Ingestion. > > > > I have created a branch https://github.com/apache/druid/tree/24.0.1 to > > backport the hotfix. We can also choose to backport some other bug fixes > > that we missed in 24.0.0. Though, of course, we want to backport only > > critical bug fixes. > > >
Re: [E] Re: Apache Druid Slack
What should we do about Slack canceling message history for free tier? Perhaps we should export history elsewhere? On Thu, Jan 27, 2022 at 1:10 PM Vadim Ogievetsky wrote: > Alright, I have setup the new Slack workspace and updated the link on > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=hV9FPFkuEXDmMbTGo3m_iqUc-baVKjOHznj9kig1I1Q&e= > to point to it. > Please join with the > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_join-2Dslack&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=07e2sPTwojKxi997mSN4a5Ktcr1lyHcekXuTwEZj9JY&e= > link (and share it with others). > Sadly there is no way to migrate content from one Slack workspace to > workspace, I am sure we will fill the new channel with great content very > quickly! > > On 2022/01/20 18:15:23 Vadim Ogievetsky wrote: > > I think that the PMC should create a new Slack channel for Apache Druid > and > > shift the community towards using it away from the ASF Slack. I volunteer > > to do this on the PMCs behalf and do all the setup/admin work. I would > > share admin access with any PMC member. > > > > What is the motivation for this? > > > > As you may have heard, it’s become increasingly difficult for new users > > without an @apache.org email address to join the ASF #druid Slack > channel. > > ASF Infra disabled the option to publicly provide a link to the workspace > > to anyone who wanted it, after encountering issues with spammers. > > > > Per Infra’s guidance ( > https://urldefense.proofpoint.com/v2/url?u=https-3A__infra.apache.org_slack.html&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=qZfDyv1d4QnrCrEjvTgSbm8qeEj-B-dFWKil2k4XOyQ&e= > ), new community > > members should only be invited as single-channel guests. Unfortunately, > > single-channel guests are unable to extend invitations to new members, > > including their colleagues who are using Druid. Only someone with full > > member privileges is able to extend an invitation to new members. This > lack > > of consistency doesn’t make the community feel inclusive. > > > > There is a workaround in place ( > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_druid-2Dwebsite-2Dsrc_pull_278&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=LZAv4yoEkFJcPmJckcAR0xXyuo7V81ZfR2X_jxQjH58&e= > ) – users can send an > > email to druid-u...@googlegroups.com to request an invite to the Slack > > channel from an existing member – but this still poses a barrier to > entry, > > and isn’t a viable permanent solution. It also creates potential privacy > > issues as not everyone is at liberty to announce they’re using Druid nor > > wishes to display their email address in a public forum. > > > > I propose we make our own free Slack channel for Apache Druid and > encourage > > people to migrate to it. Then we can have our own policy on Slack > > invitations - I would like to restore the ability for anyone on the web > to > > join our Slack. > > > > This is not a 100% original idea, in fact this is what other Apache > > projects have done, notably Apache Pinot (see "join our slack" on > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__pinot.apache.org_&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=GYTpyHD-1U_Er2eKNXk41b9aiy4zW9EtCt-2YXxSh9o&e= > ). I propose we do the same. > > > > Vadim > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
Re: [E] Re: Apache Druid Slack
I recently learned about Apache Flink making slack conversations google indexable through linen.dev. That might be worth exploring. Does anyone know how it works? On Wed, Oct 19, 2022 at 4:18 AM Eyal Yurman wrote: > What should we do about Slack canceling message history for free tier? > > Perhaps we should export history elsewhere? > > On Thu, Jan 27, 2022 at 1:10 PM Vadim Ogievetsky > wrote: > > > Alright, I have setup the new Slack workspace and updated the link on > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=hV9FPFkuEXDmMbTGo3m_iqUc-baVKjOHznj9kig1I1Q&e= > > to point to it. > > Please join with the > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_join-2Dslack&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=07e2sPTwojKxi997mSN4a5Ktcr1lyHcekXuTwEZj9JY&e= > > link (and share it with others). > > Sadly there is no way to migrate content from one Slack workspace to > > workspace, I am sure we will fill the new channel with great content very > > quickly! > > > > On 2022/01/20 18:15:23 Vadim Ogievetsky wrote: > > > I think that the PMC should create a new Slack channel for Apache Druid > > and > > > shift the community towards using it away from the ASF Slack. I > volunteer > > > to do this on the PMCs behalf and do all the setup/admin work. I would > > > share admin access with any PMC member. > > > > > > What is the motivation for this? > > > > > > As you may have heard, it’s become increasingly difficult for new users > > > without an @apache.org email address to join the ASF #druid Slack > > channel. > > > ASF Infra disabled the option to publicly provide a link to the > workspace > > > to anyone who wanted it, after encountering issues with spammers. > > > > > > Per Infra’s guidance ( > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__infra.apache.org_slack.html&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=qZfDyv1d4QnrCrEjvTgSbm8qeEj-B-dFWKil2k4XOyQ&e= > > ), new community > > > members should only be invited as single-channel guests. Unfortunately, > > > single-channel guests are unable to extend invitations to new members, > > > including their colleagues who are using Druid. Only someone with full > > > member privileges is able to extend an invitation to new members. This > > lack > > > of consistency doesn’t make the community feel inclusive. > > > > > > There is a workaround in place ( > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_druid-2Dwebsite-2Dsrc_pull_278&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=LZAv4yoEkFJcPmJckcAR0xXyuo7V81ZfR2X_jxQjH58&e= > > ) – users can send an > > > email to druid-u...@googlegroups.com to request an invite to the Slack > > > channel from an existing member – but this still poses a barrier to > > entry, > > > and isn’t a viable permanent solution. It also creates potential > privacy > > > issues as not everyone is at liberty to announce they’re using Druid > nor > > > wishes to display their email address in a public forum. > > > > > > I propose we make our own free Slack channel for Apache Druid and > > encourage > > > people to migrate to it. Then we can have our own policy on Slack > > > invitations - I would like to restore the ability for anyone on the web > > to > > > join our Slack. > > > > > > This is not a 100% original idea, in fact this is what other Apache > > > projects have done, notably Apache Pinot (see "join our slack" on > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__pinot.apache.org_&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU&m=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF&s=GYTpyHD-1U_Er2eKNXk41b9aiy4zW9EtCt-2YXxSh9o&e= > > ). I propose we do the same. > > > > > > Vadim > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > >
