Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve full_text_search:synchronize for Chupa Text searver change and down #93

Open
ioio000 opened this issue Jul 7, 2020 · 4 comments

Comments

@ioio000
Copy link

ioio000 commented Jul 7, 2020

I ran the sync after setting the Chupa Text Server URL, but I had the same issue as Issue #92.
I couldn't search in doc, xls, pdf, eml files.
The newly added file will be searched.
Also, files attached while Chupa Text Server was stopped were not included in the search even after synchronization after startup.
production.log

Environment:
bitnami-redmine-4.1.1-2-windows-x64
mariadb-10.4.12-with-mroonga-10.02-winx64
full_text_search 1.0.4
chupa-text-docker on Ubuntu 20.04 LTS
Added gem "chupa-text-decomposer-mail" to Gemfile.local file.

@kou
Copy link
Member

kou commented Jul 7, 2020

Do you want to say the followings?

  • full_text_search:synchronize doesn't detect Chupa Text server URL change
    • It should run re-text-extraction against attachments that are already processed before Chupa Text server URL change
  • full_text_search:synchronize doesn't care about text-extraction error by Chupa Text server down
    • It should run re-text-extraction against attachments that are failed by Chupa Text server down

@ioio000
Copy link
Author

ioio000 commented Jul 7, 2020

Yes, pretty much.

@kou kou changed the title Similar to Issue #92 when using ChupaText Server. Improve full_text_search:synchronize for Chupa Text searver change and down Jul 8, 2020
@kou
Copy link
Member

kou commented Jul 8, 2020

Workaround: bin/rails full_text_search:reload

@ioio000
Copy link
Author

ioio000 commented Jul 8, 2020

It worked with the bin/rails full_text_search:target:reload command.
However, it takes a lot of time when there are many files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants