Details
-
Type:
Story
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 4.3.0
-
Fix Version/s: Short Term
-
Component/s: Staff Interface
-
Labels:None
Description
Elasticsearch is an application that could be installed on your own server, and used to dramatically improve searches within Blesta. See https://www.elastic.co/products/elasticsearch
This would optionally replace existing searches, and probably be an extra charge or part of an "Enterprise" feature set.
We could potentially just add a new search option when this is enabled called Elastic Search, and search everything from one field.
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Elasticsearch is an application that could be installed on your own server, and used to dramatically improve searches within Blesta. See https://www.elastic.co/products/elasticsearch
This would optionally replace existing searches, and probably be an extra charge or part of an "Enterprise" feature set. |
Elasticsearch is an application that could be installed on your own server, and used to dramatically improve searches within Blesta. See https://www.elastic.co/products/elasticsearch
This would optionally replace existing searches, and probably be an extra charge or part of an "Enterprise" feature set. We could potentially just add a new search option when this is enabled called Elastic Search, and search everything from one field. |
Yes, the data would have to be added to Elasticsearch. It doesn't replace Blesta, it's just for search purposes. My understanding is that we add data to it that we want to be searchable and it does a better faster job at searching tons of records.
Paul Phillips
added a comment - Yes, the data would have to be added to Elasticsearch. It doesn't replace Blesta, it's just for search purposes. My understanding is that we add data to it that we want to be searchable and it does a better faster job at searching tons of records. If you search for it in elasticsearch, we have to match the search results up with Blesta anyway in order to display relevant information. The elasticsearch data still must be added/updated/deleted as data changes in Blesta to keep it in sync. I'm sure it does a good job at searching tons of records, but Blesta doesn't store tons of records.
Tyson Phillips (Inactive)
added a comment - If you search for it in elasticsearch, we have to match the search results up with Blesta anyway in order to display relevant information. The elasticsearch data still must be added/updated/deleted as data changes in Blesta to keep it in sync. I'm sure it does a good job at searching tons of records, but Blesta doesn't store tons of records.
This is mostly a networked database with a different structure and language. You still have to write all the data to the database in order to search it, so unless you're replacing Blesta's database with one on Elasticsearch, you'll have to maintain 2x the data. Probably worth using for big data sets (terabytes/billions of documents).