Re: Avro - Let's talk Avro again

This is all great news. Seeing movement, and seeing it articulated, at a higher level, what has led to the discrepancies in Avro is also very helpful (thanks Paul). On Sat, Aug 19, 2017 at 6:29 PM, Stefán Baxter wrote: > Thank you Saurabh, > > I was not really

Re: Avro - Let's talk Avro again

Thank you Saurabh, I was not really expecting a constructive reply to my previous email, was appreciated. I guess some old frustration got the better of me. All the best, -Stefan On Fri, Aug 18, 2017 at 10:55 PM, Saurabh Mahapatra < saurabhmahapatr...@gmail.com> wrote: > Thank you for this

Re: Drill schema handling [Was: Avro - Let's talk Avro again]

Hello and thank you. Please also put this in the Avro context. That is quite reveling when thinking about Evolving schema support in Drill, not just for Avro but in general. Avro supports evolving schema and some might say it's designed around exactly that. The current handling of Avro in Drill

Drill schema handling [Was: Avro - Let's talk Avro again]

Hi All, Let’s also talk about the other core issue that Stefan raised: schema handling. Drill is very powerful in its use of JSON as its internal data format. Drill effortlessly handles maps and arrays as well as the more traditional scalar types. This can cause confusion, however. We all

Re: Avro - Let's talk Avro again

Let’s talk a bit about Avro as an example of the whole class of “extended” storage plugins maintained by the community. Today, each storage plugin requires very tight integration into Drill. Each must implement its own support for implicit columns (such as “filename” or “dir0”), must support

Re: Avro - Let's talk Avro again

Thank you for this candid feedback, Stefan. The fact that you even decided to write an email offering this feedback despite moving away from Drill just suggests to me that you are still a supporter. We need all the help that we can get from every member in this community to make Drill provide

Re: Avro - Let's talk Avro again

Hi John, Love Drill but we no longer use it in production as our main query tool. I do have a fairly long list of pet peeves but I also have a long list of features that I love and would not want to be without. In my opinion it's time for Drill to decide where its commitment lies regarding

Re: Avro - Let's talk Avro again

I’m not an Avro user, but I’d definitely vote for improving this. — C > On Aug 17, 2017, at 10:17, John Omernik wrote: > > I was guessing you would chime in with a response ;) > > Are you still using Drill w/ Avro how has things been lately? > > On Thu, Aug 17, 2017 at 8:00

Re: Avro - Let's talk Avro again

I was guessing you would chime in with a response ;) Are you still using Drill w/ Avro how has things been lately? On Thu, Aug 17, 2017 at 8:00 AM, Stefán Baxter wrote: > woha!!! > > > (sorry, I just had to) > > > Best of luck with that! > > Regards, > -Stefán > >

Re: Avro - Let's talk Avro again

woha!!! (sorry, I just had to) Best of luck with that! Regards, -Stefán On Thu, Aug 17, 2017 at 12:37 PM, John Omernik wrote: > I know Avro is the unwanted child of the Drill world. (I know others have > tried to mature the Avro support and that has been something that

Avro - Let's talk Avro again

I know Avro is the unwanted child of the Drill world. (I know others have tried to mature the Avro support and that has been something that still is in a "experiemental" state. That said, isn't it time for us to clean it up? I am sure I there are some open JIRAs out there, (last Doc update on