Re: Continued Avro Frustration

I am frustrated that I couldn't make the hangout, and apologize to all here. Based on the notes from Jason, things seem to be on track. Are there any action items at his point, or was a good plan laid out on the hangout? If there anything else I can help with let me know. John On Saturday,

Re: Continued Avro Frustration

Prior to opening a JIRA for the doc change, I thought we could discuss here, unless I am misinterpreting how to use JIRA. My thought is this is more than a dev only thing, the documentation, and this "exception" to documenting Avro like this is due to how Avro support was explained, and I was

Re: Continued Avro Frustration

Hi John, I recommend opening a JIRA for the suggested doc updates. Others may have different opinions on what to document. Thanks, Bob On Sat, Apr 2, 2016 at 6:38 AM, John Omernik wrote: > This has been an interesting topic, and I am sorry I could not participate > more since

Re: Continued Avro Frustration

This has been an interesting topic, and I am sorry I could not participate more since my original post due to traveling. Stefán is obviously frustrated, and I can empathize with him. Being in a position of making architectural decisions as well, it can be difficult to help define a strategy for

Re: Continued Avro Frustration

I take some responsibility for your lack of response on this, because I had said I would try to take a look at the dirN issue that has been outstanding for some time with Avro. This might have prevented others from jumping in to help and I will work on communicating when I don't have time to work

Re: Continued Avro Frustration

Yes Parth, you are 100% right and we are willing to help. The relationship one builds with a community also depends on the "wipe/feeling" of the community and I know it reflects on me here, as well as the community, that many of my attempts to help and get help have not been fruitful. I also

Re: Continued Avro Frustration

+1 on marking Avro experimental. @Stefan, we have been trying to help you as much as our time permits. I know that I held up the 1.6 release while Jason fixed the issues that you brought up. As was said earlier, this is personal time we are spending to help users in the community, so providing an

Re: Continued Avro Frustration

To give credit where it is due. MapR seems to be willing to provide us with paid support even though we are not using their platform and we welcome that but we are still waiting for a followup email from the people Ted sent an introduction to. If that is a misunderstanding on my part, and they

Re: Continued Avro Frustration

Jacques, You are way out of line here! Let me remind you that I have volunteered resources, mine and other, on some of these and asked for pointers several times, to NO AVAIL! It's not as if the Drill project is easy to wrap ones head around or test (this latter has improved a bit). I have also

Re: Continued Avro Frustration

Stefan, It makes sense to me to mark the Avro plugin experimental. Clearly, there are bugs. I also want to note your requirements and expectations haven't always been in alignment with what the Avro plugin developers built/envisioned (especially around schemas). As part of trying to address these

Continued Avro Frustration

Hi, Is it at all possible that we are the only company trying to use Avro with Drill to some serious extent? We continue to coma across all sorts of embarrassing shortcomings like the one we are dealing with now where a schema change exception is thrown even when working with a single Avro file