There may also be a way to drop a bunch of fields on intake by crafting a
custom update request processor chain in solrconfig.xml.
Or by temporarily declaring them with stored=false, indexed=false in the
target schema.
As long as nothing actually ends up in Lucene segments, you can change
schema
Interestingly enough the next issue we hit is the `fl=750 fields` == too big,
so we switched to using POST/x-url-form-encoded for REINDEXCOLLECTION which
accepts the request, but then it silently fails (no logs in solr, just doesn't
work).
I can only assume this is because behind the scenes the
So for context we have 900x fields on Collection one and have removed some 250
fields from the schema and want to reindex into collection2. We're trying to
have a process where we can easily remove fields and reindex without too much
coding overhead. Therefore, we were simply using the default
>Surely this field should simply just be ignored?
why would solr ignore this field if you're trying to index to it? can't
you change your indexer to remove these fields as well? solr will try to
do what its told, and if its told to do something bad it will simply fail,
you dont want it to ignore
https://solr.apache.org/guide/8_8/collection-management.html#reindexcollection
See the "fl" param
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Mar 22, 2021 at 9:01 AM Karl Stoney
wrote:
> Hi,
> Sorry for all the questions recently…
>
> So
Hi,
Sorry for all the questions recently…
So as per https://solr.apache.org/guide/8_0/reindexing.html; we’re trying to
remove a load of fields. Subsequently we’ve created a new collection with the
new schema and we’re attempting to reindex from old to new.
There’s about 216 fields in total bein
