[
https://issues.apache.org/jira/browse/DERBY-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765953#comment-13765953
]
ASF subversion and git services commented on DERBY-6127:
--------------------------------------------------------
Commit 1522744 from [~chaase3] in branch 'docs/branches/10.10'
[ https://svn.apache.org/r1522744 ]
DERBY-6127 Tell users to make sure that the state of a user-defined aggregate
needs to be serializable
Merged patch DERBY-6127.diff to 10.10 doc branch from trunk revision 1522740.
> Tell users to make sure that the state of a user-defined aggregate needs to
> be serializable
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-6127
> URL: https://issues.apache.org/jira/browse/DERBY-6127
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-6127.diff, DERBY-6127.stat, DERBY-6127.zip
>
>
> The Reference Manual section on "CREATE DERBY AGGREGATE statement" should
> tell users to make sure that all of the state of their user-defined aggregate
> is really serializable. This is because the Aggregator interface extends
> java.io.Serializable. A user-defined aggregate may end up being serialized to
> disk when performing grouped aggregation over a large number of groups. That
> is, intermediate results may be serialized to disk for a query like the
> following. The serialization will fail if the user-defined aggregate contains
> non-serializable fields:
> select a, myAggregate( b ) from myTable group by a
--
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
