[
https://issues.apache.org/jira/browse/MAHOUT-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845484#action_12845484
]
Sean Owen commented on MAHOUT-337:
----------------------------------
In theory, this derived / cached value isn't part of a serialized state as it
can be recomputed. That's only a broad principle.
The tradeoff is indeed between paying to serialize, store, transmit, and
deserialize this value versus recomputing once in a while during
deserialization. My gut is that the former is significantly more expensive.
Yes it's possible to fix this by forcing vectors to compute their
length-squared always before serialization. That's another bit of the price to
pay, since not all vectors need this.
> Don't serialize cached length squared in JSON vector representation
> -------------------------------------------------------------------
>
> Key: MAHOUT-337
> URL: https://issues.apache.org/jira/browse/MAHOUT-337
> Project: Mahout
> Issue Type: Bug
> Components: Math
> Affects Versions: 0.3
> Reporter: Sean Owen
> Assignee: Sean Owen
> Priority: Minor
> Fix For: 0.4
>
>
> The cached length-squared field in vectors should be marked transient so that
> it is not part of the JSON serialized state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
