Skip to content

Enforce usage of Diff index #47

@kwin

Description

@kwin

The new index definition format outlined at https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/indexing#simplified-index-management-using-the-diff-index and https://jackrabbit.apache.org/oak/docs/query/indexing.html#diff-indexes is simpler to manage.

Also according to Adobe

Beginning September 2026, the old-style index management (full-copy naming convention) will be retired. Existing indexes that have already been deployed will continue to function, but you will no longer be able to deploy new versions using the old naming convention.

Therefore there should be a rule enforcing that. Seems this is also recommended for completely custom indexes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions