Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <1485700611.1243455225541.JavaMail.jira@brutus>
Date: Wed, 27 May 2009 13:13:45 -0700 (PDT)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Updated: (HIVE-518) test mode in hive
In-Reply-To: <789957255.1243370865787.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Namit Jain updated HIVE-518:
----------------------------

    Attachment: hive.518.4.patch

> test mode in hive
> -----------------
>
>                 Key: HIVE-518
>                 URL: https://issues.apache.org/jira/browse/HIVE-518
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.3.1
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>             Fix For: 0.4.0
>
>         Attachments: hive.518.1.patch, hive.518.2.patch, hive.518.3.patch, hive.518.4.patch
>
>
> It would be good to have a test mode in hive - this will help in checking the validity of a hive drop on a production cluster.
> The following would be good to have:
> Testmode --> In testmode, all input tables are sampled (if not already sampled) and all output tables are prefixed by a user supplied name.
> This way, multiple hive drops can be compared quickly for correctness

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.