You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Arina Ielchiieva (JIRA)" <ji...@apache.org> on 2018/07/26 09:12:00 UTC
[jira] [Updated] (DRILL-6628) Possible incorporation of Twitter
text processing UDFs into Drill-proper
[ https://issues.apache.org/jira/browse/DRILL-6628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arina Ielchiieva updated DRILL-6628:
------------------------------------
Labels: doc-impacting (was: )
> Possible incorporation of Twitter text processing UDFs into Drill-proper
> ------------------------------------------------------------------------
>
> Key: DRILL-6628
> URL: https://issues.apache.org/jira/browse/DRILL-6628
> Project: Apache Drill
> Issue Type: Improvement
> Components: Functions - Drill
> Reporter: Bob Rudis
> Priority: Major
> Labels: doc-impacting
>
> Per the User mailing list thread — [https://mail-archives.apache.org/mod_mbox/drill-user/201807.mbox/%3Caef1979d-f454-4691-8607-8267adf2ac1e%40getmailbird.com%3E] — submitting the possibility for the inclusion of drill-twitter-text — [https://github.com/hrbrmstr/drill-twitter-text] — into Drill-proper.
> Shifting the conversation here since it's more appropriate and CC'ing [~cgivre] who posited the idea.
> On the one hand, there are function groups such as "Phonetic" and "String Distance" so there's precedent for inclusion of "non-boring-SQL"-like functions into Drill-proper. On the other hand, this is a small addition of a handful of functions for Twitter text so would this be to niche for a "Twitter" function group?
> As noted in the mailing list thread, there are more "cyber"-ish UDFs on the way (still kinda hoping for that guava upgrade that I saw mentioned in various places in jira), so would the Twitter components be in a "Cyber" group?
> Regardless, I'll take a look at how the functions are structured in the Drill source tree and gladly machinate the necessary changes/inclusions if the result of this discussion results in that decision.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)