[jira] [Resolved] (SLING-12384) ResourceResolver: paged query for sling:alias will miss entries

[ https://issues.apache.org/jira/browse/SLING-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12384. Resolution: Fixed > ResourceResolver: paged query for sling:alias will miss entr

[jira] [Resolved] (SLING-12387) ResourceResolver: improve test coverage for PagedQueryIterator

[ https://issues.apache.org/jira/browse/SLING-12387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12387. Fix Version/s: Resource Resolver 1.12.0 Resolution: Fixed > ResourceResol

[jira] [Created] (SLING-12387) ResourceResolver: improve test coverage for PagedQueryIterator

Julian Reschke created SLING-12387: -- Summary: ResourceResolver: improve test coverage for PagedQueryIterator Key: SLING-12387 URL: https://issues.apache.org/jira/browse/SLING-12387 Project: Sling

[jira] [Created] (SLING-12386) ResourceResolver: is an empty string a valid sling:alias value

Julian Reschke created SLING-12386: -- Summary: ResourceResolver: is an empty string a valid sling:alias value Key: SLING-12386 URL: https://issues.apache.org/jira/browse/SLING-12386 Project: Sling

[jira] [Updated] (SLING-12384) ResourceResolver: paged query for sling:alias will miss entries

[ https://issues.apache.org/jira/browse/SLING-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12384: --- Description: Initially I thought that the issue just applies to empty alias values, because

[jira] [Updated] (SLING-12384) ResourceResolver: paged query for sling:alias will miss entries

[ https://issues.apache.org/jira/browse/SLING-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12384: --- Description: Initially I thought that the issue just applies to empty alias values, because

[jira] [Updated] (SLING-12384) ResourceResolver: paged query for sling:alias will miss entriesere 'first(sling:alias)' is empty

[ https://issues.apache.org/jira/browse/SLING-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12384: --- Summary: ResourceResolver: paged query for sling:alias will miss entriesere 'first

[jira] [Updated] (SLING-12384) ResourceResolver: paged query for sling:alias will miss entries

[ https://issues.apache.org/jira/browse/SLING-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12384: --- Summary: ResourceResolver: paged query for sling:alias will miss entries

[jira] [Resolved] (SLING-12383) ResourceResolver: potential NPE while processing aliases

[ https://issues.apache.org/jira/browse/SLING-12383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12383. Fix Version/s: Resource Resolver 1.12.0 Resolution: Fixed see https://github.com

[jira] [Updated] (SLING-12384) ResourceResolver: paged query for sling:alias will miss entries where 'first(sling:alias)' is empty

[ https://issues.apache.org/jira/browse/SLING-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12384: --- Summary: ResourceResolver: paged query for sling:alias will miss entries where 'first

[jira] [Created] (SLING-12384) ResourceResolver: paged query for sling:alias will miss entries where 'first(sing:alias)' is empty

Julian Reschke created SLING-12384: -- Summary: ResourceResolver: paged query for sling:alias will miss entries where 'first(sing:alias)' is empty Key: SLING-12384 URL: https://issues.apache.org/jira/browse/SLING

[jira] [Assigned] (SLING-12383) ResourceResolver: potential NPE while processing aliases

[ https://issues.apache.org/jira/browse/SLING-12383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-12383: -- Assignee: Julian Reschke > ResourceResolver: potential NPE while processing alia

[jira] [Created] (SLING-12383) ResourceResolver: potential NPE while processing aliases

Julian Reschke created SLING-12383: -- Summary: ResourceResolver: potential NPE while processing aliases Key: SLING-12383 URL: https://issues.apache.org/jira/browse/SLING-12383 Project: Sling

[jira] [Comment Edited] (SLING-11906) Migrate to slf4j 2.x

[ https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866418#comment-17866418 ] Julian Reschke edited comment on SLING-11906 at 7/16/24 2:36 PM: - FYI

[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

[ https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866418#comment-17866418 ] Julian Reschke commented on SLING-11906: FYI, from <https://www.slf4j.org/faq.h

[jira] [Commented] (SLING-12342) commons-log test ITPackagingData fails on Windows

[ https://issues.apache.org/jira/browse/SLING-12342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851063#comment-17851063 ] Julian Reschke commented on SLING-12342: I suspect that it has to do with using "/" a

[jira] [Created] (SLING-12342) commons-log test ITPackagingData fails on Windows

Julian Reschke created SLING-12342: -- Summary: commons-log test ITPackagingData fails on Windows Key: SLING-12342 URL: https://issues.apache.org/jira/browse/SLING-12342 Project: Sling Issue

[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

[ https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851052#comment-17851052 ] Julian Reschke commented on SLING-11906: FYI; removal of slf4j.event in Oak is in progress (see

[jira] [Commented] (SLING-12313) bump oak.version to 1.62.0 for compatibility

[ https://issues.apache.org/jira/browse/SLING-12313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846598#comment-17846598 ] Julian Reschke commented on SLING-12313: Oak and Jackrabbit dependencies should be in sync. Like

[jira] [Commented] (SLING-12266) Cache initial repository state to improve JCR_OAK performance

[ https://issues.apache.org/jira/browse/SLING-12266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836072#comment-17836072 ] Julian Reschke commented on SLING-12266: bq. there was some need form other sling modules

[jira] [Commented] (SLING-12266) Cache initial repository state to improve JCR_OAK performance

[ https://issues.apache.org/jira/browse/SLING-12266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836061#comment-17836061 ] Julian Reschke commented on SLING-12266: Yep - that's an unsupported version. Either use

[jira] [Commented] (SLING-12266) Cache initial repository state to improve JCR_OAK performance

[ https://issues.apache.org/jira/browse/SLING-12266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836055#comment-17836055 ] Julian Reschke commented on SLING-12266: AEM 6.5 should be on Oak 1.22.18 with the latest SP

[jira] [Commented] (SLING-12266) Cache initial repository state to improve JCR_OAK performance

[ https://issues.apache.org/jira/browse/SLING-12266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835795#comment-17835795 ] Julian Reschke commented on SLING-12266: I'm not an expert on mocking and Oak APIs, so I really

[jira] [Comment Edited] (SLING-12250) Adding Resource with sling:vanityPath set causes mismatch when resolving vanity URL (timing issue)

[ https://issues.apache.org/jira/browse/SLING-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820743#comment-17820743 ] Julian Reschke edited comment on SLING-12250 at 2/26/24 3:21 PM: - Well

[jira] [Commented] (SLING-12250) Adding Resource with sling:vanityPath set causes mismatch when resolving vanity URL (timing issue)

[ https://issues.apache.org/jira/browse/SLING-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820743#comment-17820743 ] Julian Reschke commented on SLING-12250: Well, it should resolve. If you have a repro test case

[jira] [Commented] (SLING-12250) Adding Resource with sling:vanityPath set causes mismatch when resolving vanity URL (timing issue)

[ https://issues.apache.org/jira/browse/SLING-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820732#comment-17820732 ] Julian Reschke commented on SLING-12250: AFAIU, the path should *always* resolve. If it does

[jira] [Commented] (SLING-12250) Adding Resource with sling:vanityPath set causes mismatch when resolving vanity URL (timing issue)

[ https://issues.apache.org/jira/browse/SLING-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817039#comment-17817039 ] Julian Reschke commented on SLING-12250: While the vanity path cache is populated, the resource

[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

[ https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810479#comment-17810479 ] Julian Reschke commented on SLING-11906: Awesome. Thanks. > Migrate to slf4j

[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

[ https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810475#comment-17810475 ] Julian Reschke commented on SLING-11906: [~kwin] - IIUC, Oak has similar problems wrt using SLF

Re: [RESULT] [VOTE] Release Apache Resource Resolver 1.11.6

On 23.01.2024 13:05, Konrad Windszus wrote: Done, please update the site accordingly. Thanks, Konrad Thanks Konrad, -> Best regards, Julian

Re: [RESULT] [VOTE] Release Apache Resource Resolver 1.11.6

On 22.01.2024 17:25, Julian Reschke wrote: On 22.01.2024 10:20, Julian Reschke wrote: On 17.01.2024 07:51, Julian Reschke wrote: ... Hi, The vote has passed with the following result : +1 (binding): Bertrand Delacretaz , Julian Reschke , Konrad Windszus , Robert Munteanu I will copy

Re: [RESULT] [VOTE] Release Apache Resource Resolver 1.11.6

On 22.01.2024 10:20, Julian Reschke wrote: On 17.01.2024 07:51, Julian Reschke wrote: ... Hi, The vote has passed with the following result : +1 (binding): Bertrand Delacretaz , Julian Reschke , Konrad Windszus , Robert Munteanu I will copy this release to the Sling dist directory

[RESULT] [VOTE] Release Apache Resource Resolver 1.11.6

On 17.01.2024 07:51, Julian Reschke wrote: ... Hi, The vote has passed with the following result : +1 (binding): Bertrand Delacretaz , Julian Reschke , Konrad Windszus , Robert Munteanu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven

Re: [VOTE] Release Apache Resource Resolver 1.11.6

On 20.01.2024 02:09, Eric Norman wrote: +0 for me. Though, I am still a little annoyed that you just ignored my review comments from https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/109#pullrequestreview-1791514750 Eric, FWIW: disagreeing is not the same thing as

Re: [VOTE] Release Apache Resource Resolver 1.11.6

On 17.01.2024 13:44, Bertrand Delacretaz wrote: [X ] +1 Approve the release Julian's signature 44F4797A52C336FA666CD9271DE461528F1F1B2A was missing from https://downloads.apache.org/sling/KEYS , I have added it [1] from [0], it should appear in a few minutes. ::: Ups. Thanks. Best

Re: Order of steps in https://sling.apache.org/documentation/development/release-management.html

On 17.01.2024 11:14, Carsten Ziegeler wrote: I think there is no perfect solution. We are operating this way for many years :) which of course doesn't mean there is no room for improvement. I think the scenario you describe happened at least once. but it was detected when the version was

Order of steps in https://sling.apache.org/documentation/development/release-management.html

Hi there, the "Release Management" document suggests adding a new (next) release should happen after the release vote, and that the release being voted on remains "unreleased" in the meantime. Doesn't that leave us with a time windos of 72h+ hours in which issue tracking in Jira will be

Re: [VOTE] Release Apache Resource Resolver 1.11.6

On 17.01.2024 07:51, Julian Reschke wrote: ... [X] +1 Approve the release Best regards, Julian

[VOTE] Release Apache Resource Resolver 1.11.6

Hi, We solved 6 issues in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353856=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2830 You can use this UNIX script to download the release and verify the

[jira] [Updated] (SLING-11511) Allow checking the map/resolve result for an empty path

[ https://issues.apache.org/jira/browse/SLING-11511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-11511: --- Fix Version/s: (was: Resource Resolver 1.11.6) > Allow checking the map/resolve res

[jira] [Updated] (SLING-11513) Allow impersonating an user when checking the result of a map/resolve call

[ https://issues.apache.org/jira/browse/SLING-11513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-11513: --- Fix Version/s: (was: Resource Resolver 1.11.6) > Allow impersonating an user w

[jira] [Resolved] (SLING-12222) MapEntries: Display the total number of loaded vanity urls / alias when loading is completed

[ https://issues.apache.org/jira/browse/SLING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-1. Fix Version/s: Resource Resolver 1.11.6 Resolution: Fixed > MapEntries: Disp

[jira] [Commented] (SLING-12222) MapEntries: Display the total number of loaded vanity urls / alias when loading is completed

[ https://issues.apache.org/jira/browse/SLING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807154#comment-17807154 ] Julian Reschke commented on SLING-1: https://github.com/apache/sling-org-apache-sling

Resource Resolver release

Hi, I'd like to cut 1.11.6 (https://issues.apache.org/jira/projects/SLING/versions/12353856) tomorrow. Robert: there are currently two in-progress issues assigned to you: can we move them to the next release? Note that I haven't done a SLING release before - I'm looking at

[jira] [Resolved] (SLING-12225) resource resolver: revise documentation and naming of system properties for query paging

[ https://issues.apache.org/jira/browse/SLING-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12225. Fix Version/s: Resource Resolver 1.11.6 Resolution: Fixed System properties

[jira] [Commented] (SLING-12222) MapEntries: Display the total number of loaded vanity urls / alias when loading is completed

[ https://issues.apache.org/jira/browse/SLING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805106#comment-17805106 ] Julian Reschke commented on SLING-1: sample output from PR'd resolver: {noformat

[jira] [Commented] (SLING-12225) resource resolver: revise documentation and naming of system properties for query paging

[ https://issues.apache.org/jira/browse/SLING-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804677#comment-17804677 ] Julian Reschke commented on SLING-12225: It was suggested by Thomas Müller while trying

[jira] [Updated] (SLING-12225) resource resolver: revise documentation and naming of system properties for query paging

[ https://issues.apache.org/jira/browse/SLING-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12225: --- Summary: resource resolver: revise documentation and naming of system properties for query

[jira] [Resolved] (SLING-11799) use keyset pagination for sling:alias query

[ https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-11799. Fix Version/s: Resource Resolver 1.11.6 Resolution: Fixed > use keyset paginat

[jira] [Updated] (SLING-12225) resource resolver: revise document and naming of system properties for paging

[ https://issues.apache.org/jira/browse/SLING-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12225: --- Description: See https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/111

[jira] [Created] (SLING-12225) resource resolver: revise document and naming of system properties for paging

Julian Reschke created SLING-12225: -- Summary: resource resolver: revise document and naming of system properties for paging Key: SLING-12225 URL: https://issues.apache.org/jira/browse/SLING-12225

[jira] [Commented] (SLING-12222) MapEntries: Display the total number of loaded vanity urls / alias when loading is completed

[ https://issues.apache.org/jira/browse/SLING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804344#comment-17804344 ] Julian Reschke commented on SLING-1: (and the same for aliases...) > MapEntries: Disp

[jira] [Assigned] (SLING-12222) MapEntries: Display the total number of loaded vanity urls / alias when loading is completed

[ https://issues.apache.org/jira/browse/SLING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-1: -- Assignee: Julian Reschke > MapEntries: Display the total number of loaded van

[jira] [Commented] (SLING-11799) use keyset pagination for sling:alias query

[ https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803164#comment-17803164 ] Julian Reschke commented on SLING-11799: [~thomasm] - that's what the PR imho does. >

[jira] [Updated] (SLING-12200) sling-org-apache-sling-graphql-core unnecessarily uses the shaded guava from graphql-java

[ https://issues.apache.org/jira/browse/SLING-12200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12200: --- Affects Version/s: GraphQL Core 0.0.26 > sling-org-apache-sling-graphql-core unnecessar

[jira] [Assigned] (SLING-12200) sling-org-apache-sling-graphql-core unnecessarily uses the shaded guava from graphql-java

[ https://issues.apache.org/jira/browse/SLING-12200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-12200: -- Assignee: Julian Reschke > sling-org-apache-sling-graphql-core unnecessarily u

[jira] [Resolved] (SLING-12205) ResourceResolver: switch sling:alias query to JCR-SQL2

[ https://issues.apache.org/jira/browse/SLING-12205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12205. Fix Version/s: Resource Resolver 1.11.6 Resolution: Fixed > ResourceResol

[jira] [Updated] (SLING-12205) ResourceResolver: switch sling:alias query to JCR-SQL2

[ https://issues.apache.org/jira/browse/SLING-12205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12205: --- Summary: ResourceResolver: switch sling:alias query to JCR-SQL2 (was: ResourceResolver

[jira] [Created] (SLING-12205) ResourceResolver: switch sling:alias query to JCR2

Julian Reschke created SLING-12205: -- Summary: ResourceResolver: switch sling:alias query to JCR2 Key: SLING-12205 URL: https://issues.apache.org/jira/browse/SLING-12205 Project: Sling Issue

[jira] [Resolved] (SLING-12204) ResourceResolver: refactor PagedQueryIterator for re-use

[ https://issues.apache.org/jira/browse/SLING-12204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12204. Fix Version/s: Resource Resolver 1.11.6 Resolution: Fixed > ResourceResol

[jira] [Updated] (SLING-12204) ResourceResolver: refactor PagedQueryIterator for re-use

[ https://issues.apache.org/jira/browse/SLING-12204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12204: --- Summary: ResourceResolver: refactor PagedQueryIterator for re-use (was: ResourceResolver

[jira] [Created] (SLING-12204) ResourceResolver: refactor PagedQUeryIterator for re-use

Julian Reschke created SLING-12204: -- Summary: ResourceResolver: refactor PagedQUeryIterator for re-use Key: SLING-12204 URL: https://issues.apache.org/jira/browse/SLING-12204 Project: Sling

[jira] [Assigned] (SLING-12161) sling-org-apache-sling-testing-sling-mock: update to latest Oak releases

[ https://issues.apache.org/jira/browse/SLING-12161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-12161: -- Assignee: Julian Reschke > sling-org-apache-sling-testing-sling-mock: upd

[jira] [Updated] (SLING-12161) sling-org-apache-sling-testing-sling-mock: update to latest Oak releases

[ https://issues.apache.org/jira/browse/SLING-12161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-12161: --- Summary: sling-org-apache-sling-testing-sling-mock: update to latest Oak releases

[jira] [Created] (SLING-12161) sling-org-apache-sling-testing-sling-mock: update to latest Oak maintenance release 1.22.17

Julian Reschke created SLING-12161: -- Summary: sling-org-apache-sling-testing-sling-mock: update to latest Oak maintenance release 1.22.17 Key: SLING-12161 URL: https://issues.apache.org/jira/browse/SLING-12161

[jira] [Commented] (SLING-12025) ResourceResolver: different mapping when optimizedAliasResolution enabled

[ https://issues.apache.org/jira/browse/SLING-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770368#comment-17770368 ] Julian Reschke commented on SLING-12025: bq. Actually, when checking closer, the aliasing

[jira] [Comment Edited] (SLING-12025) ResourceResolver: different mapping when optimizedAliasResolution enabled

[ https://issues.apache.org/jira/browse/SLING-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766203#comment-17766203 ] Julian Reschke edited comment on SLING-12025 at 9/18/23 6:57 AM: - I

[jira] [Commented] (SLING-12025) ResourceResolver: different mapping when optimizedAliasResolution enabled

[ https://issues.apache.org/jira/browse/SLING-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766203#comment-17766203 ] Julian Reschke commented on SLING-12025: I agree that the behaviour needs to be the same. I

[jira] [Resolved] (SLING-12020) resource resolver: alias metric has confusing name

[ https://issues.apache.org/jira/browse/SLING-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12020. Fix Version/s: Resource Resolver 1.10.2 Resolution: Fixed > resource resol

[jira] [Assigned] (SLING-12020) resource resolver: alias metric has confusing name

[ https://issues.apache.org/jira/browse/SLING-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-12020: -- Assignee: Julian Reschke > resource resolver: alias metric has confusing n

[jira] [Created] (SLING-12020) resource resolver: alias metric has confusing name

Julian Reschke created SLING-12020: -- Summary: resource resolver: alias metric has confusing name Key: SLING-12020 URL: https://issues.apache.org/jira/browse/SLING-12020 Project: Sling Issue

[jira] [Commented] (SLING-4228) Multi-value sling:alias property test fails (ResourceResolverTest)

[ https://issues.apache.org/jira/browse/SLING-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762697#comment-17762697 ] Julian Reschke commented on SLING-4228: --- Q: do we need insertion order or just stable ordering? (I

[jira] [Resolved] (SLING-12018) resource resolver: add metrics for resources with sling:alias/vanityPath found on startup

[ https://issues.apache.org/jira/browse/SLING-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12018. Resolution: Fixed > resource resolver: add metrics for resources with sling:al

[jira] [Created] (SLING-12018) resource resolver: add metrics for resources with sling:alias/vanityPath found on startup

Julian Reschke created SLING-12018: -- Summary: resource resolver: add metrics for resources with sling:alias/vanityPath found on startup Key: SLING-12018 URL: https://issues.apache.org/jira/browse/SLING-12018

[jira] [Resolved] (SLING-12017) resource resolver: add fallback when paged query fails due to missing index

[ https://issues.apache.org/jira/browse/SLING-12017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved SLING-12017. Resolution: Fixed > resource resolver: add fallback when paged query fails due to miss

[jira] [Created] (SLING-12017) resource resolver: add fallback when paged query fails due to missing index

Julian Reschke created SLING-12017: -- Summary: resource resolver: add fallback when paged query fails due to missing index Key: SLING-12017 URL: https://issues.apache.org/jira/browse/SLING-12017

[jira] [Assigned] (SLING-12017) resource resolver: add fallback when paged query fails due to missing index

[ https://issues.apache.org/jira/browse/SLING-12017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-12017: -- Assignee: Julian Reschke > resource resolver: add fallback when paged query fa

[jira] [Comment Edited] (SLING-11799) use keyset pagination for sling:alias query

[ https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760936#comment-17760936 ] Julian Reschke edited comment on SLING-11799 at 8/31/23 1:46 PM: - Turns

[jira] [Commented] (SLING-11799) use keyset pagination for sling:alias query

[ https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760936#comment-17760936 ] Julian Reschke commented on SLING-11799: Turns around that the number of distinct names

[jira] [Commented] (SLING-11799) use keyset pagination for sling:alias query

[ https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760896#comment-17760896 ] Julian Reschke commented on SLING-11799: I wonder whether it would be good to count the distinct

Re: [VOTE] Release Apache Sling Engine 2.15.4

On 29.07.2023 18:04, Carsten Ziegeler wrote: Hi, ... [X] +1 Approve the release Best regards, Julian

[jira] [Commented] (SLING-11980) log tracer relies on Guava (15)

[ https://issues.apache.org/jira/browse/SLING-11980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745619#comment-17745619 ] Julian Reschke commented on SLING-11980: If we can't replace and don't want to embed

[jira] [Commented] (SLING-11980) log tracer relies on Guava 15

[ https://issues.apache.org/jira/browse/SLING-11980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745617#comment-17745617 ] Julian Reschke commented on SLING-11980: I hear you :-). Replacing is a fine goal

[jira] [Updated] (SLING-11980) log tracer relies on Guava (15)

[ https://issues.apache.org/jira/browse/SLING-11980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-11980: --- Summary: log tracer relies on Guava (15) (was: log tracer relies on Guava 15) >

[jira] [Commented] (SLING-11980) log tracer relies on Guava 15

[ https://issues.apache.org/jira/browse/SLING-11980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745613#comment-17745613 ] Julian Reschke commented on SLING-11980: Note <https://github.com/apache/sling-org-apache-sl

[jira] [Created] (SLING-11980) log tracer relies on Guava 15

Julian Reschke created SLING-11980: -- Summary: log tracer relies on Guava 15 Key: SLING-11980 URL: https://issues.apache.org/jira/browse/SLING-11980 Project: Sling Issue Type: Improvement

[jira] [Commented] (SLING-11875) make sling event reproducible

[ https://issues.apache.org/jira/browse/SLING-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736035#comment-17736035 ] Julian Reschke commented on SLING-11875: FWIW, I didn't get any response. > make sling ev

[jira] [Updated] (SLING-11113) resource resolver: bloom filter might be out of sync on startup

[ https://issues.apache.org/jira/browse/SLING-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-3: --- Description: It appears that the bloom filter can be out of sync with the repo on startup

Re: SLING-11865 - Conversion fails when initial content document does not include namespace declaration

On 12.05.2023 15:48, Robert Munteanu wrote: On Mon, 2023-05-08 at 18:27 +0200, Konrad Windszus wrote: Another option would probably be to pass parameters to cp2fm for declaring additional namespaces. Then downstream consumers could declare additional ones like “cq” and those would have known

[jira] [Commented] (SLING-11865) Conversion fails when initial content document does not include namespace declaration

[ https://issues.apache.org/jira/browse/SLING-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720578#comment-17720578 ] Julian Reschke commented on SLING-11865: Understood. But I still think it would be good to have

[jira] [Commented] (SLING-11865) Conversion fails when initial content document does not include namespace declaration

[ https://issues.apache.org/jira/browse/SLING-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720571#comment-17720571 ] Julian Reschke commented on SLING-11865: FWIW, I would *expect* Oak's DocView import to fail

[jira] [Commented] (SLING-11861) ResourceMapper.getAllMappings returns empty mapping "" when a vanity paths is pathless url

[ https://issues.apache.org/jira/browse/SLING-11861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719715#comment-17719715 ] Julian Reschke commented on SLING-11861: Not convinced. This is a change in behavior that could

[jira] [Created] (SLING-11835) resource resolver: should not use SNAPSHOT version of API

Julian Reschke created SLING-11835: -- Summary: resource resolver: should not use SNAPSHOT version of API Key: SLING-11835 URL: https://issues.apache.org/jira/browse/SLING-11835 Project: Sling

[jira] [Updated] (SLING-11363) resource resolver: bloom filter incomplete when vanity path size limited

[ https://issues.apache.org/jira/browse/SLING-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-11363: --- Description: This was a problem before, but has become easier to reproduce after SLING

[jira] [Updated] (SLING-11800) resource resolver: optionally run initial alias query asynchronously

[ https://issues.apache.org/jira/browse/SLING-11800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-11800: --- Description: ...to avoid slow startup in presence of many alias resources. (add OSGi

[jira] [Assigned] (SLING-11800) resource resolver: optionally run initial alias query asynchronously

[ https://issues.apache.org/jira/browse/SLING-11800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-11800: -- Assignee: Julian Reschke (was: Carsten Ziegeler) > resource resolver: optiona

[jira] [Updated] (SLING-11800) resource resolver: optionally run initial alias query asynchronously

[ https://issues.apache.org/jira/browse/SLING-11800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-11800: --- Fix Version/s: (was: Resource Resolver 1.9.0) > resource resolver: optionally

[jira] [Created] (SLING-11800) resource resolver: optionally run initial alias query asynchronously

Julian Reschke created SLING-11800: -- Summary: resource resolver: optionally run initial alias query asynchronously Key: SLING-11800 URL: https://issues.apache.org/jira/browse/SLING-11800 Project

[jira] [Assigned] (SLING-11799) use keyset pagination for sling:alias query

[ https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned SLING-11799: -- Assignee: Julian Reschke > use keyset pagination for sling:alias qu

[jira] [Updated] (SLING-11799) use keyset pagination for sling:alias query

[ https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-11799: --- Description: Similar to what was done for vanity paths (SLING-11581), we should use keyset

  1   2   3   4   5   >