Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1843

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #1843

[Apache Jenkins Server]

See 

Jenkins build is back to normal : sling-trunk-1.7 » Apache Sling Event Support #217

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #217

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #217

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 #1843

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-trunk-1.7 #217

[Apache Jenkins Server]

See 

[jira] [Created] (SLING-3028) Support for progress tracking of jobs

[Victor Saar (JIRA)]

Victor Saar created SLING-3028:
--

 Summary: Support for progress tracking of jobs
 Key: SLING-3028
 URL: https://issues.apache.org/jira/browse/SLING-3028
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Victor Saar


For long-running jobs, it would be useful to have some means to track progress, 
which can be shown in a console for the user. This should include the following:

* ETA
* Completeness value computed from (optional, defaults to 1.0) max and current 
value (e.g. 42% or 23/100)
* Log output stream for detailed progress information
* Failure reason in case job failed

AFAICS this requires a few changes to the existing implementation:

* Jobs need additional support for setting properties, e.g. max and current 
progress value
* Jobs need to be kept at least for a while after they completed/failed to give 
access to failure information/log stream

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3029) [Tooling] support connecting to sling launchpad in debug mode

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3029:
--

 Summary: [Tooling] support connecting to sling launchpad in debug 
mode
 Key: SLING-3029
 URL: https://issues.apache.org/jira/browse/SLING-3029
 Project: Sling
  Issue Type: New Feature
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli


>From Eclipse, using the slingclipse feature, it should be possible to connect 
>to a configured sling-launchpad-server not only in 'run' mode but also in 
>'debug' mode. The corresponding setting of the debug port should be available 
>in the server configuration, and connecting in debug mode should take care of 
>anything necessary to be otherwise done (including making sure, source code 
>lookup works)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3030) [Tooling] support (auto-) deploy of content-bundles

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3030:
--

 Summary: [Tooling] support (auto-) deploy of content-bundles
 Key: SLING-3030
 URL: https://issues.apache.org/jira/browse/SLING-3030
 Project: Sling
  Issue Type: New Feature
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli


Similar to SLING-3009 in Eclipse it should be possible to (auto-) deploy a 
content-bundle easily using the configured launchpad-server. This feature will 
eventually integrate with SLING-2985

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3031) [Tooling] add whitelabel support for slingclipse

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3031:
--

 Summary: [Tooling] add whitelabel support for slingclipse
 Key: SLING-3031
 URL: https://issues.apache.org/jira/browse/SLING-3031
 Project: Sling
  Issue Type: New Feature
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli


For the slingclipse plugin, at certain locations, it should be possible to 
'brand' the plugins. Eg add custom icons, labels etc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2985) [Tooling] show content of .content.xml in project explorer

[Stefan Egli (JIRA)]

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

Stefan Egli commented on SLING-2985:


Plus further common features of the 'content browser' include:
 * standard actions on files - eg double-click -> open
 * properties of jcr nodes should be visible in the properties view - and 
editable using appropriate cell editors

> [Tooling] show content of .content.xml in project explorer
> --
>
> Key: SLING-2985
> URL: https://issues.apache.org/jira/browse/SLING-2985
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Irrespective of the chosen serialization the content of .content.xml should 
> be shown in the tree structure of the project explorer. This can be achieved 
> using a Navigator Content Extension (NCE) (which is part of the Common 
> Navigator Framework (CNF) of eclipse).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2985) [Tooling] show content of .content.xml in project explorer

[Stefan Egli (JIRA)]

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

Stefan Egli commented on SLING-2985:


Also: filter out the packagefragment 'jcr_root' which gets shown by JDT 
automatically

> [Tooling] show content of .content.xml in project explorer
> --
>
> Key: SLING-2985
> URL: https://issues.apache.org/jira/browse/SLING-2985
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Irrespective of the chosen serialization the content of .content.xml should 
> be shown in the tree structure of the project explorer. This can be achieved 
> using a Navigator Content Extension (NCE) (which is part of the Common 
> Navigator Framework (CNF) of eclipse).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3032) [Tooling] add a 'new' wizard for creating an application based on a maven archetype

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3032:
--

 Summary: [Tooling] add a 'new' wizard for creating an application 
