Route 1: run ANALYZE TABLE ... REFRESH METADATA on the tables to have
them added to the tables collection in INFORMATION_SCHEMA.
Route 2: Use CREATE VIEW to create a view for every data set to be
exposed to MicroStrategy. Views are added to INFORMATION_SCHEMA.
On 2020/12/19 03:37, Indian A
Are you starting Drill using systemd? If so, see the LimitNOFILE option.
On 2021/06/21 07:28, Dony Dong (Jira) wrote:
Dony Dong created DRILL-7953:
Summary: Query failed with (Too many open files)
Key: DRILL-7953
Hi all
Based on an initiative of Cong Luo's, I've just implemented support for
doc pages in multiple languages on the Drill website. There are
currently a handful of farcically translated pages in Simplified Chinese
which I put there for demonstration purposes and which can be found by
First time I've seen spam planted in JIRA tickets. Welcome to the
future 冷.
On 2021/07/02 14:19, Cheryl Valentine (Jira) wrote:
Cheryl Valentine created DRILL-7965:
---
Summary: mercari fees Technology Trade Show
Key:
Hi
I'm looking for advice on a "to bundle or not to bundle" question for a
PR I'm working on which enables the reading and writing of all of the
compression codecs standardised for Parquet. That amounts to adding
support for LZO, LZ4, Brotli and Zstandard.
Apart from some minor code
I started to answer "1. The Drill website" thinking that it's better to
consolidate the docs rather than fragment them. But then I realised
that these docs are for a different audience than those on the website,
so having them somewhere else is less of a concern. And possibly even
better
On the documentation side of things, introducing .asf.yaml enabled some
improvements and better alignment with what other projects do. There are
new instructions in drill-site/master/README.md but here's the need-to-know.
1. The branch drill/gh-pages is now obsolete. It's full history has
If there are no unpleasant side effects then it sounds like a good idea
to me +1.
On 2021/08/30 23:23, Charles Givre wrote:
Hello Drill Devs,
I’d like to call a vote as to whether we add LGTM automated code check to our
pull requests. This would not replace the current review process, but
Thanks for this luoc. See you at ApacheCon and here's to more exciting
developments in the future.
On 2021/09/04 05:08, luoc wrote:
Hello Guys,
Thank you for your interest in Apache Drill. There are good news for Drill
community.
1. Since 2021.02, the rapid growth in the number of
Hi all
If you browse to https://hub.docker.com/r/apache/drill/tags, you'll see
that we've just started publishing the following new Docker images based
on snapshots of Drill master.
apache/drill:master-openjdk-8 (=master) snapshot of master running on
the openjdk:8 base image
Hi devs
I'd like to propose a change to the defaults for our outbound connection
pool management, at least for JDBC but perhaps ultimately wherever we
can manage it. Currently we are eager about initiating outbound JDBC
connections, bringing up 10 per storage config per drillbit. For
, the HikariCP pool grows
accordingly, up to the configured max.
On 2021/10/19 06:42, James Turton wrote:
Hi devs
I'd like to propose a change to the defaults for our outbound
connection pool management, at least for JDBC but perhaps ultimately
wherever we can manage it. Currently we are eager
2021年10月19日，20:37，James Turton 写道：
HikariCP
that do not use the HikariCP ?
在 2021年10月19日，20:37，James Turton 写道：
HikariCP
out as well,
especially where containers have low overhead (i.e. on Linux)
On Mon, Sep 20, 2021 at 4:32 AM luoc wrote:
Hello James,
Great work. Is it possible to add this NOTICE to Github wiki or docs of
website?
在 2021年9月20日，19:27，James Turton 写道：
Hi all
If you browse to https
Hi all
We've got support for reading and writing using additional Parquet
compression codecs in master now. Here are the footprints of a 25M
record dataset compressed by Drill with different codecs.
| Codec | Size on disk (Mb) |
| -- | - |
| brotli | 87 |
@Ted: yes and the master-X series is quite handy for us to get users to
test whether an unreleased fix solves some issue they've reported.
@Cong: thanks and great point. I have just documented this expanded set
of image tags in https://drill.apache.org/docs/running-drill-on-docker/.
On
at 5:37 AM luoc wrote:
James, you are doing fine.
Is it possible to post a new blog in the website for this?
在 2021年9月29日，20:27，James Turton 写道：
Hi all
We've got support for reading and writing using additional Parquet
compression codecs in master now. Here are the footprints of a 25M reco
Hi all
It's been a couple of months since we consolidated the Drill website in
the apache/drill-site repo and we've been going along fine since then.
To remove duplication and confusion I now propose that we delete the old
docs branches in the apache/drill repo. Specifically,
DRILL-7983 Get running/completed profiles from REST API
DRILL-8015 MongoDB Metastore
DRILL-8028 PDF format
* DRILL-8057 INFORMATION_SCHEMA filter push down is inefficient
(feasibility not yet clear)
On 2021/11/25 09:53, James Turton wrote:
Dear dev community
Please see an update on the Jiras
Thank you to everyone who attended and made this exciting event happen.
I'd like to make special mention of Cong Luo (luoc) and Jingchuan Hu
(kingswan) who honoured the community by staying up to join this first
call quite literally in the middle of the night. I will definitely
learn how to
, James Turton wrote:
Hi all
Thank you everyone for pushing to get us to where we are now, you can
see the results of these efforts below (not to mention other work that
got merged). We've got just three tracked Jiras outstanding. 8057 is
sitting with me and I haven't found an approach that works
Impersonation support for Phoenix plugin (only unit tests
outstanding)
On 2021/12/09 11:03, James Turton wrote:
Apologies, I was aiming for next week Friday and had an off-by-one
error. So we've agreed to delay until 2021-12-17 and we're tracking
the following.
On 2021/12/08 17:40, James
wrote:
Threading is exactly what I would want to avoid.
On Tue, Jan 4, 2022, 3:58 AM James Turton <mailto:dz...@apache.org>> wrote:
Hi all
GitHub Issues allow a conversation thread with rich formatting so I
propose that we use them for meaty topics like this. P
t (since it shouldn't be part of the consensus) and
tag anybody who might have responded. I might even leave a note saying "You
might think X, but that isn't so because of Y" to help later readers.
That is all very, very hard to do in threaded discussions.
On Tue, Jan 4, 2022 at 9:37 A
u might think X, but that isn't so because of Y" to help later
readers.
That is all very, very hard to do in threaded discussions.
On Tue, Jan 4, 2022 at 9:37 AM James Turton <mailto:dz...@apache.org>> wrote:
Ah, and I see now that you said as much already. So a collaborative
datory
for analytics
Jan Soubusta, a user active in Slack, work at company GoodData.CN, and they
have built Drill as an engine into their cloud platform.
2022年1月5日 下午6:18，James Turton 写道：
Just a quick reminder of this week's meetup which occurs at 8am PDT on Friday.
https://zoom.us/j/842911533
Just a quick reminder of this week's meetup which occurs at 8am PDT on
Friday.
https://zoom.us/j/84291153325?pwd=NWZ1MS9lbkVmMHZXWmtXN2loQ0ZZZz09
(Meeting ID 84291153325, passcode 488311)
The same details are also always available on the Community Resources
web page
Thank you, I found and updated a handful of instances.
On 2022/01/03 11:05, luoc wrote:
James, could you please confirm that there is no link to `gh-pages` directly in
the current document?
On Jan 3, 2022, at 16:28, James Turton wrote:
It's been about four months since we moved the Drill
It's been about four months since we moved the Drill website source over
to apache/drill-site. Things have been working fine and we took the
full commit history across when we migrated so I propose to delete this
cruft from apache/drill.
Please reply if you object.
Thanks
James
Hi everyone
Happy new year to one and all, and here's to all the exciting
developments coming our way.
Firstly: Drill 1.20 has not been forgotten. We have been holding off
while debugging some final issues in DRILL-8061, but the freeze is imminent.
We've got another community meetup this
Hi all
GitHub Issues allow a conversation thread with rich formatting so I
propose that we use them for meaty topics like this. Please use the
"Feature Request" issue template for this purpose, and set the issue's
Project field to "Drill 2.0"[1], said project having recently been
created by
Thank you both. Please report these to Apache Infra so that they can
lock out the abusive user account in addition to deleting the spam
ticket. Closing the ticket is good but then it still contaminates the
project's Jira statistics in a minor way and the account may create more.
On
and the Drill website accordingly.
*
*James*
*
On 2021/11/16 20:48, James Turton wrote:
Dear community member
Based on your feedback I've set up a Zoom meeting at 8am PDT on the
last Friday of every month. The details are below, attached as
iCalendar and will shortly be updated on the Drill
o have.
4. *Open floor*: anyone who raises a Zoom hand. The main event! Let's
share ideas about making Drill awesome, and any related topics.
Looking forward to it!
James
On 2021/11/09 11:15, James Turton wrote:
Hello Apache Drill community member!
It's been a few years since the last commun
Hi Maksym
This is a good point, thank you. I wonder if we could restrict the wiki
to "collaborators", or whatever the relevant Github concept is for those
who are able to push to the code repo. I also wonder if there is any
need. Any destructive action could be reverted because the wiki is
that Drill can't do something, but in reality,
it does. Then, someone other, when reading this wrong information on the
official source of the project will believe in it. I think it's wrong and
it's dangerous.
Regards,
Maksym
________
Від: James Turton
Надіслано: 24 лис
as the release manager.
We'll keep a light on for you.
在 2021年11月3日，01:04，James Turton 写道：
Hi luoc
I am willing to help the release in any capacity needed. I know there are
others who have release experience while I do not but I'm sure it can be
learned. I'll have PR #2351 done this week
+1 for this good initiative and your user friendly pages. We had an
idea of making the Dev Wiki entirely info for developers and the Drill
website entirely info for users, but this split was never formalised or
anything so if we prefer to do things differently then we should.
I have improved
Definitely a +1 for this friendlier default behaviour and another +1 for
the prospect of increased consistency across format plugins.
My follow-up questions to the community.
1. Since these are examples of user-breaking changes, and not just in
niche areas, are we approaching a point when
unt||
||group by option||
||order by borda_total desc;||
|
On 2021/11/09 11:15, James Turton wrote:
Hello Apache Drill community member!
It's been a few years since the last community meetup which means that
the next one is *cough* more than a little overdue. I've made a short
form that w
I'm delighted to report that the gold mine of developer information that
is Paul Rogers' Drill wiki has just formed the basis of a new Drill
developer wiki.
https://github.com/apache/drill/wiki
The community would like to thank Paul for this sizeable and valuable
contribution, and for his
2021, at 5:59 AM, luoc wrote:
It cannot get any better than this!
2021年10月30日 下午5:39，James Turton 写道：
I'm delighted to report that the gold mine of developer information that is
Paul Rogers' Drill wiki has just formed the basis of a new Drill developer wiki.
https://github.com/apache/drill/wi
ease share it freely.
Happy Drilling
James Turton
Hi luoc
I am willing to help the release in any capacity needed. I know there
are others who have release experience while I do not but I'm sure it
can be learned. I'll have PR #2351 done this week, it would be nice
(but not critical) to include it.
Thanks
James
On 2021/11/01 16:27, luoc
and please forward it to anyone
you know who might be interested in joining us. The form does not
require any login.
https://forms.gle/57KuDcVPJpQrGY5w7
I'll be in touch again once the responses are in. We look forward to
seeing you.
James Turton
Apache Drill Committer
I like the idea, just can't wrap my head around what the pom file would
need to look like.
On 2021/11/05 23:34, Rumar, Maksym wrote:
Yes, right. Only import the Drill JDBC dependence into the pom file. Embedded
Drill could start on the step of establishing connection and end on the
Just waiting for the join request to sqlline-dev to go through, but I'll
reproduce my response here for this community.
SQLLine is an important project that I've spotted in the wild in
contexts well removed from Apache databases and query engines. E.g. not
long ago I found someone who'd
A last reminder that the first meetup is on Friday this week!
On 2021/11/17 19:23, James Turton wrote:
Inauspiciously, the last Fridays of the first two months both clash
with major holidays, with Friday next week being Thanksgiving in the
US. Never entrust event management to an engineer
here would be to do a bit of diagnosis first. Let's see if we can
figure out what is going wrong and a sense of how much effort is required to
fix. Once we know that, we can decide on how to proceed.
-- C
On Dec 1, 2021, at 8:13 AM, James Turton wrote:
We've picked up a bug: DRILL-8063. It w
as a release blocker. Lazy consensus will apply, i.e. no reply = "I do
not believe this bug should block 1.20".
https://issues.apache.org/jira/browse/DRILL-8063
On 2021/12/01 12:00, James Turton wrote:
Hi all
Given we've had no objections, please strive to merge your PRs for
1.20 by 1
Also, did you do this stuff?
https://drill.apache.org/docs/installing-drill-on-windows/#create-drill-udf-directories-and-change-the-owner
On 2021/12/02 16:21, Charles Givre wrote:
HI there,
The first thing that immediately catches my eye is that you're running a very
old version of Drill.
Dear dev community
Please reply if you *object* to us pushing out the freeze date by one
week to 2021-12-16. The motivation to delay is to try to include more
of the open PRs that we are tracking below, a number of which are
essentially dev-complete but not yet over the line.
*Closed*
be great to include this because we
want to add Druid 0.22 in our Cluster next Year and without this
Ticket we were not be able to use Drill in front of Druid.
Regards,
Christian
‐‐‐ Original Message ‐‐‐
James Turton schrieb am Donnerstag, 9. Dezember
2021 um 10:03:
Apologies, I was aiming
-7978 Fixed width format
DRILL-8057 INFORMATION_SCHEMA filter push down is inefficient
(feasibility not yet clear)
DRILL-8061 Impersonation support for Phoenix plugin
On 2021/12/08 17:40, James Turton wrote:
Dear dev community
Please reply if you *object* to us pushing out the freeze date by one
this change...
James Turton
Drill Committer
On 2022/01/09 23:55, sebb wrote:
Your DOAP file is no longer at the location specified in the projects.xml file.
Please update the file with the new location.
-- Forwarded message -
From:
Date: Sun, 9 Jan 2022 at 21:54
Subject: svn commit
Hello dev community
Discussions about reorganising the Drill source code to better position
the project to support plug-ins for the "long tail" of weird and
wonderful systems and data formats have been coming up here and there
for a few months, e.g. in
Thanks to everyone who shared the thoughtful observations about security
architecture. This email is just to add some specific feedback on the
credential provider proposal below.
Only the in-memory PlainCredentialsProvider wraps a Map of credentials.
The other implementations only ever
on Kerberos.
On 14 January 2022 11:51:09 GMT+02:00, James Turton wrote:
>Thanks to everyone who shared the thoughtful observations about security
>architecture. This email is just to add some specific feedback on the
>credential provider proposal below.
>
>Only the in-memory PlainCred
I believe I've just updated the mentioned file.
On 2022/01/09 23:55, sebb wrote:
Your DOAP file is no longer at the location specified in the projects.xml file.
Please update the file with the new location.
-- Forwarded message -
From:
Date: Sun, 9 Jan 2022 at 21:54
Subject:
istration events for different packages are recorded in a
central registry as I mentioned. That registry is recorded in Github as
well which makes it easy to propagate changes.
On Thu, Jan 13, 2022 at 8:45 PM James Turton wrote:
Hello dev community
Discussions about reorganising the Drill
Hi all
I'd like to propose the fourth release candidate (RC3) of Apache Drill,
version 1.20.0 which differs from the previous RC in the following.
1. DRILL-8130: Upgrade Hadoop 2 to 2.10.1 because of CVE-2020-9492 (#2458).
2. DRILL-8131: Infinite planning when JDBC or Phoenix plugin is
-1 unfortunately! A regression affecting Parquet INT96 timestamps has
just been reported.
https://issues.apache.org/jira/browse/DRILL-8134
On 2022/02/13 10:30, James Turton wrote:
Hi all
I'd like to propose the fourth release candidate (RC3) of Apache
Drill, version 1.20.0 which differs
I'm fine with the Kafka plugin fix (8122) if people want it in RC4, but
not with the Jackson-BOM. Jackson is a pervasive library and, for all I
know about what the implications are for the effective library versions,
this change could produce runtime regressions not revealed by our unit
is
planned at this time.
On 2022/02/10 10:55, James Turton wrote:
This follow up is just a formality to correct the paper trail which
incorrectly cites the parent of the two commits that it should cite.
The release candidates are based on commits
7ceb7e23942d0e7806dfe334b33d63bb7634c2f9 (Hadoop 3
Forwarded Message
Subject:Cloud Recording - Apache Drill Community Meetup is now available
Date: Fri, 04 Mar 2022 17:24:33 + (UTC)
From: Zoom
To: ja...@datadistillr.com
Zoom Logo <https://zoom.us/?zcid=1640>
Hi James Turton,
Your cloud rec
+1 for 120 days.
On 2022/03/05 14:09, luoc wrote:
Hi Charles,
I prefer to the "timeout" bot, that is a good step. However, some PR may be
blocked by another PR, so I recommended that we would up the timeout to 120 days or 150
days.
Thanks.
On Mar 4, 2022, at 22:57, Charles Givre wrote:
Hi all
Does anyone have any objections to
https://github.com/apache/drill/pull/2490? Any reasons to do a 1.21.0
before a 2.0.0?
Regards
James
or any
urgent fixes.
On 2022/03/17 11:56, Vitalii Diravka wrote:
Does that mean we can merge the non backward compatible changes then, right?
Kind regards
Vitalii
On Mon, Mar 14, 2022 at 10:47 AM James Turton wrote:
Hi all
Does anyone have any objections to
https://github.com/apache/drill/pul
Hi dev community!
Many of you need no introduction to the test framework developed by MapR
https://github.com/mapr/drill-test-framework
. For those who don't know, the test framework contains around 10k tests
often exercising scenarios not covered by Drill's unit tests. Just weeks
ago it
testing of
Drill. It would be great to see it continue to meet that need.
(... I was CTO at MapR when it was acquired by HPE but I don't have any
special position in the Drill community ...)
On Thu, Mar 17, 2022 at 2:03 AM James Turton wrote:
Hi dev community!
Many of you need no introduction
on set of the test
framework here?
Again, thanks to Charles's company and HPE team for supporting Apache Drill.
Thanks.
2022年3月18日 下午12:56，Paul Rogers 写道：
Abhishek used to have that thing running like a charm. Great to see it
getting attention again.
+1
- Paul
On Thu, Mar 17, 2022 at 2:03 AM
I too would like to express my sympathy and solidarity.
On 2022/02/24 11:43, Z0ltrix wrote:
oh my goodness i hope this will end soon.
Stay safe!
--- Original Message ---
luoc schrieb am Donnerstag, 24. Februar 2022 um 10:24:
Vitalii and Vova are my Ukrainian friends, hopefully they
The vote passes. Thanks to everyone who has tested the six(!) release
candidates over last twenty(!) days and given their comments and votes.
Final tally:
3x +1 (binding): Cong Luo, Charles, James
2x +1 (non-binding): Jinfeng Ni, Christian
No 0s or -1s.
I'll start process for pushing the
, just because
I didn't find any really natural way to include it in our release
process. It was certainly doable, but it's a little clunky. Or maybe
there are Maven plugin secrets that I don't know... something we can
discuss before the next one.
On 2022/02/25 09:41, James Turton wrote
Hi all
I'd like to propose the fifth release candidate (RC4) of Apache Drill,
version 1.20.0 which differs from the previous RC in the following.
DRILL-8139: Parquet CodecFactory thread safety bug (#2463)
DRILL-8134: Cannot query Parquet INT96 columns as timestamps (#2460)
DRILL-8122: Change
Hi
Drill has supported impersonation, which I'll use here to mean any
mechanism by which Drill accesses an external system as the end user
rather than its own OS user, to certain types of storage for a long
time. HDFS and Hive are the oldest examples, Phoenix is the most recent.
The myriad
Hi all
I'd like to propose the sixth release candidate (RC5) of Apache Drill,
version 1.20.0 which differs from the previous RC in the following.
DRILL-8144: Cannot launch Drill 1.20 RC 4 on Windows (#2470)
DRILL-8143: Error querying json with $date field (#2469)
DRILL-8142: SAS Reader
As a matter of interest, if you test directly against Drill with the
following timestamp literal expressions, what happens?
SELECT *
FROM dfs.foo.bar
WHERE `startTime` >= timestamp '2022-02-14 00:00:00.00'
AND `startTime` < timestamp '2022-02-21 00:00:00.00'
ORDER BY `startTime` DESC
Errata: an improvement of the working definition of impersonation inline
below.
On 2022/02/22 08:27, James Turton wrote:
Drill has supported impersonation, which I'll use here to mean any
mechanism by which Drill accesses an external system as the end user
rather than some system-wide
Welcome Tengfei!
On 2022/03/03 14:52, Charles Givre wrote:
The Project Management Committee (PMC) for Apache Drill
has invited Tengfei Wang 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
The next meetup comes around tomorrow. I have one topic for discussion:
"Who wants a 1.21 when there is a 2.0 that is certainly reachable, even
if it is minimal one that has a major theme of cleaning out obsolete stuff?"
It's also a deeply disturbing time in world history right now, with
Tengfei has added offered to share the architecture of their realtime
data warehouse built on Drill and I've learned there is also a chance
that Vitalii and Anton will be able to connect. See you this time tomorrow!
On 2022/03/03 10:07, James Turton wrote:
The next meetup comes around
Note from the release manager.
As we announce Drill 1.20 to the world I'd like to point to the fact
that this release, and all of Drill, is full of valuable contributions
from talented Ukrainian developers whom many of us know personally. On
behalf of the Drill community may I express
It's just the CI, not a problem with Drill 1.20 on ARM (which I've
tested). So no need to fret when you see the red X in Travis, I'll take
care of it soon.
James
Givre wrote:
I would also like to express my sympathy and support for Arina, Vova,
Vitalii, Igor, Anton and the people of Ukraine.
-- C
On Feb 24, 2022, at 5:07 AM, James Turton wrote:
I too would like to express my sympathy and solidarity.
On 2022/02/24 11:43, Z0ltrix wrote:
oh my goodness i
, James Turton wrote:
Hi all
I'd like to propose the fifth release candidate (RC4) of Apache Drill,
version 1.20.0 which differs from the previous RC in the following.
DRILL-8139: Parquet CodecFactory thread safety bug (#2463)
DRILL-8134: Cannot query Parquet INT96 columns as timestamps (#2460
Hi Jingchuan Hu!
It's a long way off and I will leave this planning to the "elders" like
Cong Luo and Charles but I do want to say that I will certainly offer
you my support if you do manage the next release, since I have some
experience now.
Regards
James
On 2022/03/20 17:15, Jingchuan Hu
Hey all
Just a reminder that the first Friday of April lands tomorrow, bang on 1
April! I hope you can join us for another meetup. So far in the agenda
we have
- Introduction to the Drill test framework by Anton
let me know if you'd like to add anything else.
Regards
James
Regards,
Abhishek
On Fri, Mar 18, 2022 at 6:49 AM James Turton wrote:
Hi Cong Luo
Yes, this is the same project as DRILL-8120. Anton Gozhiy is actively
working on the test framework, I'm not sure if there are others too. I
agree that an introduction would be helpful. Maybe in the next
communit
Hello Dev community
Not a moment too soon, we've finally dispatched the last issues holding
back 1.20! Here's a big thank you from the release manager to everyone
who helped to push us forward to this point. I'm sure I'm not the only
one receiving the "When it's coming??" questions. As an
est,
--C
On Jan 29, 2022, at 7:36 AM, James Turton wrote:
Hello Dev community
Not a moment too soon, we've finally dispatched the last issues holding back 1.20!
Here's a big thank you from the release manager to everyone who helped to push us forward
to this point. I'm sure I'm not the only
PR #2449 was merged and there are now zero Dependabot alerts against
master.
+1 for freezing from me.
On 2022/02/02 16:36, Charles Givre wrote:
Assuming we pass dependabot, big +1 from me!! Great work everyone!
--C
On Feb 2, 2022, at 9:35 AM, James Turton wrote:
Please vote again
, Vitalii Diravka schrieb:
+1
Kind regards
Vitalii
On Wed, Feb 2, 2022 at 6:04 PM Vova Vysotskyi
wrote:
> +1
>
> Kind regards,
> Volodymyr Vysotskyi
>
> On 2022/02/02 15:59:55 James Turton wrote:
> > PR #2449 was merged and there
Hi everybody!
The next meetup is in just over 7 hours time. Here are some updates
from me.
1. I've learned a bit more Zoom and configured this meeting series to
automatically record to the cloud. I believe that should happen
whether I personally join the meeting or not. I will
P.S. if you know a reason that we should _not_ add
apache-drill-1.20.0-hadoop2.tar.gz.* artifacts to our release from the
new hadoop-2 profile please call a vote.
On 2022/02/05 11:11, James Turton wrote:
Hi all
Note from the release manager.
The normal RC announcement follows below
Thank you to everyone who joined! The link to the recording is below
and I understand that a textual summary will follow in due course.
Topic: Apache Drill Community Meetup
Date: Feb 4, 2022 07:56 AM Pacific Time (US and Canada)
Meeting Recording:
/rec/share/tFaDw99UfwK_ZxSg60AVM_PHCPdyIZci8MaRkVYQyAHOLiUmATJ4n4uxrkbW0Cm_.mNUcipDuNEcz_u3K
On 2022/02/05 09:02, James Turton wrote:
Thank you to everyone who joined! The link to the recording is below
and I understand that a textual summary will follow in due course.
Topic: Apache Drill
Hi all
Note from the release manager.
The normal RC announcement follows below but please take note that while
you should test and try this Hadoop 3-based RC 0 of Drill 1.20.0, there
is likely to be another RC which ships both Hadoop 2 and Hadoop 3 builds
as soon as I have got some
Not too *soon for you to send
On 2022/01/26 20:30, James Turton wrote:
Hi all
Sorry these notes were stuck with me for a while! The next meetup is
next Friday, not too for you to send anything you would like
incorporated.
1 - 100 of 378 matches
Mail list logo
