Hi Druids,
The Druid PMC has invited George Wu (@georgew5656 on GitHub)
to become a committer and we are pleased to announce that
George has accepted.
George has made major improvements to the middle manager less ingestion
capabilities for Druid on Kubernetes. Most recently, he added the ability
The Project Management Committee (PMC) for Apache Druid
has invited Rahul Gidwani and we are pleased to announce that
he has accepted.
Rahul's major contribution has been introducing the ability to launch
ingestion tasks as Kubernetes jobs aka middle managerless ingestion.
Congrats Rahul!
+1 (binding)
src:
- verified LICENSE / NOTICE present
- verified signature / checksum
- RAT check passed
- built binary, ingested wikipedia data, ran some queries
bin:
- verified LICENSE / NOTICE present
- verified signature / checksum
- Ran through jupyter notebook tutorial
- Ingested data in
Hey Druids,
The Druid PMC has invited Victoria Lim (@vtlim on GitHub)
to become a committer and we are pleased to announce that
Victoria has accepted.
Victoria has made major improvements to the docs like refactoring the
sql query docs, adding docs for cluster tiering and refactoring the
Congratulations Abhishek! And thanks for all your work shepherding the
0.23.0 release!!
On Tue, Jun 7, 2022 at 12:04 PM Gian Merlino wrote:
> Hey Druids,
>
> The Druid PMC has invited Abhishek Agarwal (asf id abhishek, github id
> abhishekagarwal87) to become a PMC member, and we are pleased to
Hi Druids,
I'd like to propose we bump the version of Druid to 24.0 for the next
release.
I think this would be beneficial because it better reflects the maturity of
the Druid
project that is actively used in many production use cases. This was
discussed briefly
in the Druid 0.23.0 release thread
>>> year and month in the version.
> >>>> For example, if we're going to release a version in May this year, the
> >>> main
> >>>> version can be 22.5.
> >>>>
> >>>>
> >>>> Versioning is one thing, LTS strategy should also be clear.
>
Hi all,
I've been thinking that we should consider re-branding this release as
the Druid 23.0 instead of 0.23 release. I think this is appropriate because
typically a `0.XX` software version implies that the software is in it's
infancy.
Druid is quite mature, and we've been putting good
Hey Druids,
The Druid PMC has invited Kashif Faraz (@kfaraz on GitHub)
to become a committer and we are pleased to announce that
Kashif has accepted.
Kashif has contributed several impactful features to Druid like support
for range partitioning on multiple dimensions and the ability to route sql
+1 (binding)
*Source code*
- NOTICE and LICENSE files present
- verified signatures and checksums
- git.version file is present and correct
- maven build passes locally
- tests are green on travis for the latest commit in the release branch
Hey Druids,
The Druid PMC has invited Yi Yuan (@bananaaggle on GitHub)
to become a committer and we are pleased to announce that Yi has accepted.
Yi has contributed several impactful features to Druid like inputFormat
support for protobuf,
avro stream and thrift, as well as improving our support
Hey Druids,
The Druid PMC has invited Charles Smith (@techdocsmith on GitHub)
to become a committer and we are pleased to announce that Charles has
accepted.
Charles has made significant contributions to the Druid docs including
refactoring of
the query caching documentation, better docs around
+1 - thank you for volunteering to be release manager this cycle Clint.
On Mon, Aug 9, 2021 at 12:05 PM Clint Wylie wrote:
> 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
moment.
>
> Jihoon
>
> [1] https://www.apache.org/legal/release-policy.html#policy
>
> On Fri, Apr 23, 2021 at 6:26 PM Suneet Saldanha
> wrote:
> >
> > Hi Druids,
> >
> > I was thinking about the 0.21.0 release vote that was just happening, and
>
Hi Druids,
I was thinking about the 0.21.0 release vote that was just happening, and
found it tedious to help with the vote because I needed to build the code
from source as well as run all the tests on my local machine. This got me
thinking about what are the key steps that we should check
Thanks for these helpful links Jihoon. I have started trying to follow the
steps. Given the other dev thread about the vulnerability job being broken
- should we wait before trying to do the verification? Or can I skip the
CVE check since an older run when the tag was made was successful?
On Wed,
I've added a suppression for the flagged CVE in
https://github.com/apache/druid/pull/11093. This should prevent us from
getting spammed because of a known issue that we plan on fixing. This way,
we can trust that any email about the failing cron job is a real failure.
On Fri, Apr 9, 2021 at 6:52
I agree with the CVSS string that you shared. The privileges required
should be high, since only an admin can exploit this vulnerability.
I think it's ok if we keep the attack complexity at low, and state in the
CVE that it only affects users with the MySQL JDBC driver loaded. So in
this case, a
+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's a
hard requirement to stick to a 3 month release schedule.
+ the longer cycle time allows users to test features in 0.21 and harden
them for 0.22
On Wed, Mar 31, 2021 at 10:52 AM
Congratulations Zach! Thanks for the contributions - finally having LDAP
integration tests is amazing!
On Tue, Mar 23, 2021 at 8:38 PM Jonathan Wei wrote:
> Hey Druids,
>
> The Druid PMC has invited Zach Sherman (@zachjsh on GitHub)
> to become a committer and we are pleased to announce that
Congratulations Yue! Thanks for the contributions - especially dynamic
auto-scaling kafka ingest!
On Tue, Mar 23, 2021 at 8:38 PM Jonathan Wei wrote:
> Hey Druids,
>
> The Druid PMC has invited Yue Zhang (@zhangyue19921010 on GitHub)
> to become a committer and we are pleased to announce that
Congratulations Frank! Thanks for the Aliyun OSS deep storage extension and
the support for units on byte related properties - that's a really cool
ease of use contribution!
On Tue, Mar 23, 2021 at 8:36 PM Jonathan Wei wrote:
> Hey Druids,
>
> The Druid PMC has invited Frank Chen (@FrankChen021
Congratulations Abhishek! Thanks for your code reviews and cool
contributions like the GROUPING_ID function and caching for join queries
On Tue, Mar 23, 2021 at 8:36 PM Jonathan Wei wrote:
> Hey Druids,
>
> The Druid PMC has invited Abhishek Agarwal (@abhishekagarwal87 on GitHub)
> to become a
Congratulations Steve! Thanks for your help with making the Druid docs
easier to consume!
On Fri, Mar 26, 2021 at 1:43 PM Jonathan Wei wrote:
> Hey Druids,
>
> The Druid PMC has invited Steve Hetland (@sthetland on GitHub)
> to become a committer and we are pleased to announce that Steve has
>
I don't have all the answers, but there are helpful notes in the README in
the integration-tests sub forlder. Some responses to your questions inline.
I think all the sections under
I will look into this failure over the next week or so. It's probably a
small misconfiguration in the travis job since the logs seem to indicate no
high dependency vulnerabilities were flagged
On Wed, Feb 17, 2021 at 7:00 PM Travis CI wrote:
> Build Update for apache/druid
>
Hi Druids!
I've been thinking about what it would take for us to remove support for
JDK 8 in the 0.21 release, and officially add support for JDK 11.
I see that unit tests for jdk11 were added about 1+ year ago in Aug 2019 -
https://github.com/apache/druid/pull/8400
And integration tests were
ed quality level of the project.
> >
> > Now, thinking about specific features, I suggest we classify the current
> > experimental features in the following way:
> >
> > - Java 11 support: Beta or GA (depending on how good the test coverage
> is)
> > - HTT
Suneet Saldanha
wrote:
> Hi Druid devs!
>
> I've been thinking about our release process and would love to get your
> thoughts on how we manage new features.
>
> When a new feature is added is it first marked as experimental?
> How do users know which features are experimenta
Hi devs,
I've been writing tests in druid for a little bit now and wanted to hear
your thoughts on using EasyMock as the mocking framework.
I've found it pretty tedious to write tests using easy mock because it's
very verbose, and requires me to do a lot of set up for the mock objects.
Because
Hello all,
I've had to triage a couple of issues with failed index tasks in druid and
find it to be a little intimidating some times. I usually search in github
issues for a similar issue, then the druid docs and maybe poke around the
code a little bit based on the stack-trace to try and figure
tFilterMatches" helper is used to create
> > test
> > > > cases that say 'this filter should match these rows'.
> > > >
> > > > Other notes:
> > > >
> > > > - IMO, the underscores are ugly, but acceptable if they buy us
> &
Hello,
I've started writing tests in the druid repo and would like to propose a
new test naming structure for the project. Inspired by this thread -
https://www.mail-archive.com/dev@druid.apache.org/msg02426.html but focused
only on the naming of tests. I'd like to propose we start using the
33 matches
Mail list logo
