[
https://issues.apache.org/jira/browse/HIVE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713830#action_12713830
]
Raghotham Murthy commented on HIVE-518:
---------------------------------------
There is now a test failure because of a change in hive-511 which was committed
after you created the patch. Can you regenerate the patch with the latest code?
[junit] 09/05/27 18:25:14 INFO exec.FileSinkOperator: Moving tmp dir:
/mnt/vol/devrs005.snc1/rmurthy/hive-committer/build/ql/tmp/_tmp.816501927.10000.insclause-0
to:
/mnt/vol/devrs005.snc1/rmurthy/hive-committer/build/ql/tmp/816501927.10000.insclause-0
[junit] diff -a -I \(file:\)\|\(/tmp/.*\)
/mnt/vol/devrs005.snc1/rmurthy/hive-committer/build/ql/test/logs/clientpositive/input30.q.out
/mnt/vol/devrs005.snc1/rmurthy/hive-committer/ql/src/test/results/clientpositive/input30.q.out
[junit] 23c23
[junit] < expr: (((hash(rand(UDFToLong(460476415))) &
2147483647) % 32) = 0)
[junit] ---
[junit] > expr:
(((default_sample_hashfn(rand(UDFToLong(460476415))) & 2147483647) % 32) = 0)
> 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.5.patch, hive.518.1.patch, hive.518.2.patch,
> hive.518.3.patch, hive.518.4.patch, hive.518.6.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.