jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2499) Expose mongo and db versions for reporting purposes
Date Tue, 03 Mar 2015 05:16:04 GMT

    [ https://issues.apache.org/jira/browse/OAK-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344545#comment-14344545

Chetan Mehrotra commented on OAK-2499:

[~mpetria] I have applied a slightly modified patch of yours with [1663526|http://svn.apache.org/r1663526].
The description is now a JSON string to allow easier parsing of attributes and also handle
escaping. So now it looks like following

{"type":"rdb","db":"H2","version":"1.4.182 (2014-10-17)"}

Also with [1663528|http://svn.apache.org/r1663528] exposed description for few blob stores
and also for SegmentNodeStore.

Can you have a look and confirm if these changes meet your requirement. Would then resolve
the issue accordingly

> Expose mongo and db versions for reporting purposes
> ---------------------------------------------------
>                 Key: OAK-2499
>                 URL: https://issues.apache.org/jira/browse/OAK-2499
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk, rdbmk, segmentmk
>            Reporter: Marius Petria
>            Assignee: Chetan Mehrotra
>         Attachments: OAK-2499.1.diff, OAK-2499.2.diff
> For reporting purposes I need to find out from java the MK type and also
> for mongo version and the info about used DB make/version?
> [~chetanm] suggested that such information can be exposed "when we register a
> {{NodeStore}} instances within OSGi we can also add a service property
> which captures such implementation details. Possibly use
> service.description or define a new one which provide a comma separated
> list of attributes.”

This message was sent by Atlassian JIRA

View raw message