You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TikaStatus strictly expects that extractByQuery will return an array with 3 elements:
0 - content
1 - metadata
2 - response
Beside that the response will only be available with upcoming EXT:solr versions 12.0.1+ (introduced with TYPO3-Solr/ext-solr@0b1a6a1) SolrWriteService->extractByQuery() will return an empty array if an exception occurred.
So in 2 cases an exception will occur in the reports module currently:
EXT:solr 12.0.0 is used
An exception occurred during extraction
For example the following exception if EXT:solr 12.0.0 is used:
Exception: "PHP Warning: Undefined array key 2 in Classes/Report/TikaStatus.php line 196" with code 1476107295 in /var/www/html/vendor/typo3/cms-core/Classes/Error/ErrorHandler.php line 138
A similar exception will occur if an empty array is returned. thus we should refactor the handling of the extractByQuery response.
To Reproduce
Steps to reproduce the behavior:
Install EXT:tika 12.0.1 and EXT:solr 12.0.0
Open the reports module
Exception message will be shown in the Apache Tika section
Expected behavior
All type of responses of extractByQuery can be handled to give proper hints of the status in the reports module.
Used versions (please complete the following information):
TYPO3 Version: 12.4
EXT:solr Version: 12.0.0+
EXT:tika Version: 12.0.1
The text was updated successfully, but these errors were encountered:
Fixed in TYPO3-Solr/ext-solr#3858
We'll ignore the case somebody uses EXT:solr 12.0.0 with EXT:tika 12.0.1+.
The EXT:solr 12.0.1 will be released soon.
Describe the bug
TikaStatus
strictly expects thatextractByQuery
will return an array with 3 elements:0 - content
1 - metadata
2 - response
Beside that the response will only be available with upcoming EXT:solr versions 12.0.1+ (introduced with TYPO3-Solr/ext-solr@0b1a6a1)
SolrWriteService->extractByQuery()
will return an empty array if an exception occurred.So in 2 cases an exception will occur in the reports module currently:
For example the following exception if EXT:solr 12.0.0 is used:
A similar exception will occur if an empty array is returned. thus we should refactor the handling of the
extractByQuery
response.To Reproduce
Steps to reproduce the behavior:
Expected behavior
All type of responses of
extractByQuery
can be handled to give proper hints of the status in the reports module.Used versions (please complete the following information):
The text was updated successfully, but these errors were encountered: