hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gang Tim Liu (JIRA)" <>
Subject [jira] [Created] (HIVE-4377) Add more comment to (HIVE-2340)
Date Thu, 18 Apr 2013 15:37:15 GMT
Gang Tim Liu created HIVE-4377:

             Summary: Add more comment to (HIVE-2340)
                 Key: HIVE-4377
             Project: Hive
          Issue Type: Bug
          Components: Query Processor
            Reporter: Gang Tim Liu
            Assignee: Navis

thanks a lot for addressing optimization in HIVE-2340. Awesome!

Since we are developing at a very fast pace, it would be really useful to
think about maintainability and testing of the large codebase. Highlights which are applicable
for D1209:

  1.  Javadoc for all public/private functions, except for
setters/getters. For any complex function, clear examples (input/output)
would really help.
  2.  Specially, for query optimizations, it might be a good idea to have
a simple working query at the top, and the expected changes. For e.g..
The operator tree for that query at each step, or a detailed explanation
at the top.
  3.  If possible, the test name (.q file) where the function is being
invoked, or the query which would potentially test that scenario, if it
is a query processor change.
  4.  Comments in each test (.q file)­ that should include the jira
number,  what is it trying to test. Assumptions about each query.
  5.  Reduce the output for each test ­ whenever query is outputting more
than 10 results, it should have a reason. Otherwise, each query result
should be bounded by 10 rows.

thanks a lot

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message