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.

Sign up for GitHub

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

Jump to bottom

Issue if multiple search indexes defined for the same model #64

Closed
Folcon opened this issue Mar 5, 2015 · 1 comment
Closed

Issue if multiple search indexes defined for the same model #64

Folcon opened this issue Mar 5, 2015 · 1 comment
Assignees
@ChristopherRabotin
Labels
bug enhancement

Comments

@Folcon
Copy link
Contributor

Folcon commented Mar 5, 2015

If multiple search indexes defined for the same model, it arbitrarily picks one.

Present workaround requires creating an alias which explicitly sets the self.search_instance._index before returning the self.search_instance.
@ChristopherRabotin
Copy link
Owner

  • Allow ModelIndex instance to be marked as default. Multiple defaults should fail on initialization.
  • Add a post_save boolean returning function to check whether this content should be saved on the given index via this ModelIndex: allows for multiple indices to have partially different content.
  • Fix pre_delete function to warn in case of deletion of non-indexed item.

@ChristopherRabotin ChristopherRabotin self-assigned this Mar 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChristopherRabotin ChristopherRabotin

Labels
bug enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Folcon @ChristopherRabotin