Boaz,
If that’s the case… I’ll have 2 PRs for Drill v 1.17 ;-)
> On Mar 22, 2019, at 14:25, Boaz Ben-Zvi <b...@apache.org> wrote:
>
> Hi Charles,
>
> If these updates are only small simple tasks, it would not be a big issue
> to add them to the Drill Release Process (see [1]).
>
> BTW, most of the release work is automated via a script (see section 4 in
> [1]); so if these updates could be automated as well, it would be a trivial
> matter,
>
> Thanks for your useful contributions,
>
> -- Boaz
>
> [1] https://github.com/parthchandra/drill/wiki/Drill-Release-Process
>
> On 3/22/19 11:13 AM, Charles Givre wrote:
>> Hello all,
>> I have a question regarding new Drill features. I have two UDFs which I’ve
>> been considering submitting but these UDFs will require regular updating.
>> The features in question are UDFs to do IP Geolocation and a User Agent
>> Parser. The IP geolocation is dependent on the MaxMind database and
>> associated libraries. Basically if it were to be included in Drill, every
>> release we would have to update the MaxMind DB. (This is done in many tools
>> that rely on it for IP Geolocation)
>>
>> The other is the user agent parser. Likewise, the only updating it would
>> need would be to update the pom.xml file to reflect the latest version of
>> the UA parser. These are both very useful features for security analysis
>> but I wanted to ask the Drill developer community if this is something we
>> wanted to consider.
>> — C
