jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marius Petria (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-2499) Expose mongo and db versions for reporting purposes
Date Mon, 02 Mar 2015 15:44:04 GMT

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

Marius Petria edited comment on OAK-2499 at 3/2/15 3:43 PM:
------------------------------------------------------------

[~chetanm] I made another patch following your suggestions.

Property oak.nodestore.description on DocumentNodeService 
{code}
type=rdb,db={dbName},version={dbVersion}
type=mongo,version={mongoVersion}
type=memory
{code}

One question, I am using Text.escape to prevent dbVersion and name to mess with separators.
Are these guaranteed not to be null?


was (Author: mpetria):
[~chetanm] I made another patch following your suggestions.

Property oak.nodestore.description on DocumentNodeService 

type=rdb,db={dbName},version={dbVersion}
type=mongo,version={mongoVersion}

One question, I am using Text.escape to prevent dbVersion and name to mess with separators.
Are these guaranteed not to be null?

> 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
(v6.3.4#6332)

Mime
View raw message