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 poin
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
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
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 chan
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:
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 candid
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:
> H
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
(
+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.
>
>
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 th
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
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
+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/
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
htt
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
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 console
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
cific 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,
> > >
> > >
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
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 featu
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
21 matches
Mail list logo
