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

investigate moving most/all searchable tables from MySQL to ElasticSearch #225

Closed
ghukill opened this issue Jun 27, 2018 · 1 comment
Closed

Comments

@ghukill
Copy link
Contributor

ghukill commented Jun 27, 2018

As Combine takes in more records, some tables are responsive, others less so.

A particularly egregious example of this is the Record table for testing screens. Given a search term, when Combine has 1m+, it becomes prohibitively slow, if not outright timeout error.

Same is true for other tables however, those that are using the Datatables connector to a MySQL view.

If this were tackled, this would serve to also address these issues:

@ghukill
Copy link
Contributor Author

ghukill commented Sep 14, 2018

Closing - this has been partially addressed switching to Mongo, and other issues pertaining to ES for tables and searching.

@ghukill ghukill closed this as completed Sep 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant