paul-rogers commented on pull request #2364:
URL: https://github.com/apache/drill/pull/2364#issuecomment-1031015937
@vdiravka, which test do I run to see the failure? I tried that one test
mentioned above, but it worked for me.
Actually, I should probably create a separate unit test
Hi All,
Drill, like all open source projects, exists to serve those that use it. To
that end, the best contributions come when some company needs a feature
badly enough that it is worth the effort to develop and contribute a
solution. That's pretty standard, as along as the contribution is
Hi Luoc,
Thanks for your concern. Apache projects are often backed unofficially by a
company. Drill was, for years, backed my MapR as evident by all the MapR
unique code that is still in the Drill codebase. However, since MapR's
acquisition, I think it is safe to say that Drill really has
Before we discuss the next release, I would like to explain that Apache project
should not be directly linked to a commercial company, otherwise this will
affect the motivation of the community to contribute.
Thanks.
> On Feb 6, 2022, at 21:29, Charles Givre wrote:
>
> Hello all,
>
Hello all,
Firstly, I wanted to thank everyone for all the work that has gone into Drill
1.20 as well as the ongoing discussion around Drill 2.0. I wanted to start a
discussion around topic for Drill 1.21 and that is INFO_SCHEMA improvements.
As my company wades further and further into
cgivre commented on pull request #2419:
URL: https://github.com/apache/drill/pull/2419#issuecomment-1030830633
>
@paul-rogers I re-ran the tests and everything passed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
+1 for the release.
I did following test manually without error:
1. starting Drill in Distributed mode.
2. Checked basically function in Web UI
3. Did sample query by Web UI and sqlline.
On Sat, Feb 5, 2022 at 5:11 PM James Turton wrote:
> Hi all
>
> Note from the release manager.
>
