mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #571] elasticsearch support #411
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#411
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tallesairan on GitHub (Apr 12, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/571
Would it be possible to use elastic to save the information? I need millions of records I'm a bit afraid of speed in the future with mysql
@phanan commented on GitHub (Apr 14, 2017):
I don't know the future.
@phanan commented on GitHub (Apr 15, 2017):
Sorry for the rude answer, I wasn't in my best mood yesterday. Still, the point is, I don't know how MySQL will perform with millions of records (if by records, you mean songs). I don't see how a person can own a million songs though, and if you do, Koel's performance may not be the first thing you should worry about.
Now, since Koel's built on top of Laravel, it will support any (R)DBMS Laravel does. Elastic, unfortunately, is not one out of the box.