Rapidly get up and running with a fully featured, SEO friendly, keyword searchable, faceted search engine with an in-built, example search page to test it all out.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# __ #
# .-----.-----.| |.----. #
# |__ --| _ || || _| #
# |_.-----.-----.--.--| | #
# | _ | _ | | | #
# | __|___._|__|__|__| #
# |__| ... .-.. #
# #
# ~ ~ ~ * ~ ~ ~ #
# #
# #
# SOLR/PANL #
# #
# --------- #
# #
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
Build and test 'main' branch:
(courtesy of Circle-CI)
Panl is designed to be a drop in replacement for your current version. Keep note of any breaking release, although backwards compatibility is always high on the list of features.
Your existing configuration files should just work with the downloaded release package.
- Online book (HTML): https://synapticloop.github.io/panl/
- Offline book (PDF): Getting Started With Synapticloop Panl.pdf
Both of the book links above refer to Solr Panl integration 9 with instructions for setting up and running earlier versions of Solr.
Because...
/Caran+d'Ache/true/Black/bDW/
looks A LOT nicer than
q=*:*&facet.mincount=1&rows=10&facet.field=lead_size_indicator&facet.field=grip_material&facet.field=colours&facet.field=nib_shape&facet.field=diameter&facet.field=cap_shape&facet.field=brand&facet.field=mechanism_type&facet.field=length&facet.field=hardness_indicator&facet.field=grip_type&facet.field=cap_material&facet.field=lead_grade_indicator&facet.field=tubing_material&facet.field=in_built_sharpener&facet.field=disassemble&facet.field=category&facet.field=body_shape&facet.field=clip_material&facet.field=mechanism_material&facet.field=lead_length&facet.field=body_material&facet.field=in_built_eraser&facet.field=grip_shape&facet.field=relative_weight&facet.field=name&facet.field=nib_material&facet.field=weight&facet.field=variants&facet=true&fq=brand:"Caran+d'Ache"&fq=disassemble:"true"&fq=colours:"Black"&q.op=AND
Panl was designed to convert rather long and unfriendly (both in human readable and SEO terms) to shorter, nicer, and friendlier URL paths throughout the entire search journey.
Working with a Solr schema, the Panl configuration files translate unwieldy URL parameters into concise and precise URL paths.
-
Have SEO friendlier URL paths with much shorter URLs than traditional query parameters - This was the primary driver and the base functionality.
-
Abstract away the complexities of the Solr query string - Being able to have a simple interface through the URL which could generate complex queries. Not having to fully understand how Solr works in the back-end abstracts away the complexity of a front-end integrator and reduces the need to have the back-end and front-end understand each-other.
-
Be quick to start up and easy to configure - During development of a solution, being able to iterate over a solution, or change the way that Panl is configured is a must have. Additionally, being able to upgrade the Panl server and have the configuration files be automatically picked up and work without any changes is a plus.
-
Protect Solr from errant queries - Hiding the Solr implementation details from the end user and parsing, decoding, and validating the URL before passing the query through to Solr. Additionally, Solr has a tendency to return an internal server error when the query string is not as it expected, and this should not disturb the return of the results.
-
Be able to present the same Solr collection in multiple different ways - A single Solr collection should be able to serve up different fields and facets from the result documents without any back-end logic.
-
Have a configuration file drive the generation of the UI as much as possible - Rather than hard-coding facets and then determining how to display them, being able to have a returned JSON response which can be interrogated to determine how the facets should be displayed.
-
MULTIPLE ways to 'SLICE and DICE' - From one Solr collection, the Panl server can present the results and facets in multiple different ways, providing individual use cases for specific needs.
-
PREFIXES and SUFFIXES - Panl can also add prefixes and suffixes to the URI path to increase readability, for example, with configuration. For the example LPSE URI path of
/Caran+d'Ache/true/Black/bDW/
could also have the brand Solr field prefixed with ‘Manufactured By ’ and suffixed by ‘ Company’ to produce the URI path/Manufactured+By+The+Caran+d'Ache+Company/true/Black/bDW/
-
BOOLEAN value translations, for any Solr field that is defined as a
solr.BoolField
, then an additional translation can be performed. ‘True’ and ‘false’ values can be replaced with arbitrary text, which will be transparently converted between Panl and Solr. For the LPSE URI path of/Caran+d'Ache/true/Black/bDW/
the true value (which is defined as whether the mechanical pencil can be disassembled could be changed to ‘Able to be disassembled’ for true values, and ‘Cannot be disassembled’ for false values. The above URI path would then become/Caran+d'Ache/Able+to+be+disassembled/Black/bDW/
-
FIELD VALUE validation - By default, Solr can error when an invalid value is passed through - for example, if Solr is expecting a numeric value and it could not be parsed. Panl can protect against this, by attempting to parse the value as best it can, and silently dropping the parameter if it cannot be sensibly parsed.
-
HIERARCHICAL facets - Only show facets if a parent facet is currently selected, allowing you to narrow down the facet results and lead users through the search journey.
-
SORTED facets - Each individual facet can be sorted by either the facet count (which is the default), or the facet value (e.g. alphabetic/numeric)
-
MORE facets - Request more facets where the number of facets return does not contain the full set.
-
RESULTS SORTING options - Sort by any of the Solr fields, either ascending, or descending and with multiple sub-sorting available - e.g. sorting by a brand name, than the model number
-
PAGINATION - All the data to easily generate pagination URL paths giving you options and control over your own implementation.
-
STATIC SITE GENERATION - With the exception of a query parameter, all available links for every conceivable URI path can be statically generated ahead of time, with canonical URLs.
-
STATELESS - No state is stored in the Panl server, all of the state is from the URL path part that is passed through. No sessions, no memory, nothing to backup, easy to update and quick to start and restart.
The Solr Panl release package was designed to get you up and running as quickly as possible.
With the in-built tool, point it at your existing Solr managed-schema.xml
file, run the Panl server and view the results. From there you can tweak the configuration, generate new configurations and see your results in an instant.
Image: The features and functionality of the Panl server
The image is a screenshot of the in-built Panl Results Viewer Web App available in the release package, and whilst not intended as a production search page, can be used to fine-tune the configuration, or just to have a quick overview of the results.
-
A list of available Collections and FieldSet URI Paths (CaFUPs) that Panl is configured to serve. CaFUPs enable different Solr fields to be returned in the documents with the same search parameters.
-
A textual representation of the CaFUPs that the Panl Results Viewer web app is using.
-
The canonical URI path (which is returned with the Panl results JSON object) - this is important as multiple Panl LPSE URI paths will return exactly the same results - this is the unique URI path for this result set and necessary for de-duplicating the search engine results. This also includes a link to the Panl Results Explainer web app.
-
The search query box, by default, Panl responds to the same parameter name as The Solr server - i.e. 'q'. This can be configured to be a different value should you choose.
-
Active filters - either queries, selected facets, or sorting options that are currently limiting the results - the [Remove] link is the URI path that will remove this query, facet, or sorting option from the results. If it is an active sorting filter, the [Change to DESC] or [Change to ASC] links will invert the sorting order without affecting any further sub-ordering.
-
Range filters - for facets that are defined as ranges - allowing end-users to select a range of values - the values are inclusive (i.e. include the minimum and maximum values).
Date Range filters (not shown) - Enabling searching on a range of dates (but not a specific date) in the form of: next/previous <any_integer> hours/days/months/years.
- For example:
- Last 30 days
- Previous 24 hours
-
Available filters - additional facets that can further refine and limit the Solr search results.
-
Number of results found, and whether this is an exact match.
-
Query operand - whether the query is OR, or AND, this affects the search query, not the faceting - i.e. the Solr server q.op parameter.
-
Page information, the number of pages, how many results are shown per page, and how many results are shown on this page.
-
Sorting options - Whether to sort by relevance (the default) or by other configured sorting options with ascending and descending options available. Any Solr field can be configured to be used as a sorting option. And multi-sort orders are available, allowing sorting on more than one field.
-
Pagination options - the Panl server returns all information needed to build a pagination system, number of results, number of results shown per page and the current page number.
-
Number of results per page. Note: The values 3,5,10 are just examples - this can be set to any positive integer number.
-
Timing information about how long the Panl server took to build and return the results (including how much time the Solr server took to find and return the results).
-
The results - the fields that are returned with the documents and are shown in the results sections which are configured by the CaFUPs. Multiple field sets can be configured for the collection.
Image: The features and functionality of the Panl results explainer
The image is a screenshot of the in-built Panl Results Explainer Web App available in the release package, and whilst not intended as a production search page, can be used to look into, troubleshoot, and fine-tune the configuration.
- A list of available Collections and FieldSet URI Paths (CaFUPs) that Panl is configured to serve. CaFUPs enable different Solr fields to be returned in the documents with the same search parameters.
- A textual representation of the CaFUPs that the Panl Results Viewer web app is using.
- The canonical URI path entry field allows you to enter any canonical URI path and have the parsing and tokenising explained to you, including whether the parsed token was valid, the LPSE code found and the original value that Panl attempted to decode.
- The request token explainer - for any canonical URI entered, this will list the parsing and decoding steps, with the following details
- Whether the token is valid (if it is invalid, it will be ignored and not passed through to the Solr search server),
- The type of token that was found,
- The LPSE code,
- The parsed value,
- The original value, and
- Where pertinent, additional information pertaining to the specific code.
- Configuration parameters - parameters that are not fields or facets with information about the value, a description, and the property that set the value.
- Field configuration explainer - for each of the fields or facets that are configured in the LPSE order an explanation of their configuration including:
- The type of Java field type,
- The LPSE code,
- The Solr field name,
- The Solr field type, the Panl field name, and
- Additional configuration items which may include Prefixes, Suffixes, Ranges, Facet type, or Minimum/maximum values
- Any configuration warning messages that were found whilst parsing the properties files.
Image: The In-Built Panl Single Page Search Web Application
Panl also ships with a URL that will provide a separate JSON response, allowing you to build a single page search interface, giving your users all the options at a glance.
- A list of available Collections URI Paths for each available single page search interface.
- The generated Panl LPSE path from the selections.
- All the facets and the facet values that can be selected.
- The generated Panl LPSE path from the selections.
- A search button that will take you the in-built Panl Results Viewer web app so that you can view the results instantly.
At the end of this chapter, you will have a web page up and running with the mechanical-pencils collection indexed and ready to sort and facet on the URL: http://localhost:8181/panl-results-viewer/
Image: The In-Built Panl Results Viewer Web Application
Download the latest release of Synapticloop Panl
https://github.com/synapticloop/panl/releases
Download the latest version of Apache Solr - this book is using the 9.6.1-slim
version
https://solr.apache.org/downloads.html
A Note On Running The Commands
These are the commands for either Microsoft Windows or NIX operating systems (Linux/Apple Macintosh). Should there be any errors - see the ‘Getting Started’ section for a more in-depth explanation and approach.
WARNING: The Solr Release version
9.7.0
has changed the options for creating a new example cloud. The command line option has changed from-noprompt
to--no-prompt
All other commands remain the same
**IMPORTANT**: You will need to replace the
SOLR_INSTALL_DIRECTORY
and
PANL_INSTALL_DIRECTORY
references in the commands for your particular setup.
**IMPORTANT**: Each of the commands - either Windows or *NIX must be run on a
single line - watch out for continuations.
This requires no interaction, will use the default setup, two replicas, and two shards under the 'example' cloud node. Command(s)
cd SOLR_INSTALL_DIRECTORY
bin\solr start -e cloud -noprompt
This will set up the mechanical pencil collection and schema so that the data can be indexed. Command(s)
cd SOLR_INSTALL_DIRECTORY
bin\solr create -c mechanical-pencils -d PANL_INSTALL_DIRECTORY\sample\solr\mechanical-pencils\ -s 2 -rf 2
This will index all mechanical pencil data into the Solr instance. Command(s)
cd SOLR_INSTALL_DIRECTORY
bin\solr post -c mechanical-pencils PANL_INSTALL_DIRECTORY\sample\data\mechanical-pencils.json
This will start the server and be ready to accept requests. Command(s)
cd PANL_INSTALL_DIRECTORY
bin\panl.bat -properties PANL_INSTALL_DIRECTORY\sample\panl\mechanical-properties\panl.properties
Open http://localhost:8181/panl-results-viewer/ in your favourite browser.
Choose a collection/fieldset and search, facet, sort, paginate and view the results
**IMPORTANT**: Each of the commands - either Windows or *NIX must be run on
a single line - watch out for continuations.
No prompting, default setup, two replicas, and two shards under the 'example' cloud node. Command(s)
cd SOLR_INSTALL_DIRECTORY
bin/solr start -e cloud -noprompt
Set up the schema so that the data can be indexed. Command(s)
cd SOLR_INSTALL_DIRECTORY
bin/solr create -c mechanical-pencils -d PANL_INSTALL_DIRECTORY/sample/solr/mechanical-pencils/ -s 2 -rf 2
Index all of the data into the Solr instance Command(s)
cd SOLR_INSTALL_DIRECTORY
bin/solr post -c mechanical-pencils PANL_INSTALL_DIRECTORY/sample/data/mechanical-pencils.json
Ready to go. Command(s)
cd PANL_INSTALL_DIRECTORY
bin/panl -properties PANL_INSTALL_DIRECTORY/sample/panl/mechanical-properties/panl.properties
View the in-built Panl Results Viewer web application
Open http://localhost:8181/panl-results-viewer/ in your favourite browser.
Choose a collection/fieldset and search, facet, sort, paginate and view the results
WARNING: The Solr Release version
9.7.0
has changed the options for starting a new example cloud. The command line option has changed from-cloud
to--cloud
All other commands remain the same - For versions greater than
9.7.0
they have re-added the-cloud
option
If you have stopped the example Solr server, starting it up:
cd SOLR_INSTALL_DIRECTORY
bin\solr start -cloud -p 8983 -s "example\cloud\node1\solr"
bin\solr start -cloud -p 7574 -s "example\cloud\node2\solr" -z localhost:9983
cd SOLR_INSTALL_DIRECTORY
bin/solr start -cloud -p 8983 -s "example/cloud/node1/solr"
bin/solr start -cloud -p 7574 -s "example/cloud/node2/solr" -z localhost:9983
gradlew.bat assemble
./gradlew assemble
The distributions (both a .zip
and a .tar
file) will be created in the build distributions directory.
I.e.
./build/distributions
(*NIX), or.\build\distributions
(Windows)
with the release files named solr-panl-9-x.x.x
where x.x.x
is the version number.
-
Bug fixes
- Fixed JavScript in Single Page Search results in-built web app to take into account range facets
- Fixed serving in-built panl testing URLs when run from the script
-
Code changes
- Retrieval of more facets functionality added:
- Added in
facet_limit
JSON key for retrieving more facet results - Added in handler for retrieving more facets for a specific search field
- Added in
- Better output for testing URLs
- Added Always on OR facets and
panl.or.always.<lpse_code>
property - Moved log4j out of the jar file so that user's con configure their own logging
- Retrieval of more facets functionality added:
-
Breaking Changes - (which is OK as nobody is using it at the moment :) )
- Changed the single page search URL binding from
/panl-configuration/
to/panl-single-page/
as it makes more sense
- Changed the single page search URL binding from
-
Documentation update
- General spelling and grammatical mistake updates
- Update to new functionality and configuration properties
- Added in the
pagination
returned JSON Object implementation details - Added in URLs bound by the Panl server in the Appendices
View the code for this release
-
Bug fixes
- Fixed 'OR' facet
before
andafter
URL values in the JSON response where a range facet has already been selected
- Fixed 'OR' facet
-
Code cleanup
- Updated explanation for DATE Range and RANGE facets
View the code for this release
-
Added in
empty
FieldSet to return no documents -
Added in Single Search Page functionality
-
Update Mechanical Pencils
- Added in hierarchy for the Pencil Model example
-
Dynamic range functionality - pulling actual values for the facet
-
Suppress facet values for ranges, so that the user may only select from the range UI, and the individual range facet values do not appear
-
Documentation update
- New documentation for additional features and functionality
- Fixed general spelling and grammar errors
- Updated mechanical pencils introductory dataset explanations
- Added in documentation for Fields
- Panl cookbook
View the code for this release
- Initial release with base functionality