Hi Damien,
Like Jason said, we have a heartbeat mechanism that should've prevented
this issue all together, so I'm interested to learn how this is happening.
We've seen this happen many times but so far we were never able to
reproduce it.
Could you give us more details so we can reproduce the
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
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
This is a good idea, especially in light of some of the frustrations around
Avro. From a project perspective, what are your thoughts related to
plugins that could be released as experimental? Do you think we should
setup a separate project from the Drill project? Should a goal be to move
plugins
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
Experimental plugins:
I strongly believe in the open architecture offered by Drill, and I would
welcome a plugin dictionary separated from core Apache Drill where
"experimental" and / or even commercial plugins could be shared. (similar
to how Spark is dealing with packages) I believe experimental