Better error message on format inconsistency detection

[GoogleCodeExporter]

Max wrote:

What I suggest however, is a different error message for errors during 
materialization. As I gathered during debugging, once there's a problem, the 
error is signalled pretty quickly. So I think it would be quite easy to 
remember the last cluster (or at least it's type, like 
"FLPrimitiveCluster[Date]") and signal the error accordingly. For example:

"An error occurred during materialization, probably because the serializer used 
a different format than I'm trying to read. The last cluster was 
FLPrimitiveCluster and the objects where of type Date. The difference in format 
can very likely be traced one of these classes."

Original issue reported on code.google.com by [email protected] on 15 Feb 2013 at 8:46

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.