Closed abias closed 7 years ago
Hi Alex, This is indeed an issue. I've created branch issue28_tika_connect to solve this. It is still a WIP, but I hope to have it complete in the next 24 hours.
The fix was straight forward, but I'm still working on better test coverage to avoid issues like this in the future
I'll double check but we're a little behind with the release cycle with his plugin, which is likely why this was missed. Also with my own testing and dev I've been using pure txt files that won't go via Tika.
Thanks, Matt, for your feedback. I am looking forward for your final fix :)
Master branch now contains the fix and Moodle plugin dir has been updated.
Thanks for the quick fix, Matt
Hi Matt,
I am currently looking into search_elastic and have added the latest version of this plugin to a Moodle 3.2.3+ (Build: 20170622) instance and have hooked this up to a fresh elasticsearch 5.5 instance.
I also started a standalone tika instance running on a separate machine and configured this tika instance in the plugin's settings.
While doing the first indexing with
sudo -u apache /opt/rh/rh-php70/root/usr/bin/php /var/www/html/moodle_dev3/search/cli/indexer.php --force
with fileindexing enabled, the indexer script encountered a fatal error and stopped with this message:I traced the problem back to commit 4c32c7103f9b1579807e02a743cfedf292247df2 which breaks the connection to tika. Based on the latest code, this patch should solve the problem and clean up the function at the same time:
However, I am wondering how this problem could remain undetected as you are running this plugin in production...
Thanks, Alex