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

[spring-projects-issues]

trafficstars

John Blum opened DATAGEODE-98 and commented

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

@Region("Books")
class Book {

    @Id
    private Long id;

    @Indexed
    private Author author;

    @LuceneIndexed
    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...

@SpringBootApplication
@ClientCacheApplication
@EnableEntityDefinedRegions(..)
@EnableIndexing
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: https://jira.spring.io/browse/DATAGEODE-99