On 11/6/17 12:00 PM, Jesus Camacho Rodriguez wrote:
I am not involved in the Avatica effort, but it has been great to see Avatica
continue maturing, moving into its own repository and following with its own
release cadence. Josh, Julian, if you want to add a few lines about the state
of Avatica, that would be great.
Would be happy to :)
I've certainly been spending less time on core-functionality. Avatica
has definitely passed the cusp for what most developers need. The
majority of users would find Avatica to be fully-featured as a JDBC
interface (but there are some gaps that still exist).
We've started to see the focus on non-JDBC drivers for Avatica which is
a great sign. Our Francis has been making progress on trying to adopt
the driver written in Go into the Apache codebase. There are a few other
drivers available as well. The presence of these drivers, and their
ability to continue to function is good validation of the
protocol/stability model that we outlined/implemented in the past 1-2 years.
Avatica is still fairly low-volume, with only a few people contributing.
I'd love to see more people take an interest (it's a great stepping
stone into Calcite too ;P).