based on a maven archetype
 Key: SLING-3032
 URL: https://issues.apache.org/jira/browse/SLING-3032
 Project: Sling
  Issue Type: New Feature
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli


In Eclipse, in the slingclipse plugin, it should be easily possible to create a 
new application based on an available maven archetype. The archetype needs to 
fulfill certain criterias, eg contain 'content-bundle' and 'bundle' modules - 
besides 'pom' modules that represent the reactor/parent structure. The 'new' 
wizard takes care of setting up the projects accordingly with any eclipse 
specific features (eg setting a 'project facet' and setting any sling 
properties accordingly) - also, the new projects (the 'content-bundle' and the 
'bundle' modules that is) should be added to a launchpad server - which either 
already exists or is created as part of the 'new' wizard. 

Following the SLING-3031 whitelabel support, this 'new' wizard contains hooks 
for further 'branding'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3033) [Tooling] differentiate between internal/embedded and externally (manually) started server

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3033:
--

 Summary: [Tooling] differentiate between internal/embedded and 
externally (manually) started server
 Key: SLING-3033
 URL: https://issues.apache.org/jira/browse/SLING-3033
 Project: Sling
  Issue Type: New Feature
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli


Differentiate between two kinds of servers:
 * eclipse-internal ones: those are started/stopped by eclipse in the servers 
view
 * eclipse-external ones: those are started manually by the user outside of 
eclipse (the more frequent use case probably)

Reflect this differentiation in the UI accordingly

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2779) Support for default properties values of a resource

