Re: Drill selects column with the same name of a different table

You are not receiving replies because you have not subscribed to the user@drill list. Please do that. I moderated your message through last time and this time, which is why there was a delay in the messages appearing on the list. On 2017-08-22 04:18, Hielke Hoeve

Re: Drill Summit/Conference Proposal

succeed at the above goals, thus I’m not certain what the right choice is, > but I wanted to bring up the point for discussion. > > > On June 14, 2017 at 2:32:45 PM, Julian Hyde (jh...@apache.org > <mailto:jh...@apache.org>) wrote: > >> I like the idea of co

Re: Drill Summit/Conference Proposal

I like the idea of co-hosting a conference. ApacheCon in particular is a good venue, and they explicitly encourage sub-conferences (there are “Big Data” and “IoT” tracks, and this year there were sub-conferences for Tomcat and CloudStack). DrillCon was part of ApacheCon, people could attend a

Re: Proposal for Skipping Records

It would be useful if you could describe the different ways that a record can be “bad”. IIRC the SQL standard divides the conditions into errors and warnings. Examples of a warning would be a string column that is truncated because it is too large for a varchar(20), or numeric underflow when

Re: Proposal for Skipping Records

t beliefs on the definition. However, > from the aspect of users' experience, they could just proceed and see the > different types of errors at the log, which helps them judge whether the > failure is tolerable or not. > > On Mon, Nov 16, 2015 at 11:56 AM, Julian Hyde <jh...@apache.org&