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.

Sign up for GitHub

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

Jump to bottom

Elasticsearch が利用できないときはデータベースの検索を利用するように #3315

Closed
tamaina opened this issue Nov 18, 2018 · 4 comments · Fixed by #5712
Closed

Elasticsearch が利用できないときはデータベースの検索を利用するように #3315

tamaina opened this issue Nov 18, 2018 · 4 comments · Fixed by #5712
Labels
✨Feature This adds/improves/enhances a feature packages/backend Server side specific issue/PR
Projects
v12
Milestone
v12

Comments

@tamaina
Copy link
Member

tamaina commented Nov 18, 2018 •
edited by acid-chicken

mongoDBでの検索で十分な言語のユーザーにESの使用を強制するのは理不尽なので、Elasticsearchが利用できないときはデータベースの標準の検索機能を利用するようにしたい。

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
@tamaina
Copy link
Member Author

tamaina commented Nov 18, 2018

#3312

@tamaina tamaina changed the title Elastic Searchが利用できないとき、mongodbの検索を利用 Elastic Searchが利用できないときはデータベースの検索を利用するように Mar 27, 2019
@syuilo
Copy link
Member

syuilo commented Nov 2, 2019

LIKEクエリくらいしか思いつかないけど重くなりそう。
クエリに時間制限みたいなのを付けられる機能があれば負荷が高い状態が続くのを避けることができそうだけど、そのようなオプションがあるのか不明。
インスタンス内の投稿だけに絞るという方法では、インスタンス内の投稿が少ないならば速くなるけど、そうでない場合はヒットする投稿が見つかる可能性が低くなるからむしろ遅くなると思われる。

@acid-chicken acid-chicken changed the title Elastic Searchが利用できないときはデータベースの検索を利用するように Elasticsearch が利用できないときはデータベースの検索を利用するように Nov 2, 2019
@rinsuki
Copy link
Contributor

rinsuki commented Nov 2, 2019

ソート順を投稿日順にして直近一週間とかに制限すればマシになりそう

@acid-chicken
Copy link
Member

https://www.postgresql.jp/document/11/html/textsearch-indexes.html

@syuilo syuilo added packages/backend Server side specific issue/PR ✨Feature This adds/improves/enhances a feature labels Jan 20, 2020
@syuilo syuilo added this to the v12 milestone Jan 20, 2020
@syuilo syuilo mentioned this issue Jan 20, 2020
Merged
@syuilo syuilo added this to Close in v12 Jan 20, 2020
nokotaro pushed a commit to nokotaro/misskey that referenced this issue Jan 30, 2022
@dependabot
Bump content-disposition from 0.5.3 to 0.5.4 (misskey-dev#3315)
46be97f 
Bumps [content-disposition](https://github.com/jshttp/content-disposition) from 0.5.3 to 0.5.4.
- [Release notes](https://github.com/jshttp/content-disposition/releases)
- [Changelog](https://github.com/jshttp/content-disposition/blob/master/HISTORY.md)
- [Commits](jshttp/content-disposition@v0.5.3...v0.5.4)

---
updated-dependencies:
- dependency-name: content-disposition
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
✨Feature This adds/improves/enhances a feature packages/backend Server side specific issue/PR
Projects
No open projects
v12
  
Close
Milestone
v12
Development

Successfully merging a pull request may close this issue.

v12 misskey-dev/misskey
4 participants
@syuilo @rinsuki @tamaina @acid-chicken