Shortly after we released LucidWorks for Solr v.1.3_01 (see below), we found out that Apache Tomcat released a new minor version that fixes a security vulnerability. Our LucidWorks for Solr update v1.3_02 certified version now includes tomcat v6.0.20. Feel free to download it from our Downloads section; also, check out the update to Lucidworks for Lucene, out last week (see blog post).
The updated LucidWorks for Solr v1.3_01 change log
- Solrworks.sh script now use provided jvm
- Fixed a bug with windows folder names containing a space
- Includes LucidWorks for Lucene 2.4.1 version of Apache Lucene
- SOLR-1031: Fix XSS vulnerability in schema.jsp
- SOLR-1064: registry.jsp incorrectly displaying info for last core initialized regardless of what the current core is.
- SOLR-1072: absolute paths used in sharedLib attribute were incorrectly treated as relative paths.
- SOLR-1104: Fix some rounding errors in LukeRequestHandler’s histogram
- SOLR-1125: Use query analyzer rather than index analyzer for queryFieldType in QueryElevationComponent
- SOLR-929: LukeRequestHandler should return “dynamicBase” only if the field is dynamic.
- SOLR-532: WordDelimiterFilter now respects payloads and other attributes of the original Token by using Token.clone()
- SOLR-751: WordDelimiterFilter didn’t adjust the start offset of single tokens that started with delimiters, leading to incorrect highlighting.
- SOLR-1078: Fixes to WordDelimiterFilter to avoid splitting or dropping international non-letter characters such as non spacing marks.
- SOLR-876: WordDelimiterFilter now supports a splitOnNumerics option, as well as a list of protected terms.