README.txt in Acquia Search 3.x
Acquia Search Solr module
================================================================================
Provides integration between your Drupal site and Acquia's hosted search
service, Acquia Search [1]. Requires Search API Solr module.
[1] https://docs.acquia.com/acquia-search/
Notes on Acquia Search Solr data protection and core auto-switching
-------------------------------------------------------------------
Acquia Search Solr module attempts to auto-detect your environment and
automatically connect to the best-fit Acquia Search Solr core available. This is
done to attempt to protect your data in your production Solr instance.
Depending on the Solr cores already provisioned on your Acquia Subscription, the
module will follow these rules to connect to the proper core:
* If your site is running within Acquia Cloud, Acquia Search will connect to
the Solr core whose name matches the current environment (dev/stage/prod) and
current multi-site instance.
* If the module can't find an appropriate Solr core above, you then need to
configure a proper search core using settings below.
The current state is noted on the Drupal UI's general status report at
/admin/reports/status, as well as when attempting to edit each connection.
You can override this behavior using code snippets or a Drupal variable. This,
however, poses risks to your data that you should be aware of.
Hidden settings
----------------
- acquia_search.settings.read_only
Boolean value; if TRUE then there is enforcing of read-only mode.
Example settings.php override:
# $config['acquia_search.settings']['read_only'] = TRUE;
- acquia_search.settings.override_search_core
String that contains the ID of an Acquia Search core. When provided (and if
the core is available) this will force the connection to use that core
instead of letting the module auto-switch.
Valid use cases for setting this override is for testing locally, or
sharing the same Solr core amongst different Acquia sites/environments.
Here's an example for settings.php:
# Override Acquia Search Solr search core.
# $config['acquia_search.settings']['override_search_core'] =
'ABCD-12345.prod.mysite';
- acquia_search.settings.extract_query_handler_option
String that contains the extract query handler option. Default value is
"update/extract"'.
See SearchApiSolrSearchApiSolrAcquiaConnector::getExtractQuery() for details.
Here's an example for settings.php:
# Override Acquia Search Solr extract query handler option..
# $config['acquia_search.settings']['extract_query_handler_option'] =
# 'some/value';
File
README.txt
View source
- Acquia Search Solr module
- ================================================================================
-
- Provides integration between your Drupal site and Acquia's hosted search
- service, Acquia Search [1]. Requires Search API Solr module.
-
- [1] https://docs.acquia.com/acquia-search/
-
- Notes on Acquia Search Solr data protection and core auto-switching
- -------------------------------------------------------------------
-
- Acquia Search Solr module attempts to auto-detect your environment and
- automatically connect to the best-fit Acquia Search Solr core available. This is
- done to attempt to protect your data in your production Solr instance.
-
- Depending on the Solr cores already provisioned on your Acquia Subscription, the
- module will follow these rules to connect to the proper core:
-
- * If your site is running within Acquia Cloud, Acquia Search will connect to
- the Solr core whose name matches the current environment (dev/stage/prod) and
- current multi-site instance.
- * If the module can't find an appropriate Solr core above, you then need to
- configure a proper search core using settings below.
-
- The current state is noted on the Drupal UI's general status report at
- /admin/reports/status, as well as when attempting to edit each connection.
-
- You can override this behavior using code snippets or a Drupal variable. This,
- however, poses risks to your data that you should be aware of.
-
- Hidden settings
- ----------------
- - acquia_search.settings.read_only
- Boolean value; if TRUE then there is enforcing of read-only mode.
-
- Example settings.php override:
- # $config['acquia_search.settings']['read_only'] = TRUE;
-
- - acquia_search.settings.override_search_core
- String that contains the ID of an Acquia Search core. When provided (and if
- the core is available) this will force the connection to use that core
- instead of letting the module auto-switch.
- Valid use cases for setting this override is for testing locally, or
- sharing the same Solr core amongst different Acquia sites/environments.
-
- Here's an example for settings.php:
-
- # Override Acquia Search Solr search core.
- # $config['acquia_search.settings']['override_search_core'] =
- 'ABCD-12345.prod.mysite';
-
- - acquia_search.settings.extract_query_handler_option
- String that contains the extract query handler option. Default value is
- "update/extract"'.
- See SearchApiSolrSearchApiSolrAcquiaConnector::getExtractQuery() for details.
-
- Here's an example for settings.php:
-
- # Override Acquia Search Solr extract query handler option..
- # $config['acquia_search.settings']['extract_query_handler_option'] =
- # 'some/value';