Solr Schema界面中Schema、Index与Properties的区别及Indexed状态不一致的含义
Hey there! Let's break down these three key sections in Solr's Schema UI clearly, and tackle that specific field configuration scenario you're asking about.
1. Core Differences Between Schema, Index, and Properties
Schema Section
This is the global definition layer for your fields. Think of it as setting the "default blueprint" for a field: you define its data type (like string, text_general, or int), default behavior for storing values, default indexing status, and other base rules. Any new Solr core/collection you create will inherit these settings automatically—this is the baseline configuration that applies everywhere unless overridden.
Index Section
This is the per-core/collection customization layer. Solr lets you have multiple independent indexes (cores or collections) sharing the same base Schema, and this section lets you tweak field settings for the specific index you're currently working on. Its settings take priority over the Schema's defaults. For example, if a field is set to be indexed in Schema, you can turn that off just for this one index here.
Properties Section
This is the metadata and auxiliary configuration layer. It doesn't directly control whether a field is stored or indexed—instead, it holds extra details like field descriptions, whether it's a dynamic field, visibility settings, and extended parameters (like sorting or faceting preferences). Think of it as adding extra context and optional behaviors to the field, rather than defining its core function.
2. What Does It Mean When a Field's "Indexed" Is Checked in Schema but Unchecked in Index?
This is a classic case of global default vs. per-index override:
- The Schema's checked "Indexed" means that by default, every new core/collection will index this field (making its content searchable).
- The Index's unchecked "Indexed" is a deliberate override for the specific core/collection you're viewing. It tells Solr: "Ignore the Schema default for this index—don't build a searchable index structure for this field here."
- The end result? This field will be searchable in all other cores/collections that use the default Schema settings, but in this specific index, even if you populate the field with data, you won't be able to search using its values (since no index was built for it).
内容的提问来源于stack exchange，提问作者raj247
