+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
+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
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 Wed, Jan 17, 2024 at 5:53 PM Clint Wylie wrote:
>
> > Hi all,
> >
&g
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,
+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
+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
+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
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
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
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
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,
+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
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
/ 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
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
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
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:
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 unsure if vot
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
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 Apache
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
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
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
+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):
-
+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,
+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
+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
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
+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
+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
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
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
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.
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
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
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
> of the year and possibly longer.
> > >
> > > Will
> > >
> > >
> > > <http://www.verizonmedia.com>
> > >
> > > Will Lauer
> > >
> > > Senior Principal Architect, Audience & Advertising Reporting
> > > Data
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
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
cancelling to add fix for docker volume permissions,
https://github.com/apache/druid/pull/11299
s 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, release
>
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
, 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 can read
> the p
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
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
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
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'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
+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
+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
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
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
+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
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
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
>
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
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
+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
80924/
> >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/
> >
> > Sorry if I left o
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
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
+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
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
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 (non-binding)
src package:
- verified signature/hash
- ran RAT check
- checked for LICENSE, NOTICE, and DISCLAIMER
- compiled and ran unit tests
- built binary distribution, ran quickstart on built artifacts
bin package:
- verified signature/hash
- checked for LICENSE, NOTICE, and DISCLAIMER
ect",
> > > > > > be and hereby is established pursuant to Bylaws of the
> > > > > > Foundation; and be it further
> > > > > >
> > > > > > RESOLVED, that The Apache Druid Project be and hereby is
> > > > > > responsible for the
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.
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
Thanks to everyone who participated in the vote! The results are as follows:
Clint Wylie: +1 (non-binding)
Jihoon Son: +1 (binding)
Furkan KAMACI: +1 (non-binding)
Julian Hyde: +1 (binding)
David Lim: +1 (binding)
Surekha Saharan: +1 (non-binding)
Additionally, I think we should be able to carry
j6crw9e...@mail.gmail.com%3e
> > > <
> > >
> >
> http://mail-archives.apache.org/mod_mbox/calcite-dev/201906.mbox/%3CCA+EpF8vwOceAeUjv+DJU=zqrkoqu3dwckwsypqhrj6crw9e...@mail.gmail.com%3E
> > >
> > >
> > >
> > >
> > >
> &
tests) using JDK 8 on Ubuntu. Checked that src.tar.gz
> matches git commit.
>
> Julian
>
>
> Julian
>
> On Sun, Sep 15, 2019 at 7:24 PM Clint Wylie wrote:
> >
> > > The vote email must contain the checksums of the artifacts we are
> voting
> > on.
> &g
ks!
Clint
On Sun, Sep 15, 2019 at 6:22 PM Julian Hyde wrote:
> -1
>
> The vote email must contain the checksums of the artifacts we are voting
> on.
>
> No need for a new RC; I change my vote if the release manager sends an
> email with the checksums.
>
> Julian
>
&
Hi all,
I have created a build for Apache Druid (incubating) 0.16.0, release
candidate 3.
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/8369
The release candidate has been tagged in
Cancelling vote for RC2 due to
https://github.com/apache/incubator-druid/pull/8535. I will create an RC3
as soon as possible.
Unfortunately we have found a rather critical bug with group by query
cache, so I am going to send out a cancel of this vote soon. A PR for the
fix has been opened, https://github.com/apache/incubator-druid/pull/8535,
but apologies for the false start.
On Thu, Sep 12, 2019 at 6:00 AM Clint Wylie
Hey all,
I have created a build for Apache Druid (incubating) 0.16.0, release
candidate 2.
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/8369
The release candidate has been tagged in
Cancelling vote for RC1 due to
https://github.com/apache/incubator-druid/pull/8506. I will try to make an
RC2 and get a new vote started later today if possible.
Unfortunately a small issue was found, going to cancel this vote and make
an RC2 later today.
On Wed, Sep 11, 2019 at 12:44 AM Clint Wylie wrote:
> Hi Druids,
>
> I have created a build for Apache Druid (incubating) 0.16.0, release
> candidate 1.
>
> Thanks for every
Hi Druids,
I have created a build for Apache Druid (incubating) 0.16.0, 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/8369
The release candidate has been tagged in
Staging site is live at https://druid.staged.apache.org/ (had to rebase
asf-staging on asf-site after merging that PR)
On Tue, Sep 10, 2019 at 4:32 PM Clint Wylie wrote:
> I have druid-0.16.0-incubating-rc1 docs built to the asf-staging branch
> and opened PR https://github.com/apache/inc
Jonathan Wei wrote:
> +1, that sounds useful to me.
>
> On Thu, Sep 5, 2019 at 2:23 PM Himanshu wrote:
>
> > +1 , can't think of any reason to not do it, thanks.
> >
> > On Thu, Sep 5, 2019 at 1:15 PM Clint Wylie wrote:
> >
> > > Hey eve
Hey everyone,
I saw the email last night to committers that announced the '.asf.yaml'
feature,
https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories,
and was thinking it would be nice to get set up for
https://github.com/apache/incubator-druid-website, so we
I tried testing hadoop with java 11 using the quickstart tutorial, but ran
into the following issue on peon before it even got to hadoop
2019-08-28T22:14:56,959 ERROR [task-runner-0-priority-0]
org.apache.druid.indexing.common.task.HadoopIndexTask - Got invocation
target exception in run(),
//github.com/apache/incubator-druid/issues/8338
>
> It could well be something weird in our setup & since we're not seeing
> anyone else reporting it, that seems likely. Anyone able to triage the
> issue & my suggested fix?
>
> Cheers,
> Dylan
>
>
> On Thu,
gt; https://gist.github.com/Fokko/72b57edd47e2d2da08426bf6caca6d55
>
> This also killed the processes. Not sure if this is already fixed in
> master. I'll dive into it later.
>
> Cheers, Fokko
>
> Op di 27 aug. 2019 om 09:41 schreef Clint Wylie :
>
> > I just tested l
I just tested latest master with openjdk 12 and saw the same error in my
logs, however overall things appeared to be functioning. I was able to
bring up a cluster, index some data with native batch, and query the
resulting segments. Maybe we call it "experimental" and let people help us
shake out
1 - 100 of 136 matches
Mail list logo
