I suggest you ...

← Deprecated Feedback Forum

Expand the searching capabilities of gitlab by using Elasticsearch

GitLab is great for hosting code when you know where that code is and what is going on in your project. However, when you involve other people in your project or you need to search all of the projects which you have access for code, issues, milestones, etc there is no good way to search.

I searched for a single filename which I know exists in a repository and I couldn't find even the name of the file (let alone the contents of it).

I propose expanding the search capabilities of GitLab by integrating elasticsearch for indexing everything GitLab has to offer. Whether it's code, issues, milestones, merge requests, wall, wiki, what have you.

79 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    Sam Gleske shared this idea  ·   ·  Admin →

    13 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Forgot password?
      Create a password
      Signed in as (Sign out)
      Close
      Close
      Submitting...
      • Roman Mykhailiuk commented  · 

        Hi guys,
        Are there any plans to implement at least Postgres full text search in Gitlab, to be able to search all the code, not just inside one repository?
        Thank you

      • Anonymous commented  · 

        We have a repository for production ready modules, but we are having trouble searching for the module name which corresponds to the folder name within the production repository. A basic search for filename or folder name would be a huge advantage on usability

      • AdminGitLab team (Admin, Gitlab) commented  · 

        Adding all the dependencies to run Elastic Search (JVM, etc.) would make GitLab hard to install and maintain. It also requires a lot of extra resources (increasing the memory requirements). We afraid that there will be a split of some people running GitLab with Elastic Search and some people without, greatly complicating future development.

        We think there are still a lot of possibilities for improving GitLab search with PostgreSQL. Maybe we should focus on improving that. Long term we see GitLab using PostgreSQL exclusively and we don't mind improving the search experience for people using PostgreSQL only. A good article about it is http://blog.lostpropertyhq.com/postgres-full-text-search-is-good-enough/

        Of course this is not as good as using Elastic Search and there are valid comments about this in https://news.ycombinator.com/item?id=8381748 But there is a big advantage to keeping everyone working with the same GitLab. Search is something that could use more development attention and we should put our effort into something that everyone can use.

      • Matthias Niehoff commented  · 

        Hi guys, what is the current progress on this? we are very interested in this feature and the screenshot provided by Zzet looks very cool!

      • Sam Gleske commented  · 

        Even better that appears to have some integration with gitlab!... I'm going to play with it and see what I come up with...

      • Sam Gleske commented  · 

        I'm thinking of attempting to implement elasticsearch as an addon component to gitlab (not a requirement). I feel like PostgreSQL fulltext search is a bit heavy on the processing side to effectively serve the scope of the content I'm talking about. Additionally my org uses MySQL as the backend for this so in this scenario Postgres fulltext search wouldn't apply at all.

        For people running a raspi or digital ocean if this is configurable as an optional external service to plug-in they simply run elasticsearch in a different system or not at all.

      Deprecated Feedback Forum: GitLab CE

      Feedback and Knowledge Base

      (thinking…)