Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8524847
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 11, 20262026-06-11T07:48:13+00:00 2026-06-11T07:48:13+00:00

On the documentation for Sunspot, it says: If you make a change to the

  • 0

On the documentation for Sunspot, it says:

If you make a change to the object’s “schema” (code in the searchable block), you must reindex all objects so the changes are reflected in Solr

What happens if this procedure isn’t followed?

Specifically, I have a fairly large index on Websolr, and if I just add a boolean field to it without reindexing, what will happen?

I’d like to be able to filter by true values of the boolean field, but I’ll never need to filter by false or nil values. Will this work, or must this admonition to reindex always be obeyed?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-11T07:48:15+00:00Added an answer on June 11, 2026 at 7:48 am

    In your case, if you add the field and do not index the data, it would still work.
    However, the existing data would not have a value for the field.
    Only the new documents inserted would have values for it.
    You can surely filter on the documents based on the values and the existing documents would have a nil value for the field.

    Usually it depends on what you change.

    You would not need a reindex in if you change query time analysis of a field type.
    A simple restart or core reload would work for you.

    Changes in schema would require a reindex of the collection, if you want the value of the field for all documents.
    If you change a field type, you would need to reindex the content as the analysis done at indexing time on the types of the field would be different.
    If you don’t reindex the Query time analysis performed for the field would be different from the one indexed and no matches would be found.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

The documentation for -hash says it must not change while a mutable object is
Documentation says: Changes to fields of the passed entities are not recognized by the
Documentation says: a configuration change (such as a change in screen orientation, language, input
Documentation: https://developers.facebook.com/docs/achievements/ Each achievement must possess a unique URL with the appropriate Open Graph
Documentation for data.xml/parse says The data is returned as defrecords and can be manipulated
Documentation says: The Grails team discourages the embedding of core application logic inside controllers,
Documentation says Dictionary keys order is unspecified. I guess it means the first added
The documentation for libev ( source ) says that: Kqueue deserves special mention, as
The documentation says: Sets the language used for database server warning or error messages.
The documentation says that camel-spring-ws(v2.7.1) officially supports spring-ws 1.5.9, but doesn't mention spring-ws 2.0.2.RELEASE.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.