Do I need to keep elasticsearch?

Rellwood · 08-14-2022, 05:16 PM

Am getting a new computer and would like to know if I need to install Elasticsearch on it for the text search to work.

Already have "Full Text Search" Plugin and am wondering if is redundant

Also, the full text search file in the library folder is 7.5GB - is this normal? Can I avoid having this? I would rather keep the full text search and not have such a big file.

ownedbycats · 08-14-2022, 06:48 PM

Only if you want to continue using the Power Search plugin. The built-in full text search doesn't use Elasticsearch.

Rellwood · 08-14-2022, 07:38 PM

Is there a difference between the two? I mean, do I HAVE to use the Calibre version or can I just stick with Power Search so I don't have to keep a huge file in the library folder

PeterT · 08-14-2022, 07:45 PM

You can search by whatever method you want; it's totally YOUR call (and ONLY your call).

Sent from my Pixel 4a using Tapatalk

Rellwood · 08-14-2022, 08:12 PM

I would like to stop Calibre from creating the "full text search" database file in my folder, it is causing the "check library" function to slow down. Is there a way of "opting out" of this feature?

BetterRed · 08-14-2022, 08:47 PM

Close calibre and delete the full-text-search.db from the library folder and don't use the built-in feature.

BetterRed · 08-14-2022, 08:54 PM

Hmmm, you're right it, slows the database vacuuming phase of check library considerably, maybe it should be optional - vacuuming that is.

ownedbycats · 08-14-2022, 09:59 PM

Quote:

Originally Posted by Rellwood

I would like to stop Calibre from creating the "full text search" database file in my folder, it is causing the "check library" function to slow down. Is there a way of "opting out" of this feature?

Disable the built-in full text search.

DNSB · 08-14-2022, 10:42 PM

If you are that worried about the full text search database, have you looked at the size of the ElasticSearch database for the same library?

ownedbycats · 08-14-2022, 11:54 PM

Quote:

Originally Posted by DNSB

If you are that worried about the full text search database, have you looked at the size of the ElasticSearch database for the same library?

For what it matters, on my library they were close to the same size.

ownedbycats · 08-14-2022, 11:57 PM

Also, opened a ticket here:

https://bugs.launchpad.net/calibre/+bug/1986500

Sarmat89 · 08-15-2022, 12:23 AM

Quote:

Originally Posted by Rellwood

Also, the full text search file in the library folder is 7.5GB - is this normal?

Calibre doesn't use the real FTS. It's just a module with a similar functionality that is bundled with SQLite. If you have real indexing software with e-book plugins, use it instead.

DrChiper · 08-15-2022, 05:13 AM

Quote:

Originally Posted by Rellwood

Also, the full text search file in the library folder is 7.5GB - is this normal?

Yes, its common. I even have one which is 19GiB in size. Hate to use "check database" on that one in the near future.

What is interesting is that using "vacuum" via SQLite on the full-text-search.db did not seem to have taken that long as via calibre. It might have to do with different underlying implementation though

Rellwood · 08-26-2022, 05:15 PM

Quote:

Originally Posted by DrChiper

Yes, its common. I even have one which is 19GiB in size. Hate to use "check database" on that one in the near future.

What is interesting is that using "vacuum" via SQLite on the full-text-search.db did not seem to have taken that long as via calibre. It might have to do with different underlying implementation though

Yeah, I have been using the Full Text Search plugin with Elastisearch and have had no problems with it slowing down any of the cleaning and checking of the databases. Plus it doesn't include a secondary .db file in the library folder. So, I am going to keep with the plugin and see about stopping it in Calibre. I deleted the file in the past and didn't attempt to use the feature in Calibre, but it went and did it again without my asking it to. I appreciate the feature, but I rareley use it, so having it slow down my library is kind of annoying. I have a pretty fast computer too so when it took a few minutes (not sure how many) for it to clean the database I was shocked. Normally my databases clean out in less than 10 seconds and my main one is 65mb.

