[
https://issues.apache.org/jira/browse/JCR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227413#comment-13227413
]
Jukka Zitting commented on JCR-3243:
------------------------------------
+1 Looks good to me.
Regarding "RepositoryStatisticsImpl implements Iterable"; since that's only in
jackrabbit-core, I'd consider it an implementation detail that we can change
without problems if there's a reason to do so. Only the interfaces in
jackrabbit-api need to remain strictly backwards-compatible.
> RepositoryStatistics should be more flexible
> --------------------------------------------
>
> Key: JCR-3243
> URL: https://issues.apache.org/jira/browse/JCR-3243
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-api, jackrabbit-core
> Reporter: Mete Atamel
> Priority: Minor
> Attachments: JCR-3243-2.patch, JCR-3243-3.patch, JCR-3243-4.patch,
> JCR-3243.patch
>
>
> Right now, Jackrabbit reports TimeSeries for things like BUNDLE_READ_COUNTER,
> BUNDLE_WRITE_COUNTER, etc. but there is no way to extend Jackrabbit and
> report TimeSeries for additional properties. That's because the type of
> TimeSeries are defined in RepositoryStatistics class as Type enum. Enums in
> Java cannot be extended which limits to TimeSeries to the Types defined in
> RepositoryStatistics.
> I suggest that RepositoryStatistics is improved to allow additional
> TimeSeries. One approach is to define an additional
> RepositoryStatistics#getType(String) method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
