[
https://issues.apache.org/jira/browse/GIRAPH-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitay Joffe updated GIRAPH-693:
-------------------------------
Description:
We have a lot of cases of users running long jobs and then failing at the Hive
output step because of some misconfigured schema or type mismatch. We'd like to
move these errors as soon as possible.
To make this happen I am adding check{In,Out}put methods to the
HiveTo{Edge,Vertex} and VertexToHive API and letting the user do their checks.
Look at the diff for examples and tests.
https://reviews.apache.org/r/11927/
was:
We have a lot of cases of users running long jobs and then failing at the Hive
output step because of some misconfigured schema or type mismatch. We'd like to
move these errors as soon as possible.
To make this happen I am creating a fake vertex and fake record saver and
calling out to user code to write it in checkOutputSpecs (which happens at the
beginning). This should catch a lot of user errors early on.
https://reviews.apache.org/r/11927/
> Giraph-Hive check user code as soon as possible
> -----------------------------------------------
>
> Key: GIRAPH-693
> URL: https://issues.apache.org/jira/browse/GIRAPH-693
> Project: Giraph
> Issue Type: Bug
> Reporter: Nitay Joffe
> Assignee: Nitay Joffe
>
> We have a lot of cases of users running long jobs and then failing at the
> Hive output step because of some misconfigured schema or type mismatch. We'd
> like to move these errors as soon as possible.
> To make this happen I am adding check{In,Out}put methods to the
> HiveTo{Edge,Vertex} and VertexToHive API and letting the user do their
> checks. Look at the diff for examples and tests.
> https://reviews.apache.org/r/11927/
--
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
