[
https://issues.apache.org/jira/browse/PHOENIX-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maryann Xue resolved PHOENIX-1845.
----------------------------------
Resolution: Fixed
> Implement two sets (server and client) of Phoenix conventions
> -------------------------------------------------------------
>
> Key: PHOENIX-1845
> URL: https://issues.apache.org/jira/browse/PHOENIX-1845
> Project: Phoenix
> Issue Type: Task
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Original Estimate: 240h
> Remaining Estimate: 240h
>
> PhoenixAggregate, PhoenixSort, PhoenixJoin and PhoenixProject will be
> sub-classed to PhoenixServerAggregate, PhoenixClientAggregate,
> PhoenixServerSort, PhoenixClientSort, etc. There will be quite an amount of
> code sharing between the server classes and the client classes (the shared
> code will remain in the original classes of course), but the idea is to avoid
> server/client flags attached to each PhoenixRel node and looking into child
> nodes. This will be done through rule matching, and server classes would
> normally have a cheaper cost than their client counterparts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