[Gilles Knobloch (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilles Knobloch updated SLING-2779:
---

Attachment: SLING-2779_20130828.patch

Attaching a new patch

* Changed constructor signature to use two ValueMap instead of Map, so that 
CompositeValueMap relies on existing implementations of ValueMap for type 
conversion
* Fixed keySet(), entrySet(), and values(), added more tests to cover them
* Updated JavaDoc
* Replaced some ternary statements by if-then-else
* Created org.apache.sling.api.resource.ValueMapUtil with checkKey method
* Increased version number of exported package version

> Support for default properties values of a resource
> ---
>
> Key: SLING-2779
> URL: https://issues.apache.org/jira/browse/SLING-2779
> Project: Sling
>  Issue Type: New Feature
>  Components: API
>Affects Versions: API 2.3.0
>Reporter: Gilles Knobloch
> Attachments: SLING-2779_20130828.patch, SLING-2779.patch
>
>
> I already noticed several times it would be useful to be able to specify a 
> default properties for a resource:
> * if the resource itself contains the property, it will override the default 
> one.
> * but if it doesn't, the default value is used.
> This could be done either via:
> * specifying a {{sling:defaults}} property on the resource, which contains 
> the path to the resource which properties will be used by default.
> * providing a default map of properties
> Attaching a patch for review.
> For testing purpose, I put it under {{org.apache.sling.defaults}}, but I 
> imagine it could go to {{org.apache.sling.api.resource}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #218

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #218

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 #218

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #1844

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1844

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 #1844

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #219

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #219

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 #219

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #1845

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 #1845

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1845

[Apache Jenkins Server]

See 

[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats

[Dishara Wijewardana (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dishara Wijewardana updated SLING-3026:
---

Attachment: CassandraLatencyReport_V1.txt

Here I am attaching the latest test results which includes latency to pull data 
from a 10M and 100M collections. 

> Cassandra Resource Provider READ Latency Stats 
> ---
>
> Key: SLING-3026
> URL: https://issues.apache.org/jira/browse/SLING-3026
> Project: Sling
>  Issue Type: Task
>Reporter: Dishara Wijewardana
>Priority: Critical
> Attachments: CassandraIntegrationTest.patch, 
> CassandraLatencyReport.txt, CassandraLatencyReport_V1.txt, 
> SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt, 
> SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, 
> SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png
>
>
> This is to keep track on the statistics of the latency for the requests done 
> on Cassandra layer through Cassandra Resource Provider. Here we use Apache 
> Benchmark. 
> We have a test profile java component in the cassandra module to add bulk 
> test data to cassandra. 
> /content/cassandra/A/0   to /content/cassandra/A/999
> /content/cassandra/B/0   to /content/cassandra/B/
> /content/cassandra/C/0   to /content/cassandra/C/9
> /content/cassandra/D/0   to /content/cassandra/D/99
> And then this JIRA will keep track of reports on the http request time to 
> retrieve 1 node from each following data collection.
>   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats

[Dishara Wijewardana]

Hi Ian,
I have updated the latest results in the JIRA, and please find the report
named "CassandraLatencyReport_V1.txt" to get the latest results. I improve
the report also to get average latency under each node. So the node "E" and
"F" will have 10M and 100M collection.

P.S It took >7 hrs for me to populate a 100M collection :-). Seems it's
worth spending that much of time for populating a 100M collection by seeing
the results.

===
== FIRST RUN TEST
SUMMERY==
[RESULT] Average Latency Under Node A(1K)   = 14 (ms)
[RESULT] Average Latency Under Node B(10K)  = 11 (ms)
[RESULT] Average Latency Under Node C(100K) = 12 (ms)
[RESULT] Average Latency Under Node D(1M)   = 21 (ms)
[RESULT] Average Latency Under Node E(10M)  = 21 (ms)
[RESULT] Average Latency Under Node F(100M) = 16 (ms)
[FIRST RUN] #TOTAL CALLS = 600 Total Average Latency = 16 (ms)
===
== SECOND RUN TEST
SUMMERY==
[RESULT] Average Latency Under Node A(1K)   = 10 (ms)
[RESULT] Average Latency Under Node B(10K)  = 15 (ms)
[RESULT] Average Latency Under Node C(100K) = 14 (ms)
[RESULT] Average Latency Under Node D(1M)   = 14 (ms)
[RESULT] Average Latency Under Node E(10M)  = 11 (ms)
[RESULT] Average Latency Under Node F(100M) = 14 (ms)
[FIRST RUN] #TOTAL CALLS = 600 Total Average Latency = 13 (ms)
===









On Thu, Aug 29, 2013 at 6:37 AM, Dishara Wijewardana (JIRA)  wrote:

>
>  [
> https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Dishara Wijewardana updated SLING-3026:
> ---
>
> Attachment: CassandraLatencyReport_V1.txt
>
> Here I am attaching the latest test results which includes latency to pull
> data from a 10M and 100M collections.
>
> > Cassandra Resource Provider READ Latency Stats
> > ---
> >
> > Key: SLING-3026
> > URL: https://issues.apache.org/jira/browse/SLING-3026
> > Project: Sling
> >  Issue Type: Task
> >Reporter: Dishara Wijewardana
> >Priority: Critical
> > Attachments: CassandraIntegrationTest.patch,
> CassandraLatencyReport.txt, CassandraLatencyReport_V1.txt,
> SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt,
> SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png,
> SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png
> >
> >
> > This is to keep track on the statistics of the latency for the requests
> done on Cassandra layer through Cassandra Resource Provider. Here we use
> Apache Benchmark.
> > We have a test profile java component in the cassandra module to add
> bulk test data to cassandra.
> > /content/cassandra/A/0   to /content/cassandra/A/999
> > /content/cassandra/B/0   to /content/cassandra/B/
> > /content/cassandra/C/0   to /content/cassandra/C/9
> > /content/cassandra/D/0   to /content/cassandra/D/99
> > And then this JIRA will keep track of reports on the http request time
> to retrieve 1 node from each following data collection.
> >
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>



-- 
Thanks
/Dishara

[jira] [Commented] (SLING-3028) Support for progress tracking of jobs

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-3028:
-

I like the idea in general - can we come up with some criteria when a job needs 
to be kept after its finished? I don't want to keep all jobs all the time.So as 
you suggest we can configure a time for how long the jobs are kept, but I think 
we need an additional way to identify the jobs to keep.
Simplest solution would be to add this as a configuration property of the queue 
- but this doesn't feel quiet right


> Support for progress tracking of jobs
> -
>
> Key: SLING-3028
> URL: https://issues.apache.org/jira/browse/SLING-3028
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Victor Saar
>  Labels: jobs
>
> For long-running jobs, it would be useful to have some means to track 
> progress, which can be shown in a console for the user. This should include 
> the following:
> * ETA
> * Completeness value computed from (optional, defaults to 1.0) max and 
> current value (e.g. 42% or 23/100)
> * Log output stream for detailed progress information
> * Failure reason in case job failed
> AFAICS this requires a few changes to the existing implementation:
> * Jobs need additional support for setting properties, e.g. max and current 
> progress value
> * Jobs need to be kept at least for a while after they completed/failed to 
> give access to failure information/log stream

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats

[Ian Boston]

Hi Dishara,
That was definitely worth doing. Looks like it is flat scalable on
read in this form up to 100M items per collection. Before I get too
excited about the results, are you absolutely certain that the
ResourceProvider is retrieving the items requested and not just short
circuiting somewhere ?

I'll think you are clear to go onto the next phase if you are willing.
I think you have an option. Do write or do access control. Write will
be more exciting, access control will be more thought intensive. You
may already have most of the write code, as you just wrote 100M items!

Which one ?
Ian

On 29 August 2013 02:12, Dishara Wijewardana  wrote:
> Hi Ian,
> I have updated the latest results in the JIRA, and please find the report
> named "CassandraLatencyReport_V1.txt" to get the latest results. I improve
> the report also to get average latency under each node. So the node "E" and
> "F" will have 10M and 100M collection.
>
> P.S It took >7 hrs for me to populate a 100M collection :-). Seems it's
> worth spending that much of time for populating a 100M collection by seeing
> the results.
>
> ===
> == FIRST RUN TEST
> SUMMERY==
> [RESULT] Average Latency Under Node A(1K)   = 14 (ms)
> [RESULT] Average Latency Under Node B(10K)  = 11 (ms)
> [RESULT] Average Latency Under Node C(100K) = 12 (ms)
> [RESULT] Average Latency Under Node D(1M)   = 21 (ms)
> [RESULT] Average Latency Under Node E(10M)  = 21 (ms)
> [RESULT] Average Latency Under Node F(100M) = 16 (ms)
> [FIRST RUN] #TOTAL CALLS = 600 Total Average Latency = 16 (ms)
> ===
> == SECOND RUN TEST
> SUMMERY==
> [RESULT] Average Latency Under Node A(1K)   = 10 (ms)
> [RESULT] Average Latency Under Node B(10K)  = 15 (ms)
> [RESULT] Average Latency Under Node C(100K) = 14 (ms)
> [RESULT] Average Latency Under Node D(1M)   = 14 (ms)
> [RESULT] Average Latency Under Node E(10M)  = 11 (ms)
> [RESULT] Average Latency Under Node F(100M) = 14 (ms)
> [FIRST RUN] #TOTAL CALLS = 600 Total Average Latency = 13 (ms)
> ===
>
>
>
>
>
>
>
>
>
> On Thu, Aug 29, 2013 at 6:37 AM, Dishara Wijewardana (JIRA) > wrote:
>
>>
>>  [
>> https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>
>> Dishara Wijewardana updated SLING-3026:
>> ---
>>
>> Attachment: CassandraLatencyReport_V1.txt
>>
>> Here I am attaching the latest test results which includes latency to pull
>> data from a 10M and 100M collections.
>>
>> > Cassandra Resource Provider READ Latency Stats
>> > ---
>> >
>> > Key: SLING-3026
>> > URL: https://issues.apache.org/jira/browse/SLING-3026
>> > Project: Sling
>> >  Issue Type: Task
>> >Reporter: Dishara Wijewardana
>> >Priority: Critical
>> > Attachments: CassandraIntegrationTest.patch,
>> CassandraLatencyReport.txt, CassandraLatencyReport_V1.txt,
>> SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt,
>> SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png,
>> SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png
>> >
>> >
>> > This is to keep track on the statistics of the latency for the requests
>> done on Cassandra layer through Cassandra Resource Provider. Here we use
>> Apache Benchmark.
>> > We have a test profile java component in the cassandra module to add
>> bulk test data to cassandra.
>> > /content/cassandra/A/0   to /content/cassandra/A/999
>> > /content/cassandra/B/0   to /content/cassandra/B/
>> > /content/cassandra/C/0   to /content/cassandra/C/9
>> > /content/cassandra/D/0   to /content/cassandra/D/99
>> > And then this JIRA will keep track of reports on the http request time
>> to retrieve 1 node from each following data collection.
>> >
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA
>> administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>
>
>
> --
> Thanks
> /Dishara