[
https://issues.apache.org/jira/browse/OAK-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344751#comment-14344751
]
Chetan Mehrotra commented on OAK-2499:
--------------------------------------
bq. though comma separated are a bit more easy to parse, json needs a library
Agreed. Only reason I switched to full fledged JSON usage was due to
requirement to escape. {{Text.escape}} would work but then you would need to
ensure that you do not escape it again if you have to pass these string later.
May be JSON is an overkill ... so I am open to change here
bq. I was thinking that maybe this property should be exposed also on the
NodeStore services, i.e. the properties of the underlying blobstore.
It would be preferable if you query from BlobStore directly
bq. but will that lookup only return one reference
Yes. On a given system there should only be only 0..1 BlobStore and 1..1
NodeStore active and registered in OSGi
> 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)
