[
https://issues.apache.org/jira/browse/SLING-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793623#comment-13793623
]
Carsten Ziegeler commented on SLING-3167:
-----------------------------------------
The idea is that all information about a job is stored as information of a
single resource, and making the usage of the whole log easy (string array).
I can see that this might become a performance issue if a job heavily uses the
log as each entry is directly written to the repository. We could do batch
writes for this if necessary.
There are already resource changed events when the log is updated, so these
could be used by a listener directly (filter would be resource type and the
property holding the log entries).
[[email protected]] Do you have an alternative in mind?
> Job Logging
> -----------
>
> Key: SLING-3167
> URL: https://issues.apache.org/jira/browse/SLING-3167
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> Job.getProcessLog() - is it a good solution to use a String[] type for this?
> as i see this is currently through all the implementation that every writing
> of a log message reads gets the existing string array, copies it to a new
> array and adds the new log message. the reason is that its easy then to store
> it in a JCR compatible value map. i'm just thinking if its a good idea if a
> job produces thousands of log messages. perhaps its acceptable overall. if
> you think about and admin GUI which refreshes every second to show the log
> messages of a job currently running... perhaps it would be nice to have a
> listener interface for such log messages as well.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
