Collective.solr

Latest version: v9.3.0

Safety actively analyzes 628477 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 8

2.0

----------------

* Updated readme and project description, adding detailed information about how
Solr works and how we integrate with it.
[hannosch]

2.0b2

------------------

* Added optional support for the `Lazy` backports founds in catalogqueryplan.
[hannosch]

* Fixed patch of LazyCat's `__add__` method to patch the base class instead, as
the method was moved.
[hannosch]

* Updated test config to Solr 3.1, which should be supported but hasn't seen
extensive production use.
[hannosch]

* Avoid using the deprecated `five:implements` directive.
[hannosch]

2.0b1

------------------

* Rewrite the `isSimpleSearch` function to use a less complex regular
expression, which doesn't have O(2**n) scaling properties.
[hannosch]

* Use the standard libraries doctest module.
[hannosch]

* Fix the pretty_title_or_id method from PloneFlare; the implementation
was broken, now delegates to the standard Plone implementation.
[mj]

2.0a3

------------------

* In `solr_dump_catalog` correctly handle boolean values and empty text fields.
[hannosch]

2.0a2

------------------

* Provide a dummy request in the `solr_dump_catalog` command.
[hannosch]

2.0a1

------------------

* Handle utf-8 encoded data correctly in `utils.isWildCard`.
[hannosch]

* Gracefully handle exceptions raised during index data retrieval.
[tom_gross, hannosch]

* Added `zopectl.command` entry points for three new scripts.
`solr_clear_index` will remove all entries from Solr. `solr_dump_catalog`
will efficiently dump the content of the catalog onto the filesystem and
`solr_import_dump` will import the dump into Solr. This can be used to
bootstrap an empty Solr index or update it when the boost logic has changed.
All scripts will either take the first Plone site found in the database or
accept an unnamed command line argument to specify the id. The Solr server
needs to be running and the connection info needs to be configured in the
Plone site. Example use: ``bin/instance solr_dump_catalog Plone``. In this
example the data would be stored in `var/instance/solr_dump_plone`. The data
can be transferred between machines and calling `solr_dump_catalog` multiple
times will append new data to the existing dump. To get Solr up-to-date you
should still call `solr-maintenance/sync`.
[hannosch, witsch]

* Changed search pattern syntax to use `str.format` syntax and make both
`{value}` and `{base_value}` available in the pattern.
[hannosch]

* Add possibility to calculate site-specific boost values via a skin script.
[hannosch, witsch]

* Fix wildcard searches for patterns other than just ending with an asterisk.
[hannosch, witsch]

* Require Plone 4.x, declare package dependencies & remove BBB bits.
[hannosch, witsch]

* Add configurable setting for custom search pattern for simple searches,
allowing to include multiple fields with specific boost values.
[hannosch, witsch]

* Don't modify search parameters during indexing.
[hannosch, witsch]

* Fixed auto-commit support to actually sent the data to Solr, but omit the
commit message.
[hannosch]

* Added support for ``commitWithin`` support on add messages as per SOLR-793.
This feature requires a Solr 1.4 server.
[hannosch]

* Split out 404 auto-suggestion tests into a separate file and disabled them
under Plone 4 - the feature is no longer part of Plone.
[hannosch]

* Fixed error handling code to deal with different exception string
representations in Python 2.6.
[hannosch]

* Made tests independent of the ``Large Folder`` content type, as it no longer
exists in Plone 4.
[hannosch]

* Avoid using the incompatible TestRequest from zope.publisher inside Zope 2.
[hannosch]

* Fixed undefined variables in ``search.pt`` for Plone 4 compatibility.
[hannosch]

Page 3 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.