You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (JIRA)" <ji...@apache.org> on 2019/05/05 18:54:00 UTC

[jira] [Commented] (CALCITE-2741) Add operator table with Hive-specific built-in functions

    [ https://issues.apache.org/jira/browse/CALCITE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833429#comment-16833429 ] 

Stamatis Zampetakis commented on CALCITE-2741:
----------------------------------------------

Hi [~hhlai1990],

I had a quick look and it seems like a very interesting project, that also required a lot of work. It will certainly inspire other people who are building custom SQL engines ;)

Can you clarify a bit what exactly you would like to contribute back to Calcite? I guess it is more than a new operator table for Hive, as the current summary indicates. 
It seems that you are proposing a new adapter but I don't know if it fits the current definition of an adapter which is "Connect to third-party data sources, browse metadata, and optimize by pushing the computation to the data".



> Add operator table with Hive-specific built-in functions
> --------------------------------------------------------
>
>                 Key: CALCITE-2741
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2741
>             Project: Calcite
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 1.19.0
>            Reporter: Lai Zhou
>            Priority: Minor
>
> I write a hive adapter for calcite to support Hive sql ,includes UDF、UDAF、UDTF and some of SqlSpecialOperator.
> How do you think of supporting a direct implemention of hive sql like this?
> I think it will be valuable when someone want to migrate his hive etl jobs to real-time scene.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)