Re: [rubygems.org] Search only looks at the gem name?

[Wilson Bilkovich]

On Sun, Mar 10, 2013 at 1:37 PM, Brandon Fosdick <bfos...@gmail.com> wrote:
> Someone in r/ruby mentioned that the search function on rubygems.org only
> searches gem names and nothing else, which seemed odd to me. So I did a
> little test...if I search for 'gerber' it finds my gerber gem, but if I
> search for 'rs-274' (which is mentioned in the description and is an
> alternate name for the file format) it returns nothing. It seems the rumors
> are true, and I don't see any links that look like an advanced search
> function. Am I just missing it?
>
> Is this by design? Are there any plans to expand the scope of the search?

At the moment, `search` is just an alias for `list`, and works a whole
lot more like you'd expect that second verb to behave.

I think it would be great if you could search to also look in the
summary and description fields.
However, I am opposed to even the current amount of "rubygems api is
required for something that individual users and small organizations
find difficult to replicate privately" that we have implemented, so I
would oppose any extra remote infrastructure.

That being said, maybe there's a way to gracefully extend the index
without making it huge etc.
If we follow the previous patterns (e.g. the move from YAML to
Marshal, then to prerelease gem support, then to quickspecs etc),
there would be yet another gem index file that clients would fetch
when they wanted to enable full-text searching.

[Wilson Bilkovich]

On Sun, Mar 10, 2013 at 2:06 PM, Wilson Bilkovich <wil...@gmail.com> wrote:
> On Sun, Mar 10, 2013 at 1:37 PM, Brandon Fosdick <bfos...@gmail.com> wrote:
>> Someone in r/ruby mentioned that the search function on rubygems.org only
>> searches gem names and nothing else, which seemed odd to me. So I did a
>> little test...if I search for 'gerber' it finds my gerber gem, but if I
>> search for 'rs-274' (which is mentioned in the description and is an
>> alternate name for the file format) it returns nothing. It seems the rumors
>> are true, and I don't see any links that look like an advanced search
>> function. Am I just missing it?
>>
>> Is this by design? Are there any plans to expand the scope of the search?
>
> At the moment, `search` is just an alias for `list`, and works a whole
> lot more like you'd expect that second verb to behave.
>

Hah, my bad, I have my mailing list labels set up wrong and this
appeared in my "rubygems" view, not "rubygems.org"; you're asking
about purely the web feature, and that should be a lot easier to
extend, though I'm sure it currently mirrors the CLI `search` function
I referred to.

[Nick Quaranto]

I think there were performance problems with this so we rolled back to name only search. There were some folks working on a Solr based search that would replace search but nothing much has come out of it. Now that the infrastructure is open I think we should make this better again...any contributions would be awesome.

--
You received this message because you are subscribed to the Google Groups "rubygems.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubygems-org...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jared Fine]

If there is budget Elasticsearch is a nice option. 

(sent from a phone)

[Karel Minařík]

There's a fully featured search implementation for Rubygems at: https://github.com/rubygems/rubygems.org/pull/455

Provided we want to see this rolled out, I'd like to have a specific list of steps needed.

Side note, since Rubygems.org is infrastructure is now AWS/Chef based, it would be trivial to provision Elasticsearch nodes with the Chef cookbook [https://github.com/elasticsearch/cookbook-elasticsearch] and I can do it. Again, it's just a matter of deciding on specific steps/process.

Best,

Karel