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

HSEARCH-2715 Mention in the documentation *when* a full reindex may be necessary #1399

Closed
wants to merge 1 commit into from

Conversation

yrodiere
Copy link
Member

If you change the entity mapping to the index, chances are that the whole Index needs to be updated;
For example if you decide to index a an existing field using a different analyzer you'll need to
If you change the entity mapping to the index, chances are that the whole index needs to be updated;
for example if you decide to index a an existing field using a different analyzer you'll need to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/a an/an/

* Rebuilding the whole index is *not* required if all you did was:
** *adding* new indexes/fields that will be empty for all currently persisted entities,
e.g. adding a new property on an entity type and mapping it to a field,
but with the guarantee that this property will initially be null for every instance of this entity;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be nice to explicitly add the case when you add new entities.

@yrodiere
Copy link
Member Author

@gsmet Right. I amended my commit.

@gsmet
Copy link
Member

gsmet commented May 12, 2017

Rebased and merged. Thanks.

@gsmet gsmet closed this May 12, 2017
@yrodiere yrodiere deleted the HSEARCH-2715 branch May 12, 2017 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants