Laurent Goujon wrote:
>
> So the vote for RC0 has been cancelled because of DRILL-7945. I will publish
> a new RC with the following fixes:
> - https://issues.apache.org/jira/browse/DRILL-7937
> - https://issues.apache.org/jira/browse/DRILL-7940
> - https://issues.apache.org
On behalf of the Apache Drill community, I am happy to announce the release
of Apache Drill 1.19.0.
Drill is an Apache open-source SQL query engine for Big Data exploration.
Drill is designed from the ground up to support high-performance analysis
on the semi-structured and rapidly evolving data c
Master is now unfrozen. Thank you all for your understanding.
Laurent
On Tue, Jun 1, 2021 at 2:42 PM Laurent Goujon wrote:
> Change has been merged and is part of the release candidate.
>
> On Tue, Jun 1, 2021 at 8:38 AM luoc wrote:
>
>>
>> DRILL-7928, please merge it,
, etc.).
> > * I have access to that Twitter account (but not only I), please send an
> announcement about the release in a private message to @ApacheDrill and
> I’ll post it.
> > * Done: https://reporter.apache.org/addrelease.html?drill
> >
> > Kind regards,
> > Volodymy
> > > >>
> > > > On Wed, Jun 9, 2021 at 10:25 AM wrote:>>
> > > >>
> > > > > I have some issues, will deploy after>>
> > > > > https://issues.apache.org/jira/browse/INFRA-21981 is fixed.>>
> > > &
[
https://issues.apache.org/jira/browse/DRILL-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7854.
---
Resolution: Fixed
Should have been resolved when Guava version was updated to 30.0
> W
[
https://issues.apache.org/jira/browse/DRILL-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7914.
---
Resolution: Fixed
> Apache Drill 1.19.0 Release Activit
[
https://issues.apache.org/jira/browse/DRILL-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7921.
---
Resolution: Fixed
> Support the Linux ARM64 based sys
Laurent Goujon wrote:
> Hi all,
>
> The vote passes. Thanks to everyone who has tested the release
>
> candidate and given their comments and votes. Final tally:
>
> 3x +1 (binding): Laurent, Ted, Vova
>
> No 0s or -1s.
>
> I'll start the process for pus
Hi all,
The vote passes. Thanks to everyone who has tested the release candidate
and given their comments and votes. Final tally:
3x +1 (binding): Laurent, Ted, Vova
No 0s or -1s.
I'll start the process for pushing the release artifacts and send an
announcement once propagated.
Kind regards,
Hi all,
I'd like to propose the first release candidate (RC1) of Apache Drill,
version 1.19.0.
The release candidate covers a total of 109 resolved JIRAs [1]. Thanks
to everyone who contributed to this release.
The tarball artifacts are hosted at [2] and the maven artifacts are
hosted at [3].
This
[
https://issues.apache.org/jira/browse/DRILL-7946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7946.
---
Resolution: Fixed
> Bump HttpClient from 4.5.12 to 4.5.13 for CVE-2020-13
hamcrest version change: the junit change has actually
new comment, and all those patches do not have visible impact on the
distribution so I think they can also wait to be merged just after the
release approval (and I'll happy help get them merged).
Laurent
On Mon, May 31, 2021 at 9:17 PM
[
https://issues.apache.org/jira/browse/DRILL-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7945.
---
Assignee: Laurent Goujon (was: Vitalii Diravka)
Resolution: Fixed
> Unable to pa
's release process
> is not friendly, and we will put these discussion after the release. Now
> our focus is on preparing for RC1. BTW, You're doing great.
>
> > 2021年6月4日 下午1:20，Laurent Goujon 写道：
> >
> > You actually went ahead and merged those patches without
bhakar Bhosaale
wrote:
> Vote +1
>
> On Wed, Jun 2, 2021 at 3:12 AM Laurent Goujon wrote:
>
> > Hi all,
> >
> > I'd like to propose the first release candidate (RC0) of Apache Drill,
> > version 1.19.0.
> > The release candidate covers a total
to get a review for the DRILL-7945 patch fixing the
Guava regression, and hopefully I should be able to do another release
candidate tomorrow.
Laurent
On Thu, Jun 3, 2021 at 5:46 PM luoc wrote:
>
> The DRILL-7945 blocked the release. So, I'm ready to merge the DRILL-7937
> and DRILL
issue: DRILL-7945 <
> https://issues.apache.org/jira/browse/DRILL-7945>
>
> It is definitely a regression and it might break some important Drill
> functionality so I'm considering it as a blocker for the release.
>
> Kind regards,
> Volodymyr Vysotskyi
>
>
>
Hey guys,
Can we please stop changing the goal post again and again? The fact that
some of those pull requests are ready to merge should not be the sole
consideration when to do a next release candidate.
I've been asking several times on this mailing list about what we want to
include or not, and
Change has been merged and is part of the release candidate.
On Tue, Jun 1, 2021 at 8:38 AM luoc wrote:
>
> DRILL-7928, please merge it, thanks
>
> > 2021年6月1日 下午11:29，Laurent Goujon 写道：
> >
> > Technically, yes, it has started. Which PR? this wasn't send to t
Hi all,
I'd like to propose the first release candidate (RC0) of Apache Drill,
version 1.19.0.
The release candidate covers a total of 105 resolved JIRAs [1]. Thanks
to everyone who contributed to this release.
The tarball artifacts are hosted at [2] and the maven artifacts are
hosted at [3].
This
[
https://issues.apache.org/jira/browse/DRILL-7795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7795.
---
Fix Version/s: 1.19.0
Resolution: Fixed
> Add option to native Drill Client to
[
https://issues.apache.org/jira/browse/DRILL-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-6547.
---
Fix Version/s: 1.19.0
Resolution: Fixed
> IllegalStateException: Tried to rem
Technically, yes, it has started. Which PR? this wasn't send to the mailing
list
On Mon, May 31, 2021 at 10:51 PM luoc wrote:
>
> Has it started, Laurent? I want to merge the last PR now.
>
> > 2021年6月1日 下午12:25，Laurent Goujon 写道：
> >
> > Hi,
> >
>
Hi,
In preparation for the 1.19.0 release, master tree is currently frozen
until the release process is completed. For committers, until the release
is over and Drill version is changed to 1.20.0-SNAPSHOT, please do not push
any changes into Drill master.
Cheers,
Laurent
It looks like the parquet patch for DRILL-7934. I'll send an email to
announce the start of the release process.
On Sun, May 30, 2021 at 10:35 PM Laurent Goujon wrote:
> Ok, let's do that!
>
> On Sat, May 29, 2021, 19:09 Charles Givre wrote:
>
>> Hi Laurent,
>&g
.
> >> I believe there's only one Parquet change left for DRILL-7934:
> >> <https://issues.apache.org/jira/browse/DRILL-7934> Charles, is this
> correct?
> >>
> >> Laurent
> >>
> >>> On Thu, May 27, 2021 at 10:48 AM Lauren
is this correct?
Laurent
On Thu, May 27, 2021 at 10:48 AM Laurent Goujon wrote:
> Some fixes/improvements were made to the codebase since the last release,
> and sadly an official release is needed to pick up those changes. Ray asked
> the community more than a month ago. More recentl
[
https://issues.apache.org/jira/browse/DRILL-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7936.
---
Fix Version/s: 1.19.0
Reviewer: Charles Givre
Resolution: Fixed
> Rem
[
https://issues.apache.org/jira/browse/DRILL-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7162.
---
Fix Version/s: 1.19.0
Resolution: Fixed
Apache Drill has been updated to the latest
[
https://issues.apache.org/jira/browse/DRILL-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7135.
---
Fix Version/s: 1.19.0
Reviewer: Paul Rogers
Assignee: Laurent Goujon
[
https://issues.apache.org/jira/browse/DRILL-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7932.
---
Fix Version/s: 1.19.0
Reviewer: Cong Luo
Resolution: Fixed
Update done as
e been averaging 2 a year and
> I’d hate for users to have to wait 6 months for these fixes.
>
> — C
>
>
>
> > On May 27, 2021, at 12:19 PM, Laurent Goujon wrote:
> >
> > Since I'm also a reviewer and that I see that the past comments I've been
> &g
Laurent Goujon created DRILL-7936:
-
Summary: Remove Guava Files#createTempDir usage
Key: DRILL-7936
URL: https://issues.apache.org/jira/browse/DRILL-7936
Project: Apache Drill
Issue Type
ooks like we should include as well.
> Best,
> -- C
>
> > On May 27, 2021, at 11:01 AM, Laurent Goujon wrote:
> >
> > Sadly, I haven't heard from people regarding the patches. At the same
> time,
> > I think we held the window open for merging the changes f
or Drill
1.19.0
Here are the pull request links:
* https://github.com/apache/drill/pull/2202
* https://github.com/apache/drill/pull/2236
Laurent
On Wed, May 26, 2021 at 11:59 AM Laurent Goujon wrote:
> After several retries, the Guava checks successfully passed:
> https://github.com/a
After several retries, the Guava checks successfully passed:
https://github.com/apache/drill/pull/2202
Charles, can we proceed on merging your change?
Laurent
On Tue, May 25, 2021 at 10:24 PM Laurent Goujon wrote:
> Just an update. There's a patch for updating both Jetty and Hadoop
till want to wait on this patch, or if we should move it to
the next release.
Let me know what people think,
On Tue, May 25, 2021 at 8:24 AM Laurent Goujon wrote:
> Anything I can help with?
>
> On Tue, May 25, 2021 at 7:02 AM Charles Givre wrote:
>
>> HI Laurent,
>> My
e is almost
> done as well.
> -- C
>
>
>
>
> > On May 24, 2021, at 5:29 PM, Laurent Goujon wrote:
> >
> > Ok, I was hoping that some of the PRs could be merged, but if we are in
> > agreement, let's start the work :)
> >
> > On Sun, May 23
Laurent Goujon created DRILL-7932:
-
Summary: Update Hadoop version to 3.2.2.
Key: DRILL-7932
URL: https://issues.apache.org/jira/browse/DRILL-7932
Project: Apache Drill
Issue Type
urent Goujon wrote:
> I might be able to help on the JUnit and CVE patches too too
>
> On Mon, May 24, 2021 at 2:29 PM Laurent Goujon wrote:
>
>> Ok, I was hoping that some of the PRs could be merged, but if we are in
>> agreement, let's start the work :)
>>
> with a government ID, this would be easy.
>
> Do you know a committer personally who could vouch for you? Would you be
> interested in having a video call where you can present some ID?
>
> On Mon, May 24, 2021 at 3:24 PM Laurent Goujon wrote:
>
> > Hi,
> >
> &
Hi,
I opened a pull request to add my public GPG keys to the KEYS file at the
root of the project:
https://github.com/apache/drill/pull/2234
Sadly this key is not part of the Web Of Trust, and I would need someone
part of it to validate my key. And also a PMC member to add it to the Drill
release
I might be able to help on the JUnit and CVE patches too too
On Mon, May 24, 2021 at 2:29 PM Laurent Goujon wrote:
> Ok, I was hoping that some of the PRs could be merged, but if we are in
> agreement, let's start the work :)
>
> On Sun, May 23, 2021 at 6:52 PM luoc wrote
oesn't matter whether it is included in this release or in the next
> one.
> >>>
> >>> So we can plan to start the release process
> >>>
> >>>
> >>> Kind regards
> >>> Vitalii
> >>>
> >&g
urent,
> > We have a few PRs pending which I'd like to see in the next version
> >
> > which
> >
> > are:
> > 1. The update(s) and bug fixes to the Mongo plugin.
> > 2. There is an extended PR for bug fixes which clean up a lot of
> >
>
d by LGTM
> > 3. There are a few other library updates which are pending.
> > 4. We have some work which changes the access model around storage
> > plugins which would be good for this release
> > 5. The PCAP/PCAP-NG consolidation is awaiting review.
> >
> >
Laurent Goujon created DRILL-7914:
-
Summary: Apache Drill 1.19.0 Release Activities
Key: DRILL-7914
URL: https://issues.apache.org/jira/browse/DRILL-7914
Project: Apache Drill
Issue Type
Hello everyone,
It has been more than 6 months since the last release, and I believe this
would be a good time to discuss the next one.
As mentioned in a previous email thread, I am volunteering to be the
release manager, and I'm looking forward working with the whole community
to make another g
nt of a release is the community involvement,
> not the technical aspects of packaging.
> >
> > On 2021/04/12 21:45:22, Laurent Goujon wrote:
> >> Hi Ted,
> >>
> >> I was led to believe that only a PMC member could perform some of the
> >> release t
de of the regular unit test framework that require a
> special setup.
>
> I have to ask as I am curious but what/why is Dremio still interested in
> Drill? All the code is OSS, and you could just use what's already in
> github without it being "released".
> Bes
Hi Ted,
I was led to believe that only a PMC member could perform some of the
release tasks, but if not the case, I'm happy to volunteer for the next
one. Since it would be my first release, is there any document detailing
the list of tasks to be completed?
On Mon, Apr 12, 2021 at 1:55 PM Ted Dun
[
https://issues.apache.org/jira/browse/DRILL-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Goujon resolved DRILL-7726.
---
Fix Version/s: 1.18.0
Resolution: Fixed
> Boost requirement is incorr
Laurent Goujon created DRILL-7727:
-
Summary: Address Protobuf C++ warnings
Key: DRILL-7727
URL: https://issues.apache.org/jira/browse/DRILL-7727
Project: Apache Drill
Issue Type: Test
Laurent Goujon created DRILL-7726:
-
Summary: Boost requirement is incorrect
Key: DRILL-7726
URL: https://issues.apache.org/jira/browse/DRILL-7726
Project: Apache Drill
Issue Type: Bug
If encryption is not enabled, any MITM can intercept and inject traffic in
the session (meaning it could also do requests on behalf of the users
without the user noticing), even with Kerberos.
On Wed, Nov 1, 2017 at 2:13 PM, Sorabh Hamirwasia
wrote:
> Parth,
>
> Your understanding is correct.
>
I have a parallel scenario:
- Scenario 1:
1) A handshake from a (1.12) client expecting authentication and encryption
is intercepted by a rogue server. The rogue server then responds first with
AUTH_REQUIRED, but authenticationMechanisms doesn't provide gssapi/kerberos
as a sasl mechanism. The cli
Alternatively, you could just check that the field sasl_support is set and
not check the value alltogether. I'm not convinced you need to do some
extra logic around UNKNOWN_SASL_SERVER which would just keep people
confused (although it doesn't seem something you need to apply to 1.11 or
higher)
ility between Drill 1.11 client and Drill 1.10
> server, I think the fix should be made which is mentioned in first email of
> this thread.
>
> Thanks,
> Sorabh
>
>
> From: Laurent Goujon
> Sent: Tuesday, October 31, 2017 9:38:13 AM
> To: dev
> Cc:
ache/drill/blob/1.11.0/exec/java-
> exec/src/main/java/org/apache/drill/exec/rpc/user/UserServer.java#L254
> [2]: https://github.com/apache/drill/blob/1.11.0/exec/java-
> exec/src/main/java/org/apache/drill/exec/rpc/user/UserRpcConfig.java#L89
>
>
> Thanks,
> Sorabh
&g
Regarding DRILL-5582, I see that fix as a breakage of the work to maintain
compatibility for an newer client to connect to a older version of the
server. Or put it differently: current (master) client does not connect
anymore to a server not supporting SASL (<=1.9). Note that the client could
detec
AFAIK Tableau uses Drill ODBC driver, not JDBC (although Tableau hinted at
some JDBC support at some point: https://community.tableau.com/ideas/4633).
it's technically feasible BUT the Drill protocol is very low level so the
adapter would have to use the Drill RPC protocol and represent its own da
Laurent Goujon created DRILL-5668:
-
Summary: C++ connector crash when query error message is too long
Key: DRILL-5668
URL: https://issues.apache.org/jira/browse/DRILL-5668
Project: Apache Drill
Laurent Goujon created DRILL-5369:
-
Summary: Missing initialization for ServerMetaContext
Key: DRILL-5369
URL: https://issues.apache.org/jira/browse/DRILL-5369
Project: Apache Drill
Issue
Laurent Goujon created DRILL-5368:
-
Summary: Memory leak in C++ server metadata handler
Key: DRILL-5368
URL: https://issues.apache.org/jira/browse/DRILL-5368
Project: Apache Drill
Issue Type
Laurent Goujon created DRILL-5311:
-
Summary: C++ connector connect doesn't wait for handshake to
complete
Key: DRILL-5311
URL: https://issues.apache.org/jira/browse/DRILL-5311
Project: Apache
s.
Thanks,
Jinfeng
On Wed, Mar 1, 2017 at 10:31 AM, Laurent Goujon wrote:
> The following jiras have all been reviewed and are ready to commit:
> * DRILL-4994: Add back JDBC prepared statement for older servers
> * DRILL-4730: Update JDBC DatabaseMetaData implementation to use new
> M
d.
>
>
>
> On Mon, Feb 27, 2017 at 2:42 PM, Laurent Goujon
> wrote:
> > Thanks for the heads up: I'll try to ping directly some committers to
> > review my changes.
> >
> > For information, what's the official cutoff date?
> >
> > Laure
ertise) are on travel currently, it probably is not
> likely that one of them can review your PRs before the cutoff for
> 1.10.
>
> Thanks,
> Jinfeng
>
>
>
>
> On Mon, Feb 27, 2017 at 9:48 AM, Laurent Goujon
> wrote:
> > Hi Jinfeng,
> >
> > Thanks for
Hi Jinfeng,
Thanks for volunteering:
Please consider the following JIRAs (PRs already open):
* DRILL-4994: Add back JDBC prepared statement for older servers
* DRILL-4730: Update JDBC DatabaseMetaData implementation to use new
Metadata APIs
* DRILL-5301: Server metadata API
* DRILL-5167: Send esc
Laurent Goujon created DRILL-5301:
-
Summary: Add server metadata API
Key: DRILL-5301
URL: https://issues.apache.org/jira/browse/DRILL-5301
Project: Apache Drill
Issue Type: Improvement
Hi,
I have a couple of open patches for the C++ connector:
- DRILL-5167: Send escape character for metadata queries
https://github.com/apache/drill/pull/712
- DRILL-5219: Relax user properties validation in C++ client
https://github.com/apache/drill/pull/727
- DRILL-5220: Provide API to set appl
Laurent Goujon created DRILL-5221:
-
Summary: cancel message is delayed until queryid or data is
received
Key: DRILL-5221
URL: https://issues.apache.org/jira/browse/DRILL-5221
Project: Apache Drill
Laurent Goujon created DRILL-5220:
-
Summary: Add api to set application name in C++ connector
Key: DRILL-5220
URL: https://issues.apache.org/jira/browse/DRILL-5220
Project: Apache Drill
Laurent Goujon created DRILL-5219:
-
Summary: Remove DrillUserProperties filtering in C++ driver
Key: DRILL-5219
URL: https://issues.apache.org/jira/browse/DRILL-5219
Project: Apache Drill
Never tried myself, but that page might help:
https://cloud.google.com/hadoop/google-cloud-storage-connector. It explains
where to download the google connector and how to configure it.
After that, you should be able to configure the storage plugin to use gs://
url (vs s3://)
Laurent
On Tue, Jan
Laurent Goujon created DRILL-5167:
-
Summary: C++ connector does not set escape string for metadata
search pattern
Key: DRILL-5167
URL: https://issues.apache.org/jira/browse/DRILL-5167
Project: Apache
I don't think that all unit tests pass in Java8. I fixed a couple of test
cases but I'm pretty sure some JDBC tests still fail because of the new
default methods added to the JDBC interface which are not overriden in
Avatica and Drill: https://issues.apache.org/jira/browse/DRILL-4333
I don't have
I guess it's DRILL-4730 and not DRILL-4370
On Fri, Nov 4, 2016 at 6:23 PM, Sudheesh Katkam wrote:
> Out of the 17 requested tickets, we resolved 13 over the week, and 4 have
> been deferred (DRILL-4280, DRILL-4858, DRILL-4370, DRILL-4706). Thank you
> everyone!
>
> I get will get the RC0 out on
Laurent Goujon created DRILL-4994:
-
Summary: Prepared statement stopped working between 1.8.0 client
and < 1.7.0 server
Key: DRILL-4994
URL: https://issues.apache.org/jira/browse/DRILL-4994
Proj
ks for
> the
> > > server version as well, which make the compatibility break more
> visible.
> > >
> > > I am not sure about the plan of action in general about this
> > compatibility.
> > > However, I could work around the issue by advertising clients' SASL
ak more visible.
>
> I am not sure about the plan of action in general about this compatibility.
> However, I could work around the issue by advertising clients' SASL
> capability to the server. What do you think?
>
> Thank you,
> Sudheesh
>
> [1] https://issues.apache.o
Just for clarity, DRILL-4280 is a breaking-protocol change, so is the plan
to defer this change to a later release, or to defer bringing back
compatibility between newer clients and older servers to a later release?
Laurent
On Tue, Nov 1, 2016 at 3:43 PM, Zelaine Fong wrote:
> Oops, mistake in
Which hangout link are we using today?
On Tue, Nov 1, 2016 at 9:51 AM, Sudheesh Katkam wrote:
> Zelaine, That list is from the other thread ("Time for a 1.9 Release?"),
> where there was no mention of PR#639.
>
> Charles, DRILL-3423 is already on the list.
>
> Thank you,
> Sudheesh
>
> On Tue, N
Hi,
I have several JIRAs regarding metadata I worked on recently and would like
to see resolved before 1.9:
- DRILL-1268: Add unit test to C++ native client
- DRILL-4853: Update C++ protobuf source files
- DRILL-4420: C++ API for metadata access and prepared statements
- DRILL-1996: Add cancel me
Laurent Goujon created DRILL-4969:
-
Summary: Have basic implementation for displaySize
Key: DRILL-4969
URL: https://issues.apache.org/jira/browse/DRILL-4969
Project: Apache Drill
Issue Type
Laurent Goujon created DRILL-4968:
-
Summary: Add column size information to ColumnMetadata
Key: DRILL-4968
URL: https://issues.apache.org/jira/browse/DRILL-4968
Project: Apache Drill
Issue
Laurent Goujon created DRILL-4945:
-
Summary: Missing subtype information in metadata returned by
prepared statement
Key: DRILL-4945
URL: https://issues.apache.org/jira/browse/DRILL-4945
Project
don't think it reasonably applies to the
> changes
> > > > proposed by Laurent. His changes "complete" the already introduced
> > > metadata
> > > > and prepare apis the server exposes. It provides an improved BI user
> > > > experience. It a
Laurent Goujon created DRILL-4930:
-
Summary: Metadata results are not sorted
Key: DRILL-4930
URL: https://issues.apache.org/jira/browse/DRILL-4930
Project: Apache Drill
Issue Type: Bug
Hi,
I'm currently working on improving metadata support for both the JDBC
driver and the C++ connector, more specifically the following JIRAs:
DRILL-4853: Update C++ protobuf source files
DRILL-4420: Server-side metadata and prepared-statement support for C++
connector
DRILL-4880: Support JDBC dr
Laurent Goujon created DRILL-4925:
-
Summary: Add types filter to getTables metadata API
Key: DRILL-4925
URL: https://issues.apache.org/jira/browse/DRILL-4925
Project: Apache Drill
Issue Type
That sounds like a good idea. The JDBC example has a
Class.forName("org.apache.drill.jdbc.Driver") statement to force driver
registration, but a ServiceLoader registration is pretty standard. Maybe
you should open a bug for it?
Laurent
On Tue, Sep 6, 2016 at 9:53 AM, Sudip Mukherjee
wrote:
> Hi
l take a look at this in the next few days.
>
> On a related note, do you or Venki have a proposal for the backend
> changes (i.e actual implementation of prepare)? It would be a good idea to
> start a discussion on that.
>
> Parth
>
> On Mon, Aug 22, 2016 at 3:24 PM, L
Hi,
I just started working on adding support for prepared statements and
metadata querying in the C++ Drill client. Hopefully, nobody else has
started working on this (The Drill jiras don't mention any activity on
this), but if it is not the case, let me know.
My working branch is
https://github.
I just opened DRILL-4853 jira and PR
https://github.com/apache/drill/pull/571 for the protobuf source files
update.
Laurent
On Thu, Aug 18, 2016 at 9:49 AM, Laurent Goujon wrote:
> Thanks Sékine,
>
> After fiddling around and with a little help from Venki (who told me about
> the C
Laurent Goujon created DRILL-4853:
-
Summary: Update C++ protobuf source files
Key: DRILL-4853
URL: https://issues.apache.org/jira/browse/DRILL-4853
Project: Apache Drill
Issue Type: Task
(Defaulted
> to proto2 syntax.)
> GeneralRPC.proto: warning: Import Coordination.proto but not used.
> [libprotobuf WARNING google/protobuf/compiler/parser.cc:547] No syntax
> specified for the proto file: User.proto. Please use 'syntax = "proto2";'
> or
Hi,
There's no instructions on how to generate the C++ protobuf files, and they
are currently out-of-sync with the definitions stored under protocol module.
Does someone know how these files are generated? I'd like to update them
and add some instructions at the same time.
Cheers,
Laurent
I also believe Hadoop have some optional classloader to isolate hadoop
internal classpath from application classpath, like that guy:
https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/util/ApplicationClassLoader.html
Laurent
On Wed, Apr 6, 2016 at 12:34 PM, Hanifi Gunes wrote:
> Shadin
1 - 100 of 115 matches
Mail list logo
