jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Ryan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4712) Publish S3DataStore stats in JMX MBean
Date Fri, 02 Sep 2016 04:22:21 GMT

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

Matt Ryan commented on OAK-4712:

[~amjain] I thought of the same issue that you mentioned, how the path to the node in question
may not actually have the binary property.  This was certainly true in my testing, where I
was working with nodes of type dam:Asset.  In that case, an image named "pic.jpg" might actually
 have the binary property at the path "content/dam/pic.jpg/jcr:content/renditions/original/jcr:content".

I will seek for clarification.  But after some thought it occurred to me that it shouldn't
be Oak's responsibility to figure out what the user making the request may have meant, if
they were to provide e.g. "content/dam/pic.jpg".  In my way of thinking, only the full path
to the node containing the binary property makes sense at the Oak level.  Applications with
a more specific purpose than Oak could leverage the functionality by interpreting user input
for their specific use case.


> Publish S3DataStore stats in JMX MBean
> --------------------------------------
>                 Key: OAK-4712
>                 URL: https://issues.apache.org/jira/browse/OAK-4712
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: blob
>            Reporter: Matt Ryan
>         Attachments: OAK-4712.2.diff, OAK-4712.3.diff
> This feature is to publish statistics about the S3DataStore via a JMX MBean.  There are
two statistics suggested:
> * Indicate the number of files actively being synchronized from the local cache into
> * Given a path to a local file, indicate whether synchronization of file into S3 has

This message was sent by Atlassian JIRA

View raw message