We replace the "flush" and "delete" by "delete" and "deletedocuments"
logic. This makes it more obvious what will happen, without reading the
docs.
Also we kept the logic to always provide the index name, as
we will need them in the future. Due to elasticsearch v6 changes no
types are allowed in the same index in the future. Therefore we need to
make it possible to use different indexes in the future, leading to the
need to provide the document type all the time.
As this didn't work on first use. Also no tests are available for this
feature yet.
As we remove the whole feature in a single commit, we can revert this
commit later. This way we can upgrade Elasticsearch and provide this
feature later on.
* Streamline all commands to always accept a comma separated list of
identifiers.
* Adjust phpdoc to reflect this feature and provide help on CLI.
* Refactor code to move recurring logic to own method.
* Provide tests for new feature.
* Add documentation for feature.
Instead of hardcoding and tight coupling of relation resolving, we now
provide a dataprocessor instead.
Therefore you need to configure resolving for each indexed type.
This resolves#149 and #147.
Before this change, sys_language_uid was indexed as an empty string, due
to internal used TYPO3 API.
We now skip the configure field which defines language uid. This way you
can build filter based on current language.
Resolves#148
Allows integrators to configure which fields should be used to produce
field "content" for indexed pages.
Before only "bodytext" was used. This is now configurable and "header"
was added to defaults.
Resolves: #134
Do not index content records of all pages while indexing pages in CMS
8.x.
We add same logic as for CMS 7.x, we extend the query to only fetch
records from current page.
Resolves: #135
Fetch sys_language_uid from database.
Until now we did not fetch system related fields from database. As there
is now a RemoveProcessor, integrators are able to remove fields.
Also providing this field enables basic multi language support.
Relates: #25
We had some features in 7.6 support which we didn't merge up yet.
Mostly very small bug fixes or more helpful logging and processing of
elasticsearch options.
But also adding images of content elements while indexing pages.
Use own service to handle data processing. Classes like indexer should
not know anything about the structure and how to process the data.
Also rename record to data, as we can process just any data in form of
an array.
Relates: #116
This way injects will be resolved inside of processors, enabling
developers to inject dependencies.
We use inject instead of constructor as indexers mostly will change the
constructor and should not need to add the objectmanager.
Resolves: #117