You are here

Home » API reference » Acquia Search for Search API 7.2

README.txt in Acquia Search for Search API 7.2 

Search API Acquia module
=========================

This module provides integration between your Drupal site and Acquia's
hosted search service. It requires the Acquia Connector module, a valid Acquia
subscription, and Search API Solr module.


Installation
--------------------------------------------------------------------------------

Consult the online documentation at https://docs.acquia.com/network/install for
installation instructions.

Notes on Acquia Search data protection and index auto-switching
--------------------------------------------------------------------------------

Search API Acquia module attempts to auto-detect your environment and automatically
connect to the best-fit Acquia Search index available. This is done to attempt
to protect your data in your production Solr instance; otherwise a development
site could easily overwrite or delete the data in your production index.

This functionality was previously available as a third-party module
https://www.drupal.org/project/acquia_search_multi_subs which will now become
deprecated.

Depending on the indexes already provisioned on your Acquia Subscription, the
module will follow these rules to connect to the proper index:

* If your site is running within Acquia Cloud, Search API Acquia will connect to
  the index name that matches the current environment (dev/stage/prod) and
  current multi-site instance.
* If the module can't find an appropriate index above, it will then enforce
  READ-ONLY mode on the production Solr index. This allows you to still test
  searching from any site while protecting your production, user-facing index.

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.  Please consult
our documentation at https://docs.acquia.com/acquia-search/multiple-cores to
find out more.

File

README.txt
View source 
  1. Search API Acquia module

  2. =========================

  3. 

  4. This module provides integration between your Drupal site and Acquia's

  5. hosted search service. It requires the Acquia Connector module, a valid Acquia

  6. subscription, and Search API Solr module.

  7. 

  8. 

  9. Installation

  10. --------------------------------------------------------------------------------

  11. 

  12. Consult the online documentation at https://docs.acquia.com/network/install for

  13. installation instructions.

  14. 

  15. Notes on Acquia Search data protection and index auto-switching

  16. --------------------------------------------------------------------------------

  17. 

  18. Search API Acquia module attempts to auto-detect your environment and automatically

  19. connect to the best-fit Acquia Search index available. This is done to attempt

  20. to protect your data in your production Solr instance; otherwise a development

  21. site could easily overwrite or delete the data in your production index.

  22. 

  23. This functionality was previously available as a third-party module

  24. https://www.drupal.org/project/acquia_search_multi_subs which will now become

  25. deprecated.

  26. 

  27. Depending on the indexes already provisioned on your Acquia Subscription, the

  28. module will follow these rules to connect to the proper index:

  29. 

  30. * If your site is running within Acquia Cloud, Search API Acquia will connect to

  31.   the index name that matches the current environment (dev/stage/prod) and

  32.   current multi-site instance.

  33. * If the module can't find an appropriate index above, it will then enforce

  34.   READ-ONLY mode on the production Solr index. This allows you to still test

  35.   searching from any site while protecting your production, user-facing index.

  36. 

  37. The current state is noted on the Drupal UI's general status report at

  38. /admin/reports/status, as well as when attempting to edit each connection.

  39. 

  40. You can override this behavior using code snippets or a Drupal variable. This,

  41. however, poses risks to your data that you should be aware of.  Please consult

  42. our documentation at https://docs.acquia.com/acquia-search/multiple-cores to

  43. find out more.

  44.