Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent Lucene Indexes from being created client-side when using the @LuceneIndexed annotation with @EnableIndexing [DATAGEODE-98] #143

spring-projects-issues opened this issue Apr 14, 2018 · 0 comments
in: configuration in: search type: bug


Copy link

@spring-projects-issues spring-projects-issues commented Apr 14, 2018

John Blum opened DATAGEODE-98 and commented

This is particularly a problem for application clients that define an application domain model type, like so...

class Book {

    private Long id;

    private Author author;

    private String title;

Where the Book's title field/property has been annotated with SDG's @LuceneIndexed annotation.

SDG goes onto try and create a Lucene Index, even for cache clients when the application is annotated like so...

class ExampleApplication { .. }

This particular configuration arrangement (with @EnableIndexing) is useful since OQL Indexes can be applied to client Regions, especially LOCAL or CACHING_PROXY Regions. @EnableIndexing also has the added benefit that when used with the @EnableClusterConfiguration annotation, the configuration on the client will be pushed to the servers, which is when/why the @LuceneIndexed application domain model object fields/properties are important

Affects: 2.0.6 (Kay SR6), 2.1 M2 (Lovelace)

Reference URL:

@spring-projects-issues spring-projects-issues added type: bug in: configuration in: search labels Dec 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: configuration in: search type: bug
None yet

No branches or pull requests

2 participants