ownedbycats · 08-26-2022, 06:20 PM

Due to some users running out of memory, Kovid is going to make vacuuming the FTS database optional.

08-14-2022, 05:16 PM	#1
Rellwood Library Breeder (She/Her) Posts: 1,228 Karma: 1937891 Join Date: Apr 2015 Location: Fullerton, California Device: Paperwhite 2015 (2), PW 2024 (12 GEN), PW 2023 (11 GEN), Scribe (1st)	Do I need to keep elasticsearch? Am getting a new computer and would like to know if I need to install Elasticsearch on it for the text search to work. Already have "Full Text Search" Plugin and am wondering if is redundant Also, the full text search file in the library folder is 7.5GB - is this normal? Can I avoid having this? I would rather keep the full text search and not have such a big file. Last edited by Rellwood; 08-14-2022 at 05:20 PM.

08-14-2022, 06:48 PM	#2
ownedbycats Custom User Title Posts: 10,662 Karma: 74166147 Join Date: Oct 2018 Location: Canada Device: Kobo Libra H2O, formerly Aura HD	Only if you want to continue using the Power Search plugin. The built-in full text search doesn't use Elasticsearch. Last edited by ownedbycats; 08-14-2022 at 06:53 PM.

08-14-2022, 07:38 PM	#3
Rellwood Library Breeder (She/Her) Posts: 1,228 Karma: 1937891 Join Date: Apr 2015 Location: Fullerton, California Device: Paperwhite 2015 (2), PW 2024 (12 GEN), PW 2023 (11 GEN), Scribe (1st)	Is there a difference between the two? I mean, do I HAVE to use the Calibre version or can I just stick with Power Search so I don't have to keep a huge file in the library folder

08-14-2022, 07:45 PM	#4
PeterT Grand Sorcerer Posts: 13,294 Karma: 78876004 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	You can search by whatever method you want; it's totally YOUR call (and ONLY your call). Sent from my Pixel 4a using Tapatalk

08-14-2022, 08:12 PM	#5
Rellwood Library Breeder (She/Her) Posts: 1,228 Karma: 1937891 Join Date: Apr 2015 Location: Fullerton, California Device: Paperwhite 2015 (2), PW 2024 (12 GEN), PW 2023 (11 GEN), Scribe (1st)	I would like to stop Calibre from creating the "full text search" database file in my folder, it is causing the "check library" function to slow down. Is there a way of "opting out" of this feature?

08-14-2022, 08:47 PM	#6
BetterRed null operator (he/him) Posts: 21,616 Karma: 29710338 Join Date: Mar 2012 Location: Sydney Australia Device: none	Close calibre and delete the full-text-search.db from the library folder and don't use the built-in feature.

08-14-2022, 08:54 PM	#7
BetterRed null operator (he/him) Posts: 21,616 Karma: 29710338 Join Date: Mar 2012 Location: Sydney Australia Device: none	Hmmm, you're right it, slows the database vacuuming phase of check library considerably, maybe it should be optional - vacuuming that is.

08-14-2022, 10:42 PM	#9
DNSB Bibliophagist Posts: 44,727 Karma: 168431851 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	If you are that worried about the full text search database, have you looked at the size of the ElasticSearch database for the same library?

08-14-2022, 11:57 PM	#11
ownedbycats Custom User Title Posts: 10,662 Karma: 74166147 Join Date: Oct 2018 Location: Canada Device: Kobo Libra H2O, formerly Aura HD	Also, opened a ticket here: https://bugs.launchpad.net/calibre/+bug/1986500

08-26-2022, 06:20 PM	#15
ownedbycats Custom User Title Posts: 10,662 Karma: 74166147 Join Date: Oct 2018 Location: Canada Device: Kobo Libra H2O, formerly Aura HD	Due to some users running out of memory, Kovid is going to make vacuuming the FTS database optional.

Advert

Advert