Releases: Flowpack/Flowpack.ElasticSearch.ContentRepositoryQueueIndexer
4.0.0
- Package is now compatible to Flow 6.x
- Package is compatible to Flowpack.ElasticSearch.ContentRepositoryAdaptor Version 5.0 and 6.0
- Refactored logger outputs to a more readable format
- Code cleanup
3.3.0
- Package is compatible to Flowpack.ElasticSearch.ContentRepositoryAdaptor Version 5.0
- Improvements on handling of deleted nodes
3.2.0
FEATURE: Old indexes are automatically removed when the index switch is done successfully
3.1.0
- Failed indexing jobs in the current job queue are now checked against a configurable threshold of allowed failed jobs. If the threshold is exceeded the index is not switched.
- Some tweaks to the log messages to keep the log clean when indexing lots of nodes.
3.0.4
3.0.3
2.0.6
3.0.2
Bugfixes
Skip indexing if NodeData cannot be loaded
This fixes #14 by skipping indexing, but the fulltext index will still
contain whatever content existed before the deletion.
Correctly use node identifier in fake nodes
When a "fake" node was needed, it was assigned the persistence object
identifier as node identifier. This leads to mismatches in fulltext
indexing (at least.)
Now both identifiers are in the job payload and used as needed.
Pass target workspace name to node indexer
In the IndexingJob and RemovalJob the target workspace name was not
passed on to the node indexer upon job execution.
This lead to wrong nodes being indexed, at times.
Fix realtime indexing of node deletion
Improvements
Add RemovalJob to handle removal asynchronously
This complements the async handling of node indexing.
Add more information in the Removal and Indexing Job
This change add context patch and node type to both job payload, to
be able to create a fake node if the node as been deleted in between.
Use preset to define queues
This allows easy overriding of the queue settings in a project
through the use of presets as offered by the JobQueue.Common
package.