RE: Allow Java 1.8
I agree this would be very useful. Currently our Hadoop cluster and Spark are running on Java 1.8 and Drill is the only component left on 1.7, so ideally we could remove the reliance the older version of Java. Previously I have done some testing on Drill 1.0 on Java 1.8 and didn't hit any issues myself. -Original Message- From: Jacques Nadeau [mailto:jacq...@apache.org] Sent: 09 July 2015 03:36 To: dev@drill.apache.org Subject: Re: Allow Java 1.8 Agreed. 7 and 8. On Wed, Jul 8, 2015 at 7:35 PM, David Tucker wrote: > I assume that “move to Java 1.8” implies “support Java 1.8 as well as > Java 1.7”, not “support Java 1.8 and exclude Java 1.7”. > > Regards, > David > > > On Jul 8, 2015, at 7:17 PM, Jacques Nadeau wrote: > > > > I don't think there is a good reason. I think the main issue was > > (at > some > > point) the tests weren't working with Java 8. Do you want to try to > > run the complete test suite and see if we have outstanding issues to > > move to Java 8? > > > > Aditya might remember more... > > > > On Wed, Jul 8, 2015 at 6:41 PM, andrew wrote: > > > >> Hi, > >> > >> Is there a reason we have an enforcement on Java versions as > >> defined in the top-level pom.xml: [1.7, 1.8)? The code compiles for > >> me just fine w/1.8. Is this merely historical residue that can be > >> relaxed or is there some deeper reason > why > >> Drill won’t/can’t work with 1.8? > >> > >> Thanks, > >> Andrew > > This e-mail (including any attachments) is private and confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are strictly prohibited from taking action on the basis of information in this e-mail and must contact the sender immediately, delete this e-mail (and all attachments) and destroy any hard copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to retain, monitor and intercept e-mail communications through its networks (subject to and in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
RE: Timing for 1.2 release, ideas around things to include
I'm not sure what the appetite is for pushing this into 1.2 vs the planned 1.3, but Drill UI Authentication would be really great for companies/users that run multi-tenant Hadoop clusters with Drill. At the moment any user can change storage plugins and cancel running queries, even if they did not submit them. This is a bit of a blocker for Drill on multi-tenant production clusters for now. JIRA link: https://issues.apache.org/jira/browse/DRILL-3201 -Original Message- From: Jacques Nadeau [mailto:jacq...@apache.org] Sent: 08 July 2015 17:19 To: dev@drill.apache.org Subject: Timing for 1.2 release, ideas around things to include Hey Guys, What do you think about planning the 1.2 feature cutoff around Aug 21st and target a release vote a week or so after that? What are different features people want to get into 1.2? Here are couple of things that I'd like to help facilitate contribution and/or inclusion: - Mongo improvements (including extended type fixes 2879 , test cases 1666, etc) - httpd log parser format plugin (3423) - rpc enhancements (local 2941 and off-thread 3242) - First merge of Magnus' JDBC connector (3180) - New allocator (1942) Other key goals? What do people think about the proposed timing? This e-mail (including any attachments) is private and confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are strictly prohibited from taking action on the basis of information in this e-mail and must contact the sender immediately, delete this e-mail (and all attachments) and destroy any hard copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to retain, monitor and intercept e-mail communications through its networks (subject to and in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
Custom SerDes in Drill
Hi, Is it possible to use custom SerDe in Drill? From what I can see it is not, but there are some proprietary data types that I am interested in querying that need a SerDe. I am guessing a Drill query over a Hive table (set up to use a custom SerDe) will not work? Thanks, Mike This e-mail (including any attachments) is private and confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are strictly prohibited from taking action on the basis of information in this e-mail and must contact the sender immediately, delete this e-mail (and all attachments) and destroy any hard copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to retain, monitor and intercept e-mail communications through its networks (subject to and in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
RE: Custom SerDes in Drill
Interesting, I'll give it a go and reply to the mail list to see how I get on. Thanks, Mike -Original Message- From: Jacques Nadeau [mailto:jacq...@dremio.com] Sent: 01 October 2015 14:35 To: dev@drill.apache.org Subject: Re: Custom SerDes in Drill As long as the custom serde dependencies are also on the Drill classpath, this should work fine. On Oct 1, 2015 5:59 AM, wrote: > Hi, > > Is it possible to use custom SerDe in Drill? From what I can see it is > not, but there are some proprietary data types that I am interested in > querying that need a SerDe. I am guessing a Drill query over a Hive > table (set up to use a custom SerDe) will not work? > > Thanks, > Mike > > > This e-mail (including any attachments) is private and confidential, > may contain proprietary or privileged information and is intended for > the named > recipient(s) only. Unintended recipients are strictly prohibited from > taking action on the basis of information in this e-mail and must > contact the sender immediately, delete this e-mail (and all > attachments) and destroy any hard copies. Nomura will not accept > responsibility or liability for the accuracy or completeness of, or > the presence of any virus or disabling code in, this e-mail. If > verification is sought please request a hard copy. Any reference to > the terms of executed transactions should be treated as preliminary > only and subject to formal written confirmation by Nomura. Nomura > reserves the right to retain, monitor and intercept e-mail > communications through its networks (subject to and in accordance with > applicable laws). No confidentiality or privilege is waived or lost by > Nomura by any mistransmission of this e-mail. Any reference to > "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. > Please read our Electronic Communications Legal Notice which forms part of > this e-mail: > http://www.Nomura.com/email_disclaimer.htm > > This e-mail (including any attachments) is private and confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are strictly prohibited from taking action on the basis of information in this e-mail and must contact the sender immediately, delete this e-mail (and all attachments) and destroy any hard copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to retain, monitor and intercept e-mail communications through its networks (subject to and in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
