You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "nicolas maillard (JIRA)" <ji...@apache.org> on 2014/11/28 14:46:12 UTC

[jira] [Resolved] (PHOENIX-1093) Phoenix on Tez

     [ https://issues.apache.org/jira/browse/PHOENIX-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nicolas maillard resolved PHOENIX-1093.
---------------------------------------
    Resolution: Invalid

> Phoenix on Tez
> --------------
>
>                 Key: PHOENIX-1093
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1093
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: nicolas maillard
>
> Hello
> In case of complex queries and or joins would it make sense to have a phoenix intermediate server spin up a tez dag to resolve a query before sending back to the client.The coprocessors output could be seen as tez inputs. 
> So in the event of resulting datasets not fitting in memory for say complex joins. The results phoenix servers could become inputs for a tez job. Tez being a framework it could be embedded in this phoenix intermediate server,which would in turn decide to spin up a tez job or not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)