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 datab
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
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 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 releas
Two rly 👍 UDFs, too!
Charles: many of the FOSS (or even non-FOSS) security tools we both likely tend
to use in either of those contexts put the onus of updating the core DBs on the
end-user (and try to go out of their way in the docs re: need to do that).
I think as long as the version included
I am not sure that library update should be included in the release process. On
the contrary, I think it should be done via regular PR process. Of course, you
always have to find a volunteer :)
Kind regards,
Arina
> On Mar 22, 2019, at 8:39 PM, Bob Rudis wrote:
>
> Two rly 👍 UDFs, too!
>
> C
