Approach as described seems sound to me. Will review path early next week.
On Jun 13, 2012, at 9:46 PM, "Prasanth J (JIRA)" <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/PIG-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294806#comment-13294806 > ] > > Prasanth J commented on PIG-2726: > --------------------------------- > > This patch converts null values in dimensions to "unknown" and uses actual > null value for rollup. For a sample input > > red, ,12 > > CUBE operator will now generate > > red,unknown,12 > ,unknown,12 > red, ,12 > , ,12 > > Please let me know if it is ok to go ahead with null for rollup? another > alternative would be to use "*" or "all" to represent rollup value. > >> Handling legitimate NULL values >> ------------------------------- >> >> Key: PIG-2726 >> URL: https://issues.apache.org/jira/browse/PIG-2726 >> Project: Pig >> Issue Type: Sub-task >> Affects Versions: 0.11 >> Reporter: Prasanth J >> Assignee: Prasanth J >> Attachments: PIG-2726.1.patch >> >> >> Look into SQL/Oracle server for how they are handling legitimate NULL values >> in the input while performing operations like roll-up, filtering etc. >> Current implementation outputs NULL string which should be replaced by >> actual null value. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
