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

Marius Petria commented on OAK-2499:
------------------------------------

Hi Chetan,

I am fine with whatever map serialization is convenient for OAK (though comma 
separated are a bit more easy to parse, json needs a library).

I see that you exposed oak.blobstore.description on some BlobStore services. I 
was thinking that maybe this property should be exposed also on the NodeStore 
services, i.e. the properties of the underlying blobstore.

More generally I would like to ask how can one obtain the information about the 
"active" node store (blob store?). I was planning to use 
{code}
            ServiceReference[] references = 
bundleContext.getAllServiceReferences("org.apache.jackrabbit.oak.spi.state.NodeStore",
 null);
{code}
but will that lookup only return one reference? If multiple references are 
returned which is the "active" one? If I am to query also the BlobStores, how 
do I figure out which is the active one?


> 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)

Reply via email to