-
Bug
-
Resolution: Fixed
-
Major
-
4.1.0
-
None
-
4.1 M3
WIll unlikely cause some problem in project environnement.
But in dev environnement, when using ONE instance of Solr with multiple cores, it is very annoying;
Typical problem that occurs :
- Launch a global indexation on a Web application (Template Web for instance). Search is working properly.
- Then, switch to a CMS-only application (Template Data for instance). Search is working properly.
- Re-switch to the Web application (Template Web for instance). Launch a search. It causes an error like Error from server at http://localhost:8983/solr: undefined field site. I have to relauch a global indexation just because of the schema which was resent by CMS-only application.
It seems that schema is shared between all cores.
[CMS-8390] Solr schema is common to all cores
Simon Prieul (Inactive)
added a comment - To think about :
- duplicate ConfigSet before creating cores (in order to have a "template of configSet" named ametys-standard) ? with copy of files in a RequestHandler, to create for each core a different configSet named ametys-standard-prefix for instance
Simon Prieul (Inactive)
added a comment - To think about :
duplicate ConfigSet before creating cores (in order to have a "template of configSet" named ametys-standard ) ? with copy of files in a RequestHandler, to create for each core a different configSet named ametys-standard-prefix for instance
when done, do not forget to modify tests, when they create a core they will no longer set the configSet "ametys-standard"