[
https://issues.apache.org/jira/browse/MRUNIT-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ximo Guanter updated MRUNIT-180:
--------------------------------
Description:
Sometimes using withOutput and runTest is not possible if the .equals method is
not the correct way to compare equality. This is especially true for Mapper and
Reducers that return doubles or structure with doubles in them, since there is
no way to specify a desired error tolerance for the result.
Being able to specify a Comparator for the key and value types enabled the
usage of runTest for these cases.
was:
Sometimes using {{withOutput}} and {{runTest}} is not possible if the
{{.equals}} method is not the correct way to compare equality. This is
especially true for Mapper and Reducers that return doubles or structure with
doubles in them, since there is no way to specify a desired error tolerance for
the result.
Being able to specify a {{Comparator}} for the key and value types enabled the
usage of {{runTest}} for these cases.
> Being able to use a comparator on runTest
> -----------------------------------------
>
> Key: MRUNIT-180
> URL: https://issues.apache.org/jira/browse/MRUNIT-180
> Project: MRUnit
> Issue Type: Improvement
> Affects Versions: 0.9.0
> Reporter: Ximo Guanter
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: MRUNIT-180.patch
>
>
> Sometimes using withOutput and runTest is not possible if the .equals method
> is not the correct way to compare equality. This is especially true for
> Mapper and Reducers that return doubles or structure with doubles in them,
> since there is no way to specify a desired error tolerance for the result.
> Being able to specify a Comparator for the key and value types enabled the
> usage of runTest for these cases.
--
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: http://www.atlassian.com/software/jira
