[
https://issues.apache.org/jira/browse/HIVE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zheng Shao updated HIVE-518:
----------------------------
Description:
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
New Options:
{code}
// whether hive is running in test mode. If yes, it turns on sampling and
prefixes the output tablename
set hive.test.mode=true;
// if hive is running in test mode, prefixes the output table by this string
set hive.test.mode.prefix=;
// if hive is running in test mode and table is not bucketed, sampling frequency
set hive.test.mode.samplefreq=256;
// if hive is running in test mode, dont sample the above comma seperated list
of tables
set hive.test.mode.nosamplelist=;
{code}
was:
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
> test mode in hive
> -----------------
>
> Key: HIVE-518
> URL: https://issues.apache.org/jira/browse/HIVE-518
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
> Affects Versions: 0.3.1
> Reporter: Namit Jain
> Assignee: Namit Jain
> Fix For: 0.4.0
>
> Attachments: hive-518.5.patch, hive.518.1.patch, hive.518.2.patch,
> hive.518.3.patch, hive.518.4.patch, hive.518.6.patch, hive.518.7.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
> New Options:
> {code}
> // whether hive is running in test mode. If yes, it turns on sampling and
> prefixes the output tablename
> set hive.test.mode=true;
> // if hive is running in test mode, prefixes the output table by this string
> set hive.test.mode.prefix=;
> // if hive is running in test mode and table is not bucketed, sampling
> frequency
> set hive.test.mode.samplefreq=256;
> // if hive is running in test mode, dont sample the above comma seperated
> list of tables
> set hive.test.mode.nosamplelist=;
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
