13.2. Annotation Configuration Support, refers to incorrect Indexing annotations [DATAGEODE-157]

[spring-projects-issues]

kohlmu-pivotal opened DATAGEODE-157 and commented

---

Affects: 2.0.12 (Kay SR12), 2.1.3 (Lovelace SR3), 2.2 M1 (Moore)

Backported to: 2.1.4 (Lovelace SR4), 2.0.13 (Kay SR13)

[spring-projects-issues]

John Blum commented

kohlmu-pivotal - Since you did not add a description to this improvement, I have no idea what problem you are specifically referring to in the SDG Reference Documentation, Session 13.2 - Annotation Configuration Support for Lucene Indexes.

In fact, the example code shown deliberately shows a combination of an OQL Index, on a Person's birthDate, along with Lucene Index on the Person's lastName.

@PartitionRegion("People")
class Person {

    Gender gender;

    @Index
    LocalDate birthDate;

    String firstName;

    @LuceneIndex;
    String lastName;

    ...
}

The documentation then goes on to describe how to enable this functionality, using both @EnableEntityDefinedRegions and @EnableIndexing.

@PeerCacheApplication
@EnableEntityDefinedRegions(..)
@EnableIndexing
class GeodeConfiguration { .. }

The @PartitionRegion mapping annotation was used on the Person entity class to reinforce the point that the Apache Geode cache Region on which the Lucene Index will be added must be a PARTITION Region.

There does not appear to be a problem in the documentation AFAICT.

Please reopen this JIRA ticket if I missed something.

Thanks