[MGNLEESOLR-103] create a SolrTemplatingFunctions Created: 17/Apr/16 Updated: 10/May/16 Resolved: 18/Apr/16 |
|
| Status: | Closed |
| Project: | Solr Search Provider |
| Component/s: | None |
| Affects Version/s: | 5.0.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Date of First Response: | |||||
| Description |
|
We need to implement a solr search functions class that is stateless and decoupled from any template implementation. I've created a module called magnolia-solr-search-tools (attached). It contains 3 classes:
SolrTemplatingFunctions is based on the SearchTemplatingFunctions and FacetedSolrSearchProvider. The problem with FacetedSolrSearchProvider is dependent on a templating model class. We need a way to perform search decoupled from a specific template implementation. That search function class should be stateless. SearchResultModel is based FacetedSearchResultModel but it's not required for the search. It showcases how to use the templating functions. |
| Comments |
| Comment by luis moreno [ 10/May/16 ] |
|
Hello, We would definitely like search templating functions for Solr. As of right it is a bit cumbersome to develop a multi language site with indexes for each language. It feels a bit like walking in the dark and we spend a lot of time in trial and error to get the desire outcome. Thanks, Luis Moreno |