+1 (binding)
src package:
* verified checksum and signature
* LICENSE and NOTICE present
* rat check passed
* built release distribution successful, no compilation error or cve flagged
* tested binary package built from source distribution with quickstart
configuration with kafka ingestion, ran so
I think this sounds reasonable, but to clarify what would the actual
change be here, just stronger wording in
https://druid.apache.org/docs/latest/configuration/extensions/#community-extensions
and not scanning for CVE? or something more, e.g. would we stop
publishing contrib jars to maven
(https:/
sgtm +1, and doing this aligns with the direction we are going with
the other hadoop stuff i think. If we really want to keep supporting
kerberos for auth longer term I think we would need to look into
replacing the existing implementation with something that doesn't use
hadoop libraries.
On Mon,
12 and a dropping of Java 11 both for Druid 35.
>
> Gian
>
> On 2025/06/17 19:17:22 Gian Merlino wrote:
> > This sounds good to me.
> >
> > On 2025/06/09 20:11:41 Clint Wylie wrote:
> > > Following up on this, I want to propose the first release of 2026 f
Following up on this, I want to propose the first release of 2026 for
removal, which I think would be Druid 36, to give some lead time for
those affected to prepare (which is the same timeline I proposed for
Hadoop removal).
On Fri, Dec 20, 2024 at 1:39 AM Clint Wylie wrote:
>
> I guess w
; >>> How does this plan look?
> > > >> >>>
> > > >> >>> On Fri, Dec 13, 2024 at 1:11 AM Maytas Monsereenusorn <
> > > >> mayt...@apache.org
> > > >> >>>>
> > > >> >>> wrote:
I think as long as someone is willing to do the hard part of filling
out the form for the Apache IP clearance process to completion (which
it sounds like you are), then it seems useful to be part of the
project. Reading through https://incubator.apache.org/ip-clearance/ it
sounds like it does need
+1 (binding)
src package:
* verified checksum and signature
* checked for LICENSE and NOTICE
* rat check successful
* built binary distribution, ran json batch ingestion and some queries
binary package:
* verified checksum and signature
* checked for LICENSE and NOTICE
* ran MSQ ingestion and som
+1 (binding)
src package:
* verified checksum and signature
* checked for LICENSE and NOTICE
* rat check successful
* built binary distribution, ran MSQ ingestion, kafka ingestion,
compaction, then some queries
binary package:
* verified checksum and signature
* checked for LICENSE and NOTICE
* r
+1 (binding)
src package:
* verified checksum and signature
* checked for LICENSE and NOTICE
* rat check successful
* built binary distribution, ran native batch ingestion, kafka
ingestion, and some queries
binary package:
* verified checksum and signature
* checked for LICENSE and NOTICE
* ran M
The Apache Druid team is proud to announce the release of Apache Druid
31.0.1. Druid is a high performance analytics data store for
event-driven data.
Apache Druid 31.0.1 contains important bug fixes for topN queries and
complex metric compression and some additional fixes related to the
31.0.0 re
Thanks to everyone who participated in the vote! The results are as follows:
Clint Wylie: +1 (binding)
Laksh Singla: +1 (binding)
Karan Kumar: +1 (binding)
The vote has passed with 3 binding +1's.
-
To unsubscribe, e-mail
> > Do we really need to wait for Hadoop runtime to support Java 17 if the
> > > Hadoop client jars themselves can be used in JDK 17 runtime? Spark
> > dropped
> > > support for Java 11 but I think, spark jobs can still use Hadoop client
> > > code. So I am not
Hi all,
I have created a build for Apache Druid 31.0.1, 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/17534
The release candidate has been tagged in GitHub as
druid-31.0.1-rc2
t; I do want to note that in addition to the defaults being SQL compatible
> since Druid 28, the docs also list the legacy mode as deprecated. So the
> timing makes sense for removal in Druid 32.
>
> Gian
>
> On Mon, Dec 16, 2024 at 13:45 Clint Wylie wrote:
>
> > I pla
I am stopping the vote because I have found a regression with topN
queries using query granularity other than 'ALL' in the 31 release,
the fix is https://github.com/apache/druid/pull/17565, will make a new
RC once it is merged and backported.
---
ge:
> > - verified checksum and signature
> > - ingested sample wikipedia dataset, ran some queries, reindexed with range
> > partitioning
> >
> > docker:
> > - verified checksum
> > - ingested sample wikipedia dataset, ran some queries, reindexed with range
>
o migrate over their queries.
>
> On Fri, Jan 26, 2024 at 4:55 AM Clint Wylie wrote:
>
> > >Are there any performance implications in making those the defaults?
> > For numeric columns without null values there should be no impact. For
> > numeric columns with null values,
Hey everyone,
It is about that time again to take a pulse on how commonly Hadoop
based ingestion is used with Druid in order to determine if we should
keep supporting it or not going forward.
In my view, Hadoop based ingestion has unofficially been on life
support for quite some time as we do not
Now that we have removed support for Java 8, I wanted to start a
discussion about dropping support for Java 11 as well since it is also
pretty old, and making 17 the minimum supported version. There are a
lot of nice language features with newer java versions, so getting a
bit more aggressive about
Hi all,
I have created a build for Apache Druid 31.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/17534
The release candidate has been tagged in GitHub as
druid-31.0.1-rc1
Hi all,
I want to make a patch release for 31.0.0 due to an ugly bug with the
new complex metric compression feature. The bug is caused by the byte
order being incorrectly set on the buffers returned from the
compressed column and can cause corruption and/or out of memory
exceptions with hyperUniq
+1 from me for deprecating first then removing. I'd also like to
officially support java 21 before we totally drop support, at least
experimentally, but preferably fully. We already run unit tests with
21, so maybe we could transition the java 8 integration tests to use
21 instead? I've also been u
+1 (binding)
src package:
- verified checksum and signature
- LICENSE and NOTICE present
- rat check passed
- built binary distribution, ran MSQ ingestion, ran some queries
binary package:
- verified checksum and signature
- LICENSE and NOTICE present
- ran native ingestion, ran some queries
doc
ansition as painless as
possible before we remove it.
On Mon, Jan 22, 2024 at 9:54 AM Xavier Léauté
wrote:
>
> Two questions:
> - Are there any performance implications in making those the defaults?
> - Would this break compatibility for any existing native queries?
>
> On
Hi all,
I wanted to discuss the deprecation and removal of the Druid configs
related to SQL compatibility, with the eventual goal of always running
in SQL compatible mode. As of Druid 28, these are the default, but in
the interest of dramatically reducing complexity and removing a ton of
code, and
+1 (binding)
src package:
- verified checksum and signature
- check for LICENSE and NOTICE
- rat check passed
- built binary distribution, ran MSQ quickstart, ran some queries,
tested result cache issue
binary package:
- verified checksum and signature
- check for LICENSE and NOTICE
- ran native
Hi all, just wanted to start a thread to discuss removing the 'auto'
strategy from the native search query, which is the only thing that
uses the 'estimateSelectivity' method of
https://github.com/apache/druid/blob/master/processing/src/main/java/org/apache/druid/segment/index/BitmapColumnIndex.jav
+1 (binding)
src package:
- verified checksum and signature
- check for LICENSE and NOTICE
- rat check passed
- built binary distribution, ran MSQ quickstart, tested some new
features and ran queries
binary package:
- verified checksum and signature
- check for LICENSE and NOTICE
- tested some ne
+1 (binding)
src:
- verified LICENSE/NOTICE present
- verified signature/checksum
- RAT check passed
- built binary distribution, ingested some data, ran some queries
bin:
- verified LICENSE/NOTICE present
- verified signature/checksum
- ingested some data, ran some queries
docker:
- verified ch
Is anyone opposed to removing group-by v1? I think it would allow us
to simplify quite a lot of stuff. While it would very nice to
implement 'growable' buffer aggregators so that the v2 algorithm could
be a bit more flexible and finally cover the only potential reason I
can imagine people might sti
obvious +1 from me
On Tue, Jun 27, 2023 at 11:42 PM Gian Merlino wrote:
>
> I'd like to propose dropping support for Hadoop 2 in Druid 28. Not the very
> next release (which I assume will be Druid 27) but the one after that,
> likely late 2023 timeframe.
>
> In 2021, we had a discussion about mov
rad, thanks!
On Tue, Jun 20, 2023 at 11:57 PM Amatya Avadhanula wrote:
>
> Hi
>
> I would like to volunteer to be the release manager for 26.0.1
>
> On 2023/06/21 06:21:07 Clint Wylie wrote:
> > Hi all,
> >
> > We found a couple of bugs related to the Kafk
Hi all,
We found a couple of bugs related to the Kafka input format which I
think are worth making a small 26.0.1 patch release. This is mainly
due to the fact that we modified the web-console data loader to always
use the Kafka input format in 26.0.0 instead of just the payload
format, increasing
+1, afaict we have been following these guidelines already without knowing it
On Thu, Jun 1, 2023 at 8:48 AM Atul Mohan wrote:
>
> +1
> The requirements called out in the policy doc seem reasonable to me.
>
> Thanks for driving this effort!
>
> On Wed, May 31, 2023 at 1:10 AM Abhishek Agarwal
>
The Apache Druid team is proud to announce the release of Apache Druid 26.0.0.
Druid is a high performance analytics data store for event-driven data.
Apache Druid 26.0.0 contains over 390 new features, performance
enhancements, bug fixes, and major documentation improvements from 65
contributors.
Thanks to everyone who participated in the vote! The results are as follows:
Vadim Ogievetsky: +1 (binding)
Suneet Saldanha: +1 (binding)
Clint Wylie: +1 (binding)
The vote has passed with 3 binding +1s.
Thanks
Clint
-
To
/ NOTICE present
> - verified signature / checksum
>
> docker:
> - Pulled and ran locally
> - Ingested data, ran queries
> - Running the docker image on an M1 mac was extremely slow, but it was
> quick on older hardware.
>
> On 2023/05/19 19:28:05 Clint Wylie wrot
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
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
Found a regression, RC3 vote will start soon.
-
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
For additional commands, e-mail: dev-h...@druid.apache.org
Hi all,
I have created a build for Apache Druid 26.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/14064
The release candidate has been tagged in GitHub as
druid-26.0.0-rc2
Cancelling the vote because of an ugly issue with the new 'auto'
column schema that can result in breaking SQL schemas because it
causes segment metadata to fail to refresh.
-
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.o
Found a pretty ugly bug with the new 'auto' stuff so am going to
cancel this vote and make an RC2
On Sat, May 13, 2023 at 1:56 PM Clint Wylie wrote:
>
> I forgot to mention that I had to refresh the expiration on my gpg key
> (I think I did everything correctly), but I am uns
I forgot to mention that I had to refresh the expiration on my gpg key
(I think I did everything correctly), but I am unsure if voters might
need to get the updated keys on their side for stuff to validate
correctly.
On Fri, May 12, 2023 at 1:07 PM Clint Wylie wrote:
>
> FYI when running
ng of the website, there are a couple more doc only changes I am
aware of that will be backported to the 26 release branch, and I will
update the staging website once they are merged.
On Fri, May 12, 2023 at 12:39 PM Clint Wylie wrote:
>
> Hi all,
>
> I have created a build for Ap
Hi all,
I have created a build for Apache Druid 26.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/14064
The release candidate has been tagged in GitHub as
druid-26.0.0-rc1
Hey all,
It is about that time again to think about doing another release. I
volunteer to be release manager, and if no objections will aim to make
the branch around the first week of April.
Please use this thread to call to attention anything which should be
resolved before we make the release b
Hi all,
I want to discuss moving druid-core, extendedset, and druid-hll into
druid-processing to simplify our code structure and dependencies a
bit. We've been discussing doing something like this off and on for
quite a lot of years now, re
https://github.com/apache/druid/issues/4312, and we've do
+1 (binding)
src:
- verified LICENSE/NOTICE present
- verified signature/checksum
- RAT check passed
- built binary distribution, ingested some data, ran some queries
bin:
- verified LICENSE/NOTICE present
- verified signature/checksum
- ingested some data, ran some queries
bin (hadoop3):
- veri
+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- RAT check passed
- built binary distribution, ran into an issue with CVE-2022-1471
failing on druid-kubernetes-extensions, I don't think this needs to be
a blocker
- tested msq ingestion in binary distribution, succ
+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- compiled, ran checks, unit tests, ran into some issues with tests
due to being on an m1 mac, but i don't think they are blockers
- built binary distribution, ingested native batch quickstart data and
ran some querie
+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- compiled, ran checks, unit tests, ran into some issues with
CVE-2022-39135 which was announced a couple of days ago, but I don't
believe we are impacted; also an issue with parquet tests due to being
on an M1 mac wi
If we remove RealtimeIndexTask and AppenderatorDriverRealtimeIndexTask
then we can remove EventReceiverFirehoseFactory. The former was
primarily used by tranquility which has been sunset, the latter I'm
not sure was ever used for anything. I'm personally in favor of
removing both of them since push
+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- compiled, ran checks, unit tests
- built binary distribution, ingested batch quickstart data and ran some queries
binary package:
- verified signature/checksum
- LICENSE/NOTICE present
- kafka ingestion quickstart
-1 (binding)
The RAT check, mvn apache-rat:check -Prat, fails for me. it looks like
there are some stray files in the source distribution:
extensions-core/kubernetes-extensions/.attach_pid19113
extensions-core/druid-ranger-security/.attach_pid15985
possibly due to running tests in the packaging p
+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- compiled, ran checks, unit tests
- built binary distribution, ingested some data and ran some queries
binary package:
- verified signature/checksum
- LICENSE/NOTICE present
- ingested some data and ran some queries
Also a +0 from me, because the fix for the issue Gian mentioned is
available in https://github.com/apache/druid/pull/12056 and it seems
low risk
Release looked good otherwise, so anyone that doesn't want to wait
would probably be ok to go ahead and start using RC1 if they don't
mind the logging is
Severity: low
Description:
In the Druid ingestion system, the InputSource is used for reading
data from a certain data source. However, the HTTP InputSource allows
authenticated users to read data from other sources than intended,
such as the local file system, with the privileges of the Druid se
The Apache Druid team is proud to announce the release of Apache Druid 0.22.0.
Druid is a high performance analytics data store for event-driven data.
Apache Druid 0.22.0 contains over 400 new features, performance
enhancements, bug fixes, and documentation improvements from 73
contributors. Major
t; > >
> > > > *Binary*
> > > >
> > > >- NOTICE and LICENSE files present
> > > >- Verified signatures and checksums
> > > >- ran cluster with pre-packaged binaries and ran both native and
> > kafka
> > &g
Thanks to everyone who participated in the vote! The vote has passed
with 4 binding +1s and 1 non-binding +1.
Clint Wylie: +1 (binding)
Frank Chen: +1 (non-binding)
Suneet Saldanha: +1 (binding)
Jihoon Son: +1 (binding)
Maytas Monsereenusorn: +1 (binding
Hi all,
I have created a build for Apache Druid 0.22.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/11657
The release candidate has been tagged in GitHub as
druid-0.22.0-rc1
My understanding of that thread suggests that
https://incubator.apache.org/ip-clearance/ip-clearance-template.html
is the process that our PMC does before the IPMC can continue the
clearance process, meaning someone on our PMC fill out i think this
form
http://svn.apache.org/repos/asf/incubator/pu
I know I mentioned I was going to start the 0.22 release like over a
month ago, but haven't really had the chance to actually work on that
until now...
Since it has been a while, I wanted to start a thread to mention I'm
currently looking over the changes between 0.21 and 0.22, as well as
the set
The Apache Druid team is proud to announce the release of Apache Druid 0.21.1.
Druid is a high performance analytics data store for event-driven data.
Apache Druid 0.21.1 is a minor release to fix regressions introduced in 0.21.0.
Source and binary distributions can be downloaded
from:https://drui
id for at least the
> > remainder
> > > of the year and possibly longer.
> > >
> > > Will
> > >
> > >
> > > <http://www.verizonmedia.com>
> > >
> > > Will Lauer
> > >
> > > Senior Principal Architect, Audien
E present
> > > - started nano-quickstart cluster and ran both native ingestion and
> Kafka
> > > ingestion
> > >
> > > docker
> > > - started docker on Linux(CentOS) and ran both native ingestion and
> Kafka
> > > ingestion followed by
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)
Frank Chen: +1 (non-binding)
Jihoon Son: +1 (binding)
Jon Wei: +1 (binding)
Hi all,
I've been assisting with some experiments to see how we might want to
migrate Druid to support Hadoop 3.x, and more importantly, see if maybe we
can finally be free of some of the dependency issues it has been causing
for as long as I can remember working with Druid.
Hadoop 3 introduced s
Hi all,
I have created a build for Apache Druid 0.21.1, 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/11249
The release candidate has been tagged in GitHub as
druid-0.21.1-rc2
cancelling to add fix for docker volume permissions,
https://github.com/apache/druid/pull/11299
ies and executed native batch
> ingestion followed by basic queries and api issued kill task on data.
> Tested with HDFS deep store.
>
> On Fri, May 14, 2021 at 2:42 PM Clint Wylie wrote:
>
> > Hi all,
> >
> > I have created a build for Apache Druid 0.21.1, releas
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
or deep
storage, though I haven't had the chance to confirm this yet.
On Fri, May 14, 2021 at 12:42 PM Clint Wylie wrote:
> Hi all,
>
> I have created a build for Apache Druid 0.21.1, release
> candidate 1.
>
> Thanks to everyone who has helped contribute to the release! You
Hi all,
I have created a build for Apache Druid 0.21.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/11249
The release candidate has been tagged in GitHub as
druid-0.21.1-rc3
Hi Jason,
Thanks for thinking about this, I would agree that the system tables are a
pain point, especially the segments table in larger clusters.
In the mid term, I think that some of us have been thinking that moving
system tables into the Druid native query engine is the way to go, and have
be
I agree with Jihoon that deciding what should and shouldn't be in a release
on a feature by feature basis is way too expensive to do at release time.
I think the PR that adds a thing is the most appropriate venue to discuss
whether or not a change should be accepted to a release, unless a major
iss
Hi all,
>From the 0.21 release vote thread,
https://lists.apache.org/thread.html/r72b70181bd61585703fdc2a4699b28701bc437da8410444106f2c57a%40%3Cdev.druid.apache.org%3E,
discussing bug https://github.com/apache/druid/issues/11166, I think we've
decided it is best to do a 0.21.1 patch release that i
I'll take care of 0.21.1 Jihoon since you've handled the last few, and I
was planning on volunteering to get the ball rolling on 0.22 pretty soon
anyway.
On Sat, May 1, 2021 at 1:26 PM Jihoon Son wrote:
> Thanks Xavier, it makes sense to me.
> I will start a new thread to discuss what should be
+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- compiled, ran checks, unit tests
- built binary distribution, ingested some data and ran some queries
binary package:
- verified signature/checksum
- LICENSE/NOTICE present
- ingested some data and ran some queries
+1 for splitting releases. I don't think we need to delay 0.22 too much,
just enough so they are not on top of each other.
On Wed, Mar 31, 2021 at 11:20 AM Suneet Saldanha
wrote:
> +1 for delaying the 0.22 release as well
>
> 0.21 is already 5+ months behind the 0.20 release, so it's not like it
Hi all,
I've noticed that the integration tests in Travis that use the segments
stored in the static.druid.io s3 bucket are all failing, starting sometime
between yesterday and today. Looking closer, they are failing to load on
historicals with a 403 Forbidden error.
Is anyone familiar with the d
It seems like this will basically only affect release managers.
I am maybe -1 since I have personally had to force push to a release branch
while making an RC, when I optimistically pushed the tags and then found a
mistake doing preflight checks before sending the artifacts out to vote. I
did this
+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- compiled, ran unit tests (I actually had issue with a Kafka supervisor
test also, testFailedInitializationAndRecovery, but I think it might be
environmental, because I am seeing this same issue with 0.19 src package
The Apache Druid team is proud to announce the release of Apache Druid
0.19.0.
Druid is a high performance analytics data store for event-driven data.
Apache Druid 0.19.0 contains around 200 new features, bug fixes,
performance enhancements, documentation improvements, and additional test
coverage
Thanks to everyone who participated in the vote! The results are as follows:
Clint Wylie: +1 (binding)
Jihoon Son: +1 (binding)
Furkan KAMACI: +1 (binding)
Thanks for the votes, counting myself puts us at three +1 binding. I'll
start the thread to announce the results and continue the release process
soon.
[ERROR] Failed to execute goal on project druid-ranger-security: Could not
> resolve dependencies for project
> org.apache.druid.extensions:druid-
Hi all,
I have created a build for Apache Druid 0.19.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/10139
The release candidate has been tagged in GitHub as
druid-0.19.0-rc1
Hi all,
It's about that time again to start preparing to make the next release (the
last major branch was created in March) - I volunteer to be release
manager. I will probably try to make the branch sometime in the next week
or so, to allow us time to start seriously testing to get everything in
+1
Would it also be worth including
https://github.com/apache/druid/pull/9723? Additionally
if we can confirm and get a fix for
https://github.com/apache/druid/issues/9736 in time it would be worth
including, but if not it might also be good enough to warrant a 0.18.2.
On Tue, Apr 21, 2020 at 10:
+1 (binding)
src package:
- verified signature/hash
- checked LICENSE and NOTICE
- rat check and unit tests passed
- built distribution, tested native batch quickstart and queries
bin package:
- verified signature/hash
- checked LICENSE and NOTICE
- tested kafka quickstart and queries
docker:
-
-1 (binding)
It looks like there are some extra code coverage analysis results in the
source package in apache-druid-0.18.0-src/web-console/coverage/ which is
causing this command to fail:
mvn apache-rat:check -Prat
since these files have no license information.
On Wed, Apr 15, 2020 at 2:52 PM
+1 (binding)
src package:
- verified signature/hash
- LICENSE and NOTICE lgtm
- tests passed
- built binary distribution and ran through native batch quickstart, issued
queries successfully
bin package:
- verified signature/hash
- LICENSE and NOTICE lgtm
- ran native batch quickstart, issued quer
don/events/267380924/
> >2. January 28th in Athens -
> >https://www.meetup.com/Athens-Big-Data/events/266900242/
> >3. January 29th in Tel-Aviv (hosted by Nielsen) -
> >
> https://www.meetup.com/Big-things-are-happening-here/events/267578817/
> >
> > So
Hey all,
I put together a draft for the quarterly ASF board report due tomorrow,
sorry for the short notice. Let me know if I missed anything or should make
any changes. Thanks!
-
## Description
Apache Druid is a high performance real-time analytics database. It is
designed for work
Hey all,
I've put together our ASF board report for Feb 2020, and while I haven't
yet determined how to actually submit it, I wanted to go ahead and send out
a copy to the dev list in case anyone has any feedback.
---
## Description
Apache Druid is a high performance real-time analytics databa
+1 (binding)
src package:
- verified signature/hash
- verified LICENSE and NOTICE present
- verified packaging appears successfully de-incubated (no DISCLAIMER,
references to incubating/incubator, versions look good)
- RAT checks passed
- compiled, ran unit and integration tests
- built binary art
Apologies for the delay, I haven't had much extra time to review PRs lately
because I've been focusing on testing and fixing up bugs for 0.17 release,
but I will try to have a look at this PR sometime in the next couple of
weeks because once upon a time I also implemented an autoscaler for google
c
I strongly agree with Gian about underscores being ugly, though I think
your suggested formatting would be just as readable (to me at least) using
just camel-case and would also remain consistent with the styling of the
majority of Druids existing tests. I share similar concerns with the others
on
1 - 100 of 163 matches
Mail list logo
