nextcloud / nextcloud/fulltextsearch

Solr support?

Open
#334 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement help wanted
Dominant language
PHP
Stars
234
Forks
64
Avg merge
6h 18m
Merged PRs (30d)
10

Description

I can't be the only one who gets a very bad taste from even looking at Elasticsearch, can I?

A basic list that anyone who installs this will notice...

  • It has little/no security capability unless the user pays, it's therefore not open source but more like bait-and-switch
  • The alternative to paying for authentication is a plugin that only sends download links by email **
  • The previous two combined are basically an invitation for less careful people to feed ransomware authors.

** The author claims that this is some sort of version control on his part, but he might have a hard time explaining why he is filtering common temporary email services if he doesn't care whether the email addresses are spam-able or not (but not filtering them very well, the third one I tried worked).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the existing search-backend integration and determining whether Solr support is in scope; completion would require an agreed design, implementation scope, and validation criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch
Domain
search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.