[jira] [Created] (SLING-5432) Implement binaryless distribution
Marius Petria created SLING-5432: Summary: Implement binaryless distribution Key: SLING-5432 URL: https://issues.apache.org/jira/browse/SLING-5432 Project: Sling Issue Type: Improvement Components: Distribution Reporter: Marius Petria Fix For: Content Distribution Core 0.1.14 We should allow configuration of vault package builders not to include binaries using JCRVLT-97 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5431) PipeBinding NPE when evaluating null expression
Nicolas Peltier created SLING-5431: -- Summary: PipeBinding NPE when evaluating null expression Key: SLING-5431 URL: https://issues.apache.org/jira/browse/SLING-5431 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier PipeBindings should be able to evaluate null expressions or objects, and return null as value, right now it spits out a NPE. please find test & fix in the attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5428) Move MockSlingHttpServletRequest+Response to org.apache.sling.servlet-helpers
[ https://issues.apache.org/jira/browse/SLING-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101684#comment-15101684 ] Stefan Seifert commented on SLING-5428: --- documentation added by betrand: rev. 1724549 i added some further examples (derived from sling mocks docs): rev. 1724783 documentation: http://sling.apache.org/documentation/bundles/servlet-helpers.html > Move MockSlingHttpServletRequest+Response to org.apache.sling.servlet-helpers > - > > Key: SLING-5428 > URL: https://issues.apache.org/jira/browse/SLING-5428 > Project: Sling > Issue Type: New Feature > Components: Extensions, Testing >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Minor > Labels: mocks > Fix For: Testing Sling Mock 1.6.2, Servlet Helpers 1.0.0 > > > as discussed in the mailing list > http://apache-sling.73963.n3.nabble.com/Fake-request-response-classes-tt4057815.html > we want to move the mock SlingHttpServlerRequest+Response classes to a > separate bundle that can be used by sling mocks, but can be deployed to an > OSGi container as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5433: --- Attachment: SLING-5433.patch > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Request for release of commons testing
Hi, Would it be possible to release commons testing? In SLING-5341 we have updated the jackrabbit-core version which will allows us to use a new JackrabbitSession API method in SLING-4585. - Joel
[jira] [Updated] (SLING-5431) PipeBinding NPE when evaluating null expression
[ https://issues.apache.org/jira/browse/SLING-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5431: --- Attachment: SLING-5431.patch > PipeBinding NPE when evaluating null expression > --- > > Key: SLING-5431 > URL: https://issues.apache.org/jira/browse/SLING-5431 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5431.patch > > > PipeBindings should be able to evaluate null expressions or objects, and > return null as value, right now it spits out a NPE. > please find test & fix in the attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5371) Improving JcrInstaller's move listener registration
[ https://issues.apache.org/jira/browse/SLING-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101589#comment-15101589 ] Marc Pfaff commented on SLING-5371: --- [~cziegeler], [~bdelacretaz]: What do you think about the provided patches? Does that make sense to you? > Improving JcrInstaller's move listener registration > --- > > Key: SLING-5371 > URL: https://issues.apache.org/jira/browse/SLING-5371 > Project: Sling > Issue Type: Improvement > Components: Installer >Reporter: Marc Pfaff > Attachments: SLING_5371.patch, SLING_5371_jackrabbit.patch, > SLING_5371_jcr_only.patch > > > The JcrInstaller is currently registering a JCR listener for move events on > the root node with setting the 'deep' property to true. If it comes to > processing the underlaying Oak observation queue, this combination is very > inefficient, as it does not allow Oak to filter changes by path. > AFAIU this move listener is covering the use case where an installer artifact > is moved from/to an installer root folder. I therefore wanted to propose to > register the move listener on the configured root folders only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5433) WritePipe should remove a property when value is evaluated as null
Nicolas Peltier created SLING-5433: -- Summary: WritePipe should remove a property when value is evaluated as null Key: SLING-5433 URL: https://issues.apache.org/jira/browse/SLING-5433 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier it's not documented (will do), but a value evaluated as null in a write pipe conf should remove the property. It doesn't work right now as the target resource used for removal is the wrong one. failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE][RELEASE] Apache Sling Testing Utilities 2.0.24
On Fri, 2016-01-15 at 16:55 +0200, Robert Munteanu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101885#comment-15101885 ] Nicolas Peltier commented on SLING-5433: thx [~rombert], can you (quickly check) SLING-5431, as now i guess pipes tests are broken :-/ > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE][RELEASE] Apache Sling Testing Utilities 2.0.24
Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12334143 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1407 You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1407 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Robert
[jira] [Resolved] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5433. Resolution: Fixed Assignee: Robert Munteanu Fix Version/s: Pipes 1.0.0 Applied in https://svn.apache.org/r1724831, thanks for the contribution! > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Request for release of commons testing
Hi Joel, On Fri, 2016-01-15 at 13:27 +, Joel Richard wrote: > Hi, > > Would it be possible to release commons testing? > In SLING-5341 we have updated the jackrabbit-core version which will > allows us to use a new JackrabbitSession API method in SLING-4585. > > - Joel I'll prepare the release and start a release vote today. Robert
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101807#comment-15101807 ] Nicolas Peltier commented on SLING-5433: without SLING-5431, this patch will throw a NPE during test > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101940#comment-15101940 ] Nicolas Peltier commented on SLING-5433: thx [~rombert]! should have i done differently? > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: SLING-5434.patch > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: SLING-5434-DOC.patch also specified the fact you can use null in write pipe in the doc in the doc patch attached > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5434) WritePipe shoud remove properties at the very end
Nicolas Peltier created SLING-5434: -- Summary: WritePipe shoud remove properties at the very end Key: SLING-5434 URL: https://issues.apache.org/jira/browse/SLING-5434 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier in order to allow all expressions at current state to use the values of properties to be removed. test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-5431) PipeBinding NPE when evaluating null expression
[ https://issues.apache.org/jira/browse/SLING-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5431. Resolution: Fixed Assignee: Robert Munteanu Fix Version/s: Pipes 1.0.0 Fixed in https://svn.apache.org/r1724841 > PipeBinding NPE when evaluating null expression > --- > > Key: SLING-5431 > URL: https://issues.apache.org/jira/browse/SLING-5431 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5431.patch > > > PipeBindings should be able to evaluate null expressions or objects, and > return null as value, right now it spits out a NPE. > please find test & fix in the attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101924#comment-15101924 ] Robert Munteanu commented on SLING-5433: Oops, I thought the tests were already fixed by this patch. Applied patch from SLING-5431 just now. > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101976#comment-15101976 ] Robert Munteanu commented on SLING-5433: Nothing really, I just misread the comments :-) > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5435) Decouple processes that depend on cluster leader elections from the cluster leader elections.
Ian Boston created SLING-5435: - Summary: Decouple processes that depend on cluster leader elections from the cluster leader elections. Key: SLING-5435 URL: https://issues.apache.org/jira/browse/SLING-5435 Project: Sling Issue Type: Improvement Components: General Reporter: Ian Boston Currently there are many processes in Sling that must complete before a Sling Discovery cluster leader election is declared complete. These processes include things like transferring all Jobs from the old leader to the new leader and waiting for the data to appear visible on the new leader. This introduces an additional overhead to the leader election process which introduces a higher than desirable timeout for elections and heartbeat. This higher than desirable timeout precludes the use of more efficient election and distributed consensus algorithms as implemented in Etcd, Zookeeper or implementations of RAFT. If the election could be declared complete leaving individual components to manage their own post election operations (ie decoupling those processes from the election), then faster election or alternative Discovery implementations such as the one implemented on etcd could be used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
RE: [VOTE][RELEASE] Apache Sling Testing Utilities 2.0.24
+1
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: (was: SLING-5434.patch) > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: SLING-5434.patch > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103055#comment-15103055 ] Nicolas Peltier commented on SLING-5434: updated the patch with users-list feedback > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5430) Allow item move between distribution queues
Marius Petria created SLING-5430:
Summary: Allow item move between distribution queues
Key: SLING-5430
URL: https://issues.apache.org/jira/browse/SLING-5430
Project: Sling
Issue Type: Bug
Components: Distribution
Reporter: Marius Petria
Assignee: Marius Petria
Fix For: Content Distribution Core 0.1.14
{noformat}
POST /libs/.../agents/agentName/queues/queueName
operation=move=sourceQueueName=idsToMove
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SLING-5430) Allow item move between distribution queues
[
https://issues.apache.org/jira/browse/SLING-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria resolved SLING-5430.
--
Resolution: Fixed
Committed revision 1724744.
Also added retryQueue parameter for error queues.
> Allow item move between distribution queues
> ---
>
> Key: SLING-5430
> URL: https://issues.apache.org/jira/browse/SLING-5430
> Project: Sling
> Issue Type: Bug
> Components: Distribution
>Reporter: Marius Petria
>Assignee: Marius Petria
> Fix For: Content Distribution Core 0.1.14
>
>
> {noformat}
> POST /libs/.../agents/agentName/queues/queueName
> operation=move=sourceQueueName=idsToMove
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5410) Identify component where important Metrics can be collected
[ https://issues.apache.org/jira/browse/SLING-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101424#comment-15101424 ] Ian Boston commented on SLING-5410: --- imho Metrics data should be aggregated externally in systems like App Dynamics, Kibana, Splunk, New Relic, Ganglia. Aggregating the data on the cluster leader will obfuscate issues with individual instances. (and the cluster leader is not stable). > Identify component where important Metrics can be collected > --- > > Key: SLING-5410 > URL: https://issues.apache.org/jira/browse/SLING-5410 > Project: Sling > Issue Type: Task > Components: Engine >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > > With SLING-4080 we now have support for collecting various kinds of metrics > in performant way. > As a next step we would need to identify those parts of Sling engine and > request processing logic where we can collect important metrics. Such metric > should help > # Sling system administrator to monitor key aspects of Sling > # Allow us as developers to get insight into critical parts and help in doing > further optimization > Once identified we can then add required metric collection logic to those > parts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5410) Identify component where important Metrics can be collected
[ https://issues.apache.org/jira/browse/SLING-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101429#comment-15101429 ] Bertrand Delacretaz commented on SLING-5410: bq. Metrics data should be aggregated externally +1 > Identify component where important Metrics can be collected > --- > > Key: SLING-5410 > URL: https://issues.apache.org/jira/browse/SLING-5410 > Project: Sling > Issue Type: Task > Components: Engine >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > > With SLING-4080 we now have support for collecting various kinds of metrics > in performant way. > As a next step we would need to identify those parts of Sling engine and > request processing logic where we can collect important metrics. Such metric > should help > # Sling system administrator to monitor key aspects of Sling > # Allow us as developers to get insight into critical parts and help in doing > further optimization > Once identified we can then add required metric collection logic to those > parts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
