[
https://issues.apache.org/jira/browse/HIVE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713666#action_12713666
]
Raghotham Murthy commented on HIVE-518:
---------------------------------------
one solution would be to provide another set option with the list of tables
which should not be sampled in test mode.
set hive.test.mode.unsampled.tables=table1,table2
Another option might be to actually allow users to specify the entire
tablesample clause for every table that needs to sampled in test-mode. But that
seems like a lot more work for not a lot of additional benefit.
> 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
>
>
> 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.
