Skip to content

DATAMONGO-1682 - Add support partialFilterExpression for reactive index creation. #474

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

Closed
wants to merge 3 commits into from

Conversation

christophstrobl
Copy link
Member

@christophstrobl christophstrobl commented Jun 23, 2017

We now support partial filter expression on indexes via Index.partial(…) on the reactive API. This allows to create partial indexes that only index the documents in a collection that meet a specified filter expression.

@christophstrobl christophstrobl changed the title DATAMONGO-1682 - Add support partialFilterExpression for reactive ind… … …ex creation. DATAMONGO-1682 - Add support partialFilterExpression for reactive index creation. Jun 23, 2017
@mp911de mp911de force-pushed the issue/DATAMONGO-1682 branch from fe1ab60 to e4a982a Compare July 5, 2017 08:40
christophstrobl and others added 3 commits July 13, 2017 15:43
…ex creation.

We now support partial filter expression on indexes via Index.partial(…) on the reactive API. This allows to create partial indexes that only index the documents in a collection that meet a specified filter expression.
Require non-null arguments in DefaultReactiveIndexOperations constructor. Remove superfluous publisher creation indirections. Use StepVerifier.verifyComplete() to verify the step sequence.

Use provided entity type in template API to construct index operations.
@mp911de mp911de force-pushed the issue/DATAMONGO-1682 branch from e4a982a to 477eac0 Compare July 13, 2017 13:52
mp911de pushed a commit that referenced this pull request Jul 13, 2017
…ex creation.

We now support partial filter expression on indexes via Index.partial(…) on the reactive API. This allows to create partial indexes that only index the documents in a collection that meet a specified filter expression.

Original pull request: #474.
mp911de added a commit that referenced this pull request Jul 13, 2017
Require non-null arguments in DefaultReactiveIndexOperations constructor. Remove superfluous publisher creation indirections. Use StepVerifier.verifyComplete() to verify the step sequence.

Use provided entity type in template API to construct index operations.

Original pull request: #474.
@mp911de
Copy link
Member

mp911de commented Jul 13, 2017

That's merged and polished.

@mp911de mp911de closed this Jul 13, 2017
@mp911de mp911de deleted the issue/DATAMONGO-1682 branch July 13, 2017 14:05
mp911de added a commit that referenced this pull request Jul 13, 2017
Require non-null arguments in DefaultReactiveIndexOperations constructor. Remove superfluous publisher creation indirections. Use StepVerifier.verifyComplete() to verify the step sequence.

Use provided entity type in template API to construct index operations.

Original pull request: #474.
@PARASRAUTELA
Copy link

@christophstrobl @mp911de I'm not able to find the usage for this. Can you help with a sample snippet on how to create partialFIlterExpression Index preferably with annotation? Quick googling around didn't help much.
Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants