![]() The Query class does multiple things: Build the query, initialize the query from the configuration,… This could be split into multiple components. ![]() TYPO3 specific logic and common Apache Solr logic is mixed and makes it hard to switch to frameworks like e.g.It is hard to integrate new features (e.g the tiebreaker or bigram features).The corresponding parts in the code especially the Query class had grown over time and reached a huge complexity. Many parts of the code of EXT:solr deal with queries for Apache Solr that’s no surprise :). Fluent API for Queries with the QueryBuilderįluent API for Queries with the QueryBuilder ¶.Phrase support (phrase, bigram, trigram).Use TYPO3 Guzzle for page index requests.But in most cases only a subset of the entire Solr API is accessible so it might lead to error messages or warnings, for example in the Drupal status report page. Some of the Solr hosting services above could be leveraged using the default connectors this module provides. If you want your Solr hosting service to be listed here, please contact drunken monkey or mkalkbrenner.) (This is a free information service, We do not endorse any of these products. If you do not want to or cannot install your own Solr server, there are a number of web Solr hosts which are more or less compatible with the Search API (either because they have it as an option, or they allow uploading custom configurations). An Apache Solr server which can be individually configured (or has a configuration compatible with this module).The PR on github will automatically tested by travis or github actions and the test results willīe reflected in the PR conversation. add a link to the github PR to the issue.apply your patch and file a PR on github.upload the patch for being reviewed to that issue on as usual.Therefore we leverage travis and github actions for our tests and had to establish a more complex workflow: Requirement can't be provided by the test infrastructure. Our test suite includes integration tests that require a real Solr server. Such issues are only handled in the 4.x branches. ![]() There are open "issues" which are in fact new features or configuration options. The 7.x-1x branch is considered feature complete and only gets critical bug or security fixes. ![]() There is no support for Solr 8 as of yet. Solr 7 support is currently only working by using the Lucene 6 compatibility mode ( luceneMatchVersion=6.0), though. The Drupal 7 version of this module attempts to support all Solr versions starting at Solr 3.5, though you should be aware that all versions before Solr 7.7 have reached end-of-life (EOL) already and using them is strongly discouraged. Important: You have to use composer to install the module! Otherwise the dependencies won't be resolved and the autoloader isn't configured correctly.Įnsure to read README.md before you start! 7.x-1.x version That reduced the code base and improved the performance. In 4.2 there's only one unified backend for all purposes. The 4.2 release of this module is works for Drupal 9 and 10! And it supports a wide range of Solr versions from 3.6 to 8.Įarlier versions provided dedicated backends for special puproses, like the multilingual or the "any schema" backends. (4) supported via the search_api_solr_legacy sub-module and a Solr 5.x config-setĪccording to any Solr version before 7.7 reached "End of Life". (3) supported via the search_api_solr_legacy sub-module (1) running in Solr 6 backward compatibility mode Solr and module versions compatibility matrix for Drupal 8 and 9 Multilingual content is handled correctly by design. It provides a great performance, and is suitable even for use on large commercial websites and supports facets and multi-index searches. This module provides a Apache Solr backend for the Search API module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |