Re: [VOTE] Release Apache Druid 29.0.0 [RC1]
That sounds great to me. Thank you +1 On 2024/02/20 18:58:35 Laksh Singla wrote: > Since the artifacts were already out at the time of the Vad's vote, I will > be going ahead with the release of Druid 29.0.0. However, I do echo with > the comments mentioned in the mail, therefore we can take the following > steps to prevent misfortune for the unexpecting users: > > For the current Druid 29.0.0 release: > 1. The docs (update, release, and general docs) will be updated with the > possible pitfalls arising out of console injecting the "arrayIngestMode" > automatically, and persisting it for the given tab. > > Further, we can have a patch release, 29.0.1, with the following patches > mentioned in the Vad's mail, that would have been a part of RC2, had the > vote not passed through at the time: > 1. https://github.com/apache/druid/pull/15927 > 2. https://github.com/apache/druid/pull/15920 > > This will address the concerns regarding the 29.0.0 release, and also give > enough time for the PRs to get reviewed without being hastened by the > release timeline. I'll volunteer to be the release manager for the same. > Thoughts? > > Regards > Laksh > > > > On Tue, 20 Feb 2024 at 10:50, Abhishek Agarwal wrote: > > > Vad, The vote was closed by Laksh, given that 72 hours had passed and > > artifacts had been released. Given we had the three binding +1s, we can > > proceed as usual. I suggest that we call out the caveat clearly in the > > release notes section. > > > > On Mon, Feb 19, 2024 at 11:53 PM Vadim Ogievetsky > > wrote: > > > > > Thank you for all the work getting this release to this point. As the > > > author of https://github.com/apache/druid/pull/15588 I regretfully vote > > > -1 on this release. To echo Gian's point I think the chance of some user > > > injuring a production Datasource with an innocent query pasted into the > > > wrong web console tab is just too large. The fact that the > > > "arrayIngestMode" setting itself is not new in this release is immaterial > > > to my consideration as I am more worried about "what might happen by > > > accident" than "what is technically possible to mess up". > > > > > > I have made a PR (https://github.com/apache/druid/pull/15927) that > > > implements Gian's suggestion of: Making it obvious in the web console > > > whether a tab is in "arrayIngestMode: array" or "arrayIngestMode: mvd" or > > > "server default". Furthermore this PR also minimizes the use of > > > "arrayIngestMode: array" to only when needed while still generating the > > > "correct" form of the SQL queries at all times. If this PR was merged and > > > back-ported I would change my vote to +1. > > > > > > I think that Gian's validation PR ( > > > https://github.com/apache/druid/pull/15920) is an even better solution, > > > as it would protect API usage and usage via other frontends also. > > Obviously > > > we could merge both. > > > > > > Another idea that would solve this issue would be have the ability to set > > > context flags via SQL perhaps with a PARAMETER keyword. If this was > > > possible the console could exclusively use that for setting query context > > > parameters on generated queries. > > > > > > Vadim > > > > > > On 2024/02/17 02:52:38 Gian Merlino wrote: > > > > Here's a patch with the validation idea: > > > https://github.com/apache/druid/pull/15920 > > > > > > > > It adds validation for the most problematic case (mixing strings and > > > arrays), provides a way to override the validation, and makes the warning > > > log on the controller task when arrayIngestMode is 'mvd' more friendly > > and > > > explanatory. > > > > > > > > Depending on which direction you're going in, the errors look like > > > either: > > > > > > > > Cannot write into field[flags] using type[VARCHAR ARRAY] and > > > arrayIngestMode[mvd], since the existing type is[VARCHAR ARRAY]. Try > > > setting arrayIngestMode to[array] to retain the SQL type[VARCHAR ARRAY] > > > > > > > > Or: > > > > > > > > Cannot write into field[flags] using type[VARCHAR ARRAY] and > > > arrayIngestMode[array], since the existing type is[VARCHAR]. Try wrapping > > > this field using ARRAY_TO_MV(...) AS "flags" > > > > > > > > The "try" language pushes people towards t
Re: [VOTE] Release Apache Druid 29.0.0 [RC1]
Thank you for all the work getting this release to this point. As the author of https://github.com/apache/druid/pull/15588 I regretfully vote -1 on this release. To echo Gian's point I think the chance of some user injuring a production Datasource with an innocent query pasted into the wrong web console tab is just too large. The fact that the "arrayIngestMode" setting itself is not new in this release is immaterial to my consideration as I am more worried about "what might happen by accident" than "what is technically possible to mess up". I have made a PR (https://github.com/apache/druid/pull/15927) that implements Gian's suggestion of: Making it obvious in the web console whether a tab is in "arrayIngestMode: array" or "arrayIngestMode: mvd" or "server default". Furthermore this PR also minimizes the use of "arrayIngestMode: array" to only when needed while still generating the "correct" form of the SQL queries at all times. If this PR was merged and back-ported I would change my vote to +1. I think that Gian's validation PR (https://github.com/apache/druid/pull/15920) is an even better solution, as it would protect API usage and usage via other frontends also. Obviously we could merge both. Another idea that would solve this issue would be have the ability to set context flags via SQL perhaps with a PARAMETER keyword. If this was possible the console could exclusively use that for setting query context parameters on generated queries. Vadim On 2024/02/17 02:52:38 Gian Merlino wrote: > Here's a patch with the validation idea: > https://github.com/apache/druid/pull/15920 > > It adds validation for the most problematic case (mixing strings and arrays), > provides a way to override the validation, and makes the warning log on the > controller task when arrayIngestMode is 'mvd' more friendly and explanatory. > > Depending on which direction you're going in, the errors look like either: > > Cannot write into field[flags] using type[VARCHAR ARRAY] and > arrayIngestMode[mvd], since the existing type is[VARCHAR ARRAY]. Try setting > arrayIngestMode to[array] to retain the SQL type[VARCHAR ARRAY] > > Or: > > Cannot write into field[flags] using type[VARCHAR ARRAY] and > arrayIngestMode[array], since the existing type is[VARCHAR]. Try wrapping > this field using ARRAY_TO_MV(...) AS "flags" > > The "try" language pushes people towards the behavior we'd like for the > future: using arrayIngestMode[array] and wrapping MVDs in ARRAY_TO_MV. > > I'm changing my vote to a plain 0, given that _most_ of the changes related > to arrayIngestMode went out in Druid 28. However I do think it would be nice > to get a patch like this in, given that the Druid 29 web console is pushing > more people to change their arrayIngestMode. > > Gian > > On 2024/02/16 22:24:23 Gian Merlino wrote: > > I just learned that arrayIngestMode is not actually new, just > > https://github.com/apache/druid/pull/15588 is. However this will still make > > it more likely that people accidentally break their tables, so I am still > > -0. Just, slightly less so. I still think it would be a good idea, for > > Druid 29, to add string-to-array type validation to Druid 29's INSERT / > > REPLACE handling to compensate for the new web console support for > > arrayIngestMode, and the UI changes to push people towards setting it to > > "array". > > > > I could be convinced that it's ok to do that in a 29.0.1. I don't think it > > should wait for 30, given the impact that can happen if people end up with > > mixed types without planning for it. > > > > On Fri, Feb 16, 2024 at 2:16 PM Gian Merlino wrote: > > > > > Thanks for managing this release! > > > > > > My vote is -0, let me explain why. I am concerned about usability issues > > > with the new arrayIngestMode feature. There are various issues when mixing > > > MVD strings and string arrays in the same column: as soon as arrays show > > > up > > > in a column, various "classic MVD-style" queries will fail at validation > > > or > > > at runtime. I believe that the new feature, and especially the changes to > > > the web console in https://github.com/apache/druid/pull/15588, will make > > > it more likely that people will do this by accident and experience > > > brokenness. > > > > > > When this occurs, there is not an easy way to fix it; data needs to be > > > reingested or queries need to be adjusted. I believe that in some cases, > > > queries can't be adjusted without suffering from performance loss. > > > > > > This is something that could happen even before Druid 29, if you did a > > > Kafka ingest with auto types or useSchemaDiscovery, followed by a SQL > > > REPLACE from that table into itself. In that case, arrays written by Kafka > > > ingest would get rewritten as MVDs. But with this Druid 29 RC, there are > > > additional pathways created that enable people to get into this > > > problematic > > > scenario with increased likelihood. I suggest we
Re: [VOTE] Release Apache Druid 26.0.0 [RC3]
I vote +1 (binding) My checks included: 1. Checksum verified for all assets 2. Source code compiled (Intel based Mac) 3. Ran through the demo queries 4. Ran through the quickstart and the 60m NYC taxi query (Java 11) 5. Checked out the web console specific changes, release notes, and docs Vadim On 2023/05/19 19:28:05 Clint Wylie wrote: > Hi all, > > I have created a build for Apache Druid 26.0.0, release > candidate 3. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/14064 > > The release candidate has been tagged in GitHub as > druid-26.0.0-rc3 (727c61943381a82e94a0d6c6409f505dcfda11c1), > available here: > https://github.com/apache/druid/releases/tag/druid-26.0.0-rc3 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/26.0.0-rc3/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1042/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/26.0.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:26.0.0-rc3 > > artifact checksums > src: > 67f572acf2cdfbf3affdeb665fefb8d91bec0650ad54e1c3fb3d1eedb15932fa33b612bf870676a76a1a2aa0c57f7cee99bec8eeec33de975326d0d6923ac0b4 > bin: > b8d2c982c8fcc0abadecb571727a3e8f69a6f79ee315fbe9628c3cffc7f92df7437d17b80c0e5234222bb55b265591d19081cbdcda0ab37563805fecf3e4 > hadoop3-bin: > 0dc1bfbd90ff4467518c203375278a1cfa0ef1ebceea5a3359615aebd06e70d1af121ddd8590eeae960e5d286e5c317cd4b571bcf94c8c25458e4ae92d6aafab > docker: > 9a3a07819058693b29bb5fc145e071c3b3a1f551960640529a60ad5198f29b59 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/cwylie.asc > > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > > Verify checksums: > diff <(shasum -a512 apache-druid-26.0.0-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-26.0.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-26.0.0-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-26.0.0-bin.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-26.0.0-hadoop3-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-26.0.0-hadoop3-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-26.0.0-src.tar.gz.asc \ > apache-druid-26.0.0-src.tar.gz > > gpg --verify apache-druid-26.0.0-bin.tar.gz.asc \ > apache-druid-26.0.0-bin.tar.gz > > gpg --verify apache-druid-26.0.0-hadoop3-bin.tar.gz.asc \ > apache-druid-26.0.0-hadoop3-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The RAT license check can be run from source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Druid 26.0.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks! > > - > 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: [VOTE] Release Apache Druid 25.0.0 [RC2]
I vote +1 (binding) My checks included: 1. Checksum verified for all assets 2. Signature verified for all assets 3. Source code compiled (Intel based Mac) 4. Ran through the quickstart and the 60m NYC taxi query (Java 11) 5. Ran through the demo queries 6. Checked out the web console specific changes, release notes, and new docs Vadim On 2022/12/22 16:41:04 Kashif Faraz wrote: > Hi > > I have created a build for Apache Druid 25.0.0, release candidate 2. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/13592 > > The release candidate has been tagged in GitHub as druid-25.0.0-rc2 > (9a78059ffbb22f0bf6074cd81b13078a2d4501bc), > available here: > https://github.com/apache/druid/releases/tag/druid-25.0.0-rc2 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/25.0.0-rc2/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1039/ > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:25.0.0-rc2 > > Artifact checksums: > src: > 0002091f2f76d64315e1242e5f61cf07517add8af5e4e4739d06eeff93944064721843a4e9666c61cb4f1e8bf587c0a4669cea01fe8f894cb3ae1a09849dd565 > bin: > 16f917c1c12c8edf85cefd4ad2fb68bf74cdbbb83e791e15fd13e74af18f3fbfddcdfbae8ab3834dba71cd8d45c6fe3920fbe3c75b0e5d050f040332c8ce54b7 > hadoop3-bin: > bdbfc5ae261d8bb551e91e0bca366d7a467e2063e174216ce65c574a73dd44bf6b8f9cde0301bddcab548210ab217a2ccfc9d2e077fe010d3959a10fd0e4b23c > docker: > d512f248e70b43fe94f2703b87e28b6f49a5a396f2407f6068cbb95c60153b14 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/kfaraz.asc > > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > Verify checksums: > diff <(shasum -a512 apache-druid-25.0.0-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-25.0.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-25.0.0-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-25.0.0-bin.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-25.0.0-hadoop3-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-25.0.0-hadoop3-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-25.0.0-src.tar.gz.asc \ > apache-druid-25.0.0-src.tar.gz > > gpg --verify apache-druid-25.0.0-bin.tar.gz.asc \ > apache-druid-25.0.0-bin.tar.gz > > gpg --verify apache-druid-25.0.0-hadoop3-bin.tar.gz.asc \ > apache-druid-25.0.0-hadoop3-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The hadoop-3 based artifacts can be generated by running: > mvn clean install -Phadoop3,apache-release,dist -Dgpg.skip > > The RAT license check can be run from source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Druid 25.0.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks > Kashif Faraz > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: [VOTE] Release Apache Druid 25.0.0 [RC1]
FYI One of the verification commands has a typo (extra 'o') It should be diff <(shasum -a512 apache-druid-25.0.0-hadoop3-bin.tar.gz | \ cut -d ' ' -f1) \ <(cat apache-druid-25.0.0-hadoop3-bin.tar.gz.sha512 ; echo) Just posting for anyone else who might be confused as I was. On 2022/12/20 07:12:08 Kashif Faraz wrote: > Hi > > I have created a build for Apache Druid 25.0.0, release candidate 1. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/13592 > > The release candidate has been tagged in GitHub as druid-25.0.0-rc1 > (644f70681dfbe44aab8f85473936c5a58e8dfac9), > available here: > https://github.com/apache/druid/releases/tag/druid-25.0.0-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/25.0.0-rc1/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1038/ > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:25.0.0-rc1 > > Artifact checksums: > src: > 9a25ac68bf2cc6a4352b06306711b557e3def31387310d398392f17675259a27e3186158611782d8eaaf0a88e64c83e775fe7bb590f29a99e59c6f9e5b4a57c2 > bin: > 345933d64a8b7d818f2e16914af0d2f3d2b8b8de08784382b054e4f5fdaa0fff2d28bda44737b57282adc9f5bbf404880bfec7292aba97f31ff1cb8181ca7b4d > hadoop3-bin: > 94c5aaae22a24e423cfb0f7a9df5559b1b7dd3553b70c34c24b44b420c50734a8f88843cc16e3fa67e9550d96d15674f8a5d59eb4860ed2f377d0a46c0a6 > docker: > b0feade0a47f2a2dc3687e410293bf8e3309fd9e8a3de10b101e2384902e76c2 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/kfaraz.asc > > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > Verify checksums: > diff <(shasum -a512 apache-druid-25.0.0-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-25.0.0-src.tar.gz.sha512 ; echo) > diff <(shasum -a512 apache-druid-25.0.0-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-25.0.0-bin.tar.gz.sha512 ; echo) > diff <(shasum -a512 apache-druid-25.0.0-hadooop3-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-25.0.0-hadoop3-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-25.0.0-src.tar.gz.asc \ > apache-druid-25.0.0-src.tar.gz > gpg --verify apache-druid-25.0.0-bin.tar.gz.asc \ > apache-druid-25.0.0-bin.tar.gz > gpg --verify apache-druid-25.0.0-hadoop3-bin.tar.gz.asc \ > apache-druid-25.0.0-hadoop3-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The hadoop-3 based artifacts can be generated by running: > mvn clean install -Phadoop3,apache-release,dist -Dgpg.skip > > The RAT license check can be run from source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Druid 25.0.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks > Kashif Faraz > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: [VOTE] Release Apache Druid 24.0.2 [RC1]
I vote +1 My checks included: 1. Checksum verified 2. Signature verified 3. Source code compiled (Intel based Mac) 4. Ran through the quickstart and the 60m NYC taxi query (Java 11) On 2022/11/26 09:21:53 Kashif Faraz wrote: > Hi > > I have created a build for Apache Druid 24.0.2, release candidate 1. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/13435 > > The release candidate has been tagged in GitHub as druid-24.0.2-rc1 > (13c9fdcbafcf61211a9381892615c4b4db6a3535), > available here: > https://github.com/apache/druid/releases/tag/druid-24.0.2-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/24.0.2-rc1/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1037/ > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:24.0.2-rc1 > > Artifact checksums: > src: > 1ca1ea4b9a4418813fc22cdba2626725f802ff886e118b9986b89e8a6df9fe304a0fb0eca1370a1c937ac5b136448c8157d58b1f79712347ca5cb67f7f034cfc > bin: > ca22923d0c1b60803289ada2be6c7e74b41641e95e3ad36fb625edd71c62d29f5203221062e5bf7af8199075bbc46606ec3ae8b559b455e1ecfc990f0e669f55 > docker: > e96ae3293242e90e0a78be128c0d12325b8a6fc5c68ce2f2bc53de3aac568bbf > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/kfaraz.asc > > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > Verify checksums: > diff <(shasum -a512 apache-druid-24.0.2-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-24.0.2-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-24.0.2-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-24.0.2-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-24.0.2-src.tar.gz.asc \ > apache-druid-24.0.2-src.tar.gz > > gpg --verify apache-druid-24.0.2-bin.tar.gz.asc \ > apache-druid-24.0.2-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The RAT license check can be run from source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Druid 24.0.2 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > > Thanks > Kashif > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: [VOTE] Release Apache Druid 24.0.1 [RC1]
I vote +1 My checks included: 1. Checksum verified 2. Signature verified 3. Source code compiled (Intel based Mac) 4. Ran through the quickstart and a few other select queries (Java 11) 5. Checked the specific web-console things fixed in this release On 2022/11/09 05:55:50 Kashif Faraz wrote: > Hi > > I have created a build for Apache Druid 24.0.1, release candidate 1. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/13320 > > The release candidate has been tagged in GitHub as druid-24.0.1-rc1 > (7a04fc1a7b5eddfdf766ae31c1d3ce3c49fc16a8), > available here: > https://github.com/apache/druid/releases/tag/druid-24.0.1-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/24.0.1-rc1/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1035/ > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:24.0.1-rc1 > > Artifact checksums: > src: > 75b1eaf28b83a014c282e32519edb07402dae35625d5cffcbc7ce3ce3a7fbd5338370a4d8dae7c001b77360c176ca32298b7ff4d71a610ed39423fa078863b03 > bin: > 58430e64ecad15f4a4baf37c3a91b863c20546a012bf488984c4b79b1642f8a398ba9454d2218f57e23a57a70c117a30423eedfb359d3dc3079027c002580f61 > docker: > 40123383a5d6b2a186fbabb7d63382f6903aa4e77aeab272db55a6ff1dd446be > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/kfaraz.asc > > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > Verify checksums: > diff <(shasum -a512 apache-druid-24.0.1-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-24.0.1-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-24.0.1-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-24.0.1-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-24.0.1-src.tar.gz.asc \ > apache-druid-24.0.1-src.tar.gz > > gpg --verify apache-druid-24.0.1-bin.tar.gz.asc \ > apache-druid-24.0.1-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The RAT license check can be run from source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Druid 24.0.1 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks > Kashif > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: [VOTE] Release Apache Druid 24.0.0 [RC2]
I vote +1 My checks included: 1. Checksum verified 2. Signature verified 3. Source code compiled (Intel based Mac) 4. Ran through the new quickstart and all the example queries from the binary distribution (Java 11) 5. Used the binary distribution for a few days just doing all sorts of queries (lots of MSQ usage) on it as part of other projects Regarding the issues that Frank raised: - https://github.com/apache/druid/pull/13068 this does not look like a regression in 24.0 - https://github.com/apache/druid/pull/13069 I think it is fine to release without it and mention it in the documentation. On 2022/09/10 08:32:18 Abhishek Agarwal wrote: > Hi all, > I have created a build for Apache Druid 24.0.0, release candidate 2. > > Thanks to everyone who has helped contribute to the release. You can read > the draft release notes here: > https://github.com/apache/druid/issues/12825 > > The release candidate has been tagged in GitHub as druid-24.0.0-rc2 > (09991dcf17fb9984b65f291f0db47e38058253e4), available here: > https://github.com/apache/druid/releases/tag/druid-24.0.0-rc2 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/24.0.0-rc2/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1032 > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/24.0.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:24.0.0-rc2 > > artifact checksums > src: > 867e3c4787e4e3f2a35e066cc982698d3e1a77fe90be7de163bd893908c13fec7fd8a84e19020f6f32fb517502a8eb729ae4492d51549f72a57f2bbf42b08e9c > > bin: > 8b15192a7fb5a6f979b0c8f51bfd0dee5d26a5912ec2a3d25f4739ebbf89cadebed353ba30977a0b13b6410f89a2991eb7ee5ebea4217026129ce2262875dc91 > > docker (sha256): > c5ab9872c2f6e340f1429fd0bd514f163b0e491a9d808ee85de9a1b8f81ffe0b > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/abhishek > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > Verify checksums: > diff <(shasum -a512 apache-druid-24.0.0-src.tar.gz | cut -d ' ' -f1) <(cat \ > apache-druid-24.0.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-24.0.0-bin.tar.gz | cut -d ' ' -f1) <(cat \ > apache-druid-24.0.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-24.0.0-src.tar.gz.asc \ > apache-druid-24.0.0-src.tar.gz > > gpg --verify apache-druid-24.0.0-bin.tar.gz.asc \ > apache-druid-24.0.0-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The RAT license check can be run from source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Druid 24.0.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks! > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: [VOTE] Release Apache Druid 0.23.0 [RC2]
+1 (binding) Source: - Did a build (the one the console does as part of CI) Binary: - Run the quickstart - Played with the depth of the console - Ran some queries On 2022/06/15 14:22:23 Abhishek Agarwal wrote: > Hi all, > I have created a build for Apache Druid 0.23.0, release candidate 2. > > Thanks to everyone who has helped contribute to the release. You can read > the draft release notes here: > https://github.com/apache/druid/issues/12510 > > The release candidate has been tagged in GitHub as druid-0.23.0-rc2 > (c085dd1a5e3db02806f1fc8f54fd7f9297ee0f77), available here: > https://github.com/apache/druid/tree/druid-0.23.0-rc2 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/0.23.0-rc2/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1030 > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/0.23.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:0.23.0-rc2 > > artifact checksums > src: > 50ff149fa274ac10c01040dc30bbf28fc24732da5a27f1b88f89b13bbee5c9ec8a68f5d57e7caabc5813cac5f551e1c4ca94dc8faa9c6d8efc022f3bd3bef7e3 > > bin: > 5e7420bdc66247f0309fc0c1eafeff7ba935ed195f3a28c2da4b23a28ff637300b46b1c3d048379ccd570dde164968494ff5d8847e82eaf9b0edb518f8665328 > > docker (sha256): > ed9719968b4be3a2f1643907a1a5a5814e2ee1215f3604da8b2da2ac05f65912 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/abhishek > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > Verify checksums: > diff <(shasum -a512 apache-druid-0.23.0-src.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-0.23.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-0.23.0-bin.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-0.23.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-0.23.0-src.tar.gz.asc > apache-druid-0.23.0-src.tar.gz > > gpg --verify apache-druid-0.23.0-bin.tar.gz.asc > apache-druid-0.23.0-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from the source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The RAT license check can be run from the source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Druid 0.23.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks! > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Apache Druid Slack
Alright, I have setup the new Slack workspace and updated the link on https://druid.apache.org/community/ to point to it. Please join with the https://druid.apache.org/community/join-slack 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://infra.apache.org/slack.html), 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://github.com/apache/druid-website-src/pull/278) – 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://pinot.apache.org/). 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
Apache Druid Slack
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://infra.apache.org/slack.html), 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://github.com/apache/druid-website-src/pull/278) – 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://pinot.apache.org/). 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
Re: Graduation
Huzzah! Thank you for all the hard work Gian. On 2019/12/20 19:49:37, Gian Merlino wrote: > Hey Druids, > > It is official: Druid has graduated to a top level project! > > Now, we need to conduct various post-graduation tasks. The first is to > raise an infra ticket to migrate the appropriate resources. I started it > off here: https://issues.apache.org/jira/browse/INFRA-19609. Please, take a > look to see if I missed anything. > > The website (https://druid.apache.org/) has already been updated to remove > the incubation disclaimed. We should also update the packaging and > documentation to remove the DISCLAIMER file and mentions of incubating > status. Is anyone interested in picking this up? > > There are some other steps in this doc that I'm starting to take a look at: > https://incubator.apache.org/guides/transferring.html > > Thanks everyone!! > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: [VOTE] Release Apache Druid (incubating) 0.16.1 [RC1]
+1 (non-binding) On 2019/11/29 04:21:38, Jonathan Wei wrote: > Hi all, > > I have created a build for Apache Druid (incubating) 0.16.1, release > candidate 1. > > Thanks for everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/incubator-druid/issues/8972 > > The release candidate has been tagged in GitHub as > druid-0.16.1-incubating-rc1 (0706f70ad0e3ec74f09b47c615451c42b9a5b337), > available here: > https://github.com/apache/incubator-druid/releases/tag/druid-0.16.1-incubating-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/incubator/druid/0.16.1-incubating-rc1/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/0.16.1-incubating/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/incubator-druid:0.16.1-incubating-rc1 > > artifact checksums > src: > aff2117e4c6c5440e34e0579eee97ad47ae954ad659363574610972ffec417e00d47650c0fb5bf4cee3cba7cfa369784491d35b085a26b1efa497b10d09df115 > bin: > 1b9a3a6bfd53a3d743be6b66d9b83cd42e2c9dd49ba8e5d1c000377ed4ff7c3dc6e56eb59590acb42ebf48e787158f6d27256c5b998a877f33baf1acf509becd > docker: a6921f213383772a8797b2699c507153fa713fd4ddfc05d3e4585d691ecd53ac > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/jonwei.asc > > This key and the key of other committers can also be found in the project's > KEYS file here: > https://dist.apache.org/repos/dist/release/incubator/druid/KEYS > > (If you are a committer, please feel free to add your own key to that file > by following the instructions in the file's header.) > > > Verify checksums: > diff <(shasum -a512 apache-druid-0.16.1-incubating-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-0.16.1-incubating-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-0.16.1-incubating-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-0.16.1-incubating-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-0.16.1-incubating-src.tar.gz.asc \ > apache-druid-0.16.1-incubating-src.tar.gz > > gpg --verify apache-druid-0.16.1-incubating-bin.tar.gz.asc \ > apache-druid-0.16.1-incubating-bin.tar.gz > > Please review the proposed artifacts and vote. Note that Apache has > specific requirements that must be met before +1 binding votes can be cast > by PMC members. Please refer to the policy at > http://www.apache.org/legal/release-policy.html#policy for more details. > > As part of the validation process, the release artifacts can be generated > from source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The RAT license check can be run from source by: > mvn apache-rat:check -Prat > > This vote will be open for at least 72 hours. The vote will pass if a > majority of at least three +1 PMC votes are cast. > > Once the vote has passed, the second stage vote will be called on the > Apache Incubator mailing list to get approval from the Incubator PMC. > > [ ] +1 Release this package as Apache Druid (incubating) 0.16.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks! > > Apache Druid (incubating) is an effort undergoing incubation at The Apache > Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is > required of all newly accepted projects until a further review indicates > that the infrastructure, communications, and decision making process have > stabilized in a manner consistent with other successful ASF projects. While > incubation status is not necessarily a reflection of the completeness or > stability of the code, it does indicate that the project has yet to be > fully endorsed by the ASF. > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Make a Druid 0.16.1 release?
Huge +1 to this. I think the Java 11 phantom working issue is the number one thing that I see stumbling new users in the ASF Slack. The other big one the is the ZooKeeper dependency that I have personally seen several people skip the download ZK step of the quickstart. This is addressed in https://github.com/apache/incubator-druid/pull/8792 and it would be awesome if it could get included. Lastly there is https://github.com/apache/incubator-druid/pull/8682 which has hit me in demos a few times. It makes me sad that clicking on the paste data tile does not work by default (index_parallel). Thank you for doing this release Jon! On 2019/11/26 02:34:38, Jonathan Wei wrote: > Hi all, > > I think we should do a small 0.16.1 fix release to address two rolling > upgrade issues, add improvements to the startup scripts that would help > avoid some very confusing failures for new users, and address the Wikipedia > dataset licensing questions that were raised during the 0.15.1 voting > process. I'll volunteer to manage the release if we agree on it. > > > > There are two known issues with rolling upgrades that affect 0.16.0, fixed > by the following PRs: > - https://github.com/apache/incubator-druid/pull/8864 add sequenceName and > currentCheckPoint for backwards compatibility #8864 > - https://github.com/apache/incubator-druid/pull/8905 Retrying with a > backward compatible task type on unknown task type error in parallel > indexing #8905 > > > > There have been quite a few people hitting issues when they try to run > Druid under a Java version later than 8. > > While our docs mention that only Java 8 is supported, the failure mode when > that condition is not met occurs pretty late: users try ingesting some > data, and stuff works until they see that historicals are not loading their > segments, with no immediate indication that the error is occurring because > of Java version incompatibilities. > > The following links from the ASF Slack channel show examples of users > encountering this confusing failure: > - https://the-asf.slack.com/archives/CJ8D1JTB8/p1569948481021000 > - > https://the-asf.slack.com/archives/CJ8D1JTB8/p1572936011252000?thread_ts=1572845319.226400=CJ8D1JTB8 > - https://the-asf.slack.com/archives/CJ8D1JTB8/p1572561066155100 > > The following patch adds a Java 8 version check to the bundled startup > scripts, so that users are given a clear error reason promptly: > https://github.com/apache/incubator-druid/pull/8794 Startup scripts: verify > Java 8 (exactly), improve port/java verification messages. > > A follow-on patch to the above also addresses port conflicts that can > result in confusing behavior for people getting started with Druid (the > failure mode here is that a user has an existing process that binds only on > localhost to a port that Druid uses, so traffic destined for localhost with > that port hits that non-Druid process but traffic destined for other IP > addresses on that machine will go to Druid): > https://github.com/apache/incubator-druid/pull/8942 Improve > verify-default-ports to check both INADDR_ANY and 127.0.0.1. > > > > The licensing questions around the bundled Wikipedia dataset that were > raised in the IPMC vote for 0.15.1 have been resolved ( > https://issues.apache.org/jira/browse/LEGAL-480), so we should also update > our licensing-related documentation soon. > > Thanks, > Jon > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: replacing the old web consoles
Hi All, Firstly: I have just added the segment timeline to the coordinator version of the console https://github.com/apache/incubator-druid/pull/8838/commits/ef6f8efb23b66be5a70e6f53138509cc30ee540f This now makes the coordinator version of the console a complete functional replacement for the legacy console. David, the UX goes as follows: After this change the Router, Coordiantor, and Overlord all serve the exact same JS asset. When the console loads it does a capability check by trying to query certain APIs. Specifically it checks for: - SQL query-ability (for system tables) - Native query-ability - Cooridnator API availability (directly or via management proxy) - Overlord API availability (directly or via management proxy) It then goes into an appropriate mode depending on what capabilities it has access to. On the Coordinator it will not have access to the query aspects and will go into a restricted mode where some features are disabled. This restricted mode is still functionally equivalent/superior to the old coordinator console. You will still get the most complete experience with the console when it is served from the Router as it is the only node that offers all those APIs. In the future (not part of 0.17.0 release) it would be nice to have the console served on the Broker also and put the management proxy into the Broker so it can also offer the complete experience. On 2019/11/12 02:44:47, David Glasser wrote: > The idea here is that you would be able to get the equivalent experience of > the new web console without running a router? > > If you are still running separate coordinator and overlord, what does the > user experience feel like here? Do you have two separate "half" apps that > you have to bookmark and switch between manually, or do they both serve the > same React app but just talk to two different backends? > > On Mon, Nov 11, 2019 at 1:30 PM Clint Wylie wrote: > > > Hi all, > > > > Vadim and I have been working on a PR to replace and remove all of the old > > coordinator and overlord web consoles with the new web console that is > > currently only served from the router. The new console will operate with > > the subset of functionality which is appropriate to each service type. This > > new ui will be functionally equivalent to what was available, with the > > exception of the segment timeline that is available on the newer old > > coordinator console, which I believe Vad plans to add in a follow-up (there > > is already a version of this on the new router web console). We think this > > will give users a more consistent and coherent experience when operating > > Druid, and it removes a rather large chunk of code from the code-base which > > should make maintenance a lot easier on our end. > > > > You can find the PR here: > > https://github.com/apache/incubator-druid/pull/8838. We think this PR is > > ready to merge, but wanted to ask the list if anyone has any concerns > > before we move forward with this. > > > > Cheers, > > Clint > > > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: replacing the old web consoles
Thanks for posting Clint! I wanted to add that all the code being removed is totally unmaintained (and has been for a while), has many errors that show up in the JS console, and depends on old libraries marked with vulnerabilities. This is the main motivation to actually remove the old consoles as opposed to just hiding them but letting them live as is. On 2019/11/11 21:30:12, Clint Wylie wrote: > Hi all, > > Vadim and I have been working on a PR to replace and remove all of the old > coordinator and overlord web consoles with the new web console that is > currently only served from the router. The new console will operate with > the subset of functionality which is appropriate to each service type. This > new ui will be functionally equivalent to what was available, with the > exception of the segment timeline that is available on the newer old > coordinator console, which I believe Vad plans to add in a follow-up (there > is already a version of this on the new router web console). We think this > will give users a more consistent and coherent experience when operating > Druid, and it removes a rather large chunk of code from the code-base which > should make maintenance a lot easier on our end. > > You can find the PR here: > https://github.com/apache/incubator-druid/pull/8838. We think this PR is > ready to merge, but wanted to ask the list if anyone has any concerns > before we move forward with this. > > Cheers, > Clint > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Extending Druid management UI
Thank you! I appreciate your excitement! There are no ways currently of extending the console via an extension (save for replacing it wholesale). Could you file GitHub issues detailing exactly what you would want to achieve and how it might look like? For example what information would you want to hide and from who? Best regards, Vadim On 2019/10/29 19:08:03, Insightum Data wrote: > We just upgraded to 0.16 release and very excited to see the new management > UI. > Thanks for all the awesome work you guys have been doing. > > We have some internal use cases and would like to build them on top of > existing druid management UI by extending it - > >1. Is it possible to add new tabs to the UI via druid extensions ? >2. any guidelines/sample code or pointers to existing extensions around >the UI would be helpful >3. We do not want to show some information to some user groups e.g. we >do not wish to show the internal server information, is it possible to hide >specific tabs for a user group via some configurations ? > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: A list of issues for new committers
Ok I will remove the Difficulty labels and repurpose "Easy" to "Starter" unless anyone objects within 24h. On 2019/10/09 06:30:06, Gian Merlino wrote: > That is definitely a good property for starter issues (not needing a > production cluster to validate). > > On Fri, Oct 4, 2019 at 12:01 AM Roman Leventov > wrote: > > > I don't use "Contributions Welcome" exclusively for starter issues. I do > > _not_ put this label though on issues that are impossible or hard to > > validate without a production cluster (with specific type of load, > > perhaps). So the assumption is that anyone just with a laptop and IDE could > > contribute these issues, in theory. > > > > On Fri, 4 Oct 2019, 02:59 Vadim Ogievetsky, > > wrote: > > > > > Hi all, > > > > > > I would like to organize a set of issues (via a label) that are good > > > starting points for someone wanting to contribute to Druid. > > > I want to have the link to the issues filtered on that label to be part > > of > > > the README. > > > This would encourage people new to Druid to contribute and get involved > > in > > > the community. > > > > > > Right now there are two labels that sort of look like they might be > > > talking about something relevant: > > > > > > "Contributions Welcome" ( > > > https://github.com/apache/incubator-druid/labels/Contributions%20Welcome > > ) > > > > > > This label seems to only be used by Leventov. I am not a Java dev so it > > > is hard for me to judge if these issues are really good starter issues. > > > Maybe this is more of a "Help Wanted" label. > > > > > > "Difficulty - Easy" ( > > > https://github.com/apache/incubator-druid/labels/Difficulty%20-%20Easy) > > > > > > This label seems more aligned with what I want but I find its text too > > > off-putting to use. > > > "Easy"? for who? It would not be "easy" for me to to fix a distributed > > > systems bug no matter how small. > > > On the flip side the console might have a CSS bug that is "easy" in my > > > eyes but will make a Java dev very sad. > > > While I am on this subject I think these "Difficulty - *" labels are > > > generally unhelpful - does anyone actually use them? > > > > > > My suggestion is as follows: > > > > > > 1. Establish a "Starter" label, link it from the README > > > > > > 2. Rename the "Difficulty - Easy" to "Starter" and review to see if some > > > issues could be added or removed > > > > > > 3. Remove all the "Difficulty - *" labels > > > > > > > > > I would love to get some feedback on this. > > > > > > Best regards, > > > 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
A list of issues for new committers
Hi all, I would like to organize a set of issues (via a label) that are good starting points for someone wanting to contribute to Druid. I want to have the link to the issues filtered on that label to be part of the README. This would encourage people new to Druid to contribute and get involved in the community. Right now there are two labels that sort of look like they might be talking about something relevant: "Contributions Welcome" (https://github.com/apache/incubator-druid/labels/Contributions%20Welcome) This label seems to only be used by Leventov. I am not a Java dev so it is hard for me to judge if these issues are really good starter issues. Maybe this is more of a "Help Wanted" label. "Difficulty - Easy" (https://github.com/apache/incubator-druid/labels/Difficulty%20-%20Easy) This label seems more aligned with what I want but I find its text too off-putting to use. "Easy"? for who? It would not be "easy" for me to to fix a distributed systems bug no matter how small. On the flip side the console might have a CSS bug that is "easy" in my eyes but will make a Java dev very sad. While I am on this subject I think these "Difficulty - *" labels are generally unhelpful - does anyone actually use them? My suggestion is as follows: 1. Establish a "Starter" label, link it from the README 2. Rename the "Difficulty - Easy" to "Starter" and review to see if some issues could be added or removed 3. Remove all the "Difficulty - *" labels I would love to get some feedback on this. Best regards, Vadim - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: [ANNOUNCE] Apache Druid (incubating) 0.16.0 release
Best release ever On 2019/09/25 03:36:54, Clint Wylie wrote: > The Apache Druid team is proud to announce the release of Apache Druid > (incubating) 0.16.0. Druid is a high performance analytics data store for > event-driven data. > > Apache Druid 0.16.0-incubating contains over 350 new features, performance > enhancements, bug fixes, and major documentation improvements from 50 > contributors. Major new features and improvements include: > > - 'Vectorized' query processing > - 'Minor' compaction > - Native parallel indexing with shuffle > - New 'indexer' process > - Huge improvements to the web console > - New documentation website > - Official Docker image > > Source and binary distributions can be downloaded from: > https://druid.apache.org/downloads.html > > Release notes are at: > https://github.com/apache/incubator-druid/releases/tag/druid-0.16.0-incubating > > A big thank you to all the contributors in this milestone release! > > > > Disclaimer: Apache Druid is an effort undergoing incubation at The Apache > Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is > required of all newly accepted projects until a further review indicates > that the infrastructure, communications, and decision making process have > stabilized in a manner consistent with other successful ASF projects. While > incubation status is not necessarily a reflection of the completeness or > stability of the code, it does indicate that the project has yet to be > fully endorsed by the ASF. > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: new committer: Vadim Ogievetsky
Thank you for having me! I am excited to work alongside all of you to make Druid the most user friendly DB on the planet and to further this community. On 2019/09/24 20:20:44, Jonathan Wei wrote: > The Project Management Committee (PMC) for Apache Druid > has invited Vadim Ogievetsky to become a committer and we are pleased > to announce that he has accepted. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > Being a PMC member enables assistance with the management > and to guide the direction of the project. > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
