You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've figured out a nice trick for defining indexes that span multiple databases (eg master+web, as in the "demo" index included with the source). You can use the "ref" feature to reference a location config twice and simply change the database reference, thus avoiding the need to redefine the field types, field crawlers, etc for each database:
The "ref" can point to anywhere in the config document, I just used a templates node as it seemed logical.
This isn't really a bug in the code, but it might help some folks. It could be used to refactor the demo config file's "demo" index to only need to define stuff once.
The text was updated successfully, but these errors were encountered:
Does anyone know if it is possible to do something similar to this (using "ref=...") for sections within the crawler config, such as the contents of ""? We have indexes that vary in their dynamic fields and included templates, but the base field types are all configured 100% the same, and it seems like a huge was to have to copy and maintain the fieldTypes and fieldCrawlers sections multiple times.
I've figured out a nice trick for defining indexes that span multiple databases (eg master+web, as in the "demo" index included with the source). You can use the "ref" feature to reference a location config twice and simply change the database reference, thus avoiding the need to redefine the field types, field crawlers, etc for each database:
The "ref" can point to anywhere in the config document, I just used a templates node as it seemed logical.
This isn't really a bug in the code, but it might help some folks. It could be used to refactor the demo config file's "demo" index to only need to define stuff once.
The text was updated successfully, but these errors were encountered: