Re: Solr Flare
Hi Erik (and others),
I would like to help with this effort. But I want to make sure I understand
the landscape (forgive my noobness):
Solr Flare is actual two pieces of software: 1) a Rails application [flare]
that uses 2) a Ruby DSL [solrb] to communicate with a Solr Server. Is this
correct?
Plus, the current state/status of Solr Flare is that the UI is yet to be
developed but the communication piece works. Is this also correct?
What work is next?
Thanks,
Mel Riffe
Erik Hatcher wrote:
>
> Based on a chat with an early adopter of Flare, we decided to split
> out the Ruby-Solr DSL sooner rather than later. I've pulled out the
> library code into a separate directory under client/ruby/solrb ("rb"
> being the standard Ruby file extension). Info for this library is here:
>
> <http://wiki.apache.org/solr/solrb>
>
> Flare will be the user interface that leverages solrb to communicate
> with Solr, though currently the Flare code is just an empty Rails
> generated application. It'll start being useful very soon. There
> are quite a few folks already dipping into this, so this all should
> evolve fairly quickly over the next few weeks.
>
> Erik
>
>>> On 1/2/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
>>>> I'm finally kicking off that long dreamed of Ruby/Solr DSL,
>>>> including
>>>> an accompanying general purpose web interface to showcase the
>>>> greatness of Solr's capabilities, including faceted browsing. I've
>>>> titled the project Flare, and have committed the bits of low-level
>>>> code into Solr's repository. The gory details are on the wiki,
>>>> here:
>>>>
>>>> <http://wiki.apache.org/solr/Flare>
>>>>
>>>> I'm dedicating the next couple of months of spare time to this in
>>>> order to have it ready for a couple of big projects, one is to
>>>> demonstrate a faceted browsing front-end on our libraries holdings
>>>> (~3.7M records), and also to have a framework for even more easily
>>>> demonstrating and teaching Lucene and Solr to a bunch of library
>>>> geeks
>>>> [1].
>>>>
>>>> For the Ruby-savvy of you out there, I'd love to have help in
>>>> crafting a Ruby Solr DSL suitable for "gem install", and fleshing
>>>> out
>>>> a general purpose API and UI. As for collaboration, it'll be via
>>>> JIRA patches, wiki, and this e-mail list, and we'll go from there.
>>>> Thanks in advance!
>>>>
>>>> Erik
>>>>
>>>> [1] http://www.code4lib.org/node/139
>
>
>
--
View this message in context:
http://www.nabble.com/Solr-Flare-tf2910036.html#a8272154
Sent from the Solr - User mailing list archive at Nabble.com.
[solrb] Win32 Functional Tests and patches...
Howdy everyone, I have a first pass at getting the test server to come up in a win32 environment. So I would like to know how to submit a patch. Right now I have two failing tests and would welcome any advice/suggestions to aid in debugging the problems. Here is the output of rake test: rm -rf test/data starting solr server on i386-mswin32 c:/ruby/bin/ruby -Ilib -r solr -r test/unit -Itest/functional "c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader.rb" "test/functional/server_test.rb" Loaded suite c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.1 /lib/rake/rake_test_loader Started .F.F.. Finished in 10.219 seconds. 1) Failure: test_bad_connection(ServerTest) [./test/functional/server_test.rb:78]: exception expected but was Class: Message: <"Bad file descriptor - connect(2)"> ---Backtrace--- c:/ruby/lib/ruby/1.8/net/http.rb:560:in `initialize' c:/ruby/lib/ruby/1.8/net/http.rb:560:in `open' c:/ruby/lib/ruby/1.8/net/http.rb:560:in `connect' c:/ruby/lib/ruby/1.8/timeout.rb:48:in `timeout' c:/ruby/lib/ruby/1.8/timeout.rb:76:in `timeout' c:/ruby/lib/ruby/1.8/net/http.rb:560:in `connect' c:/ruby/lib/ruby/1.8/net/http.rb:553:in `do_start' c:/ruby/lib/ruby/1.8/net/http.rb:542:in `start' c:/ruby/lib/ruby/1.8/net/http.rb:1032:in `request' c:/ruby/lib/ruby/1.8/net/http.rb:842:in `post' ./lib/solr/connection.rb:137:in `post' ./lib/solr/connection.rb:130:in `send' ./test/functional/server_test.rb:79:in `test_bad_connection' ./test/functional/server_test.rb:78:in `test_bad_connection' --- 2) Failure: test_ping(ServerTest) [./test/functional/server_test.rb:96]: expected but was . 14 tests, 21 assertions, 2 failures, 0 errors stopping solr server Cheers, Mel
Re: [solrb] Win32 Functional Tests and patches...
On 2/6/07, Erik Hatcher <[EMAIL PROTECTED]> wrote: On Feb 5, 2007, at 11:50 PM, Mel Riffe wrote: > I have a first pass at getting the test server to come up in a win32 > environment. Fantastic! Now both of you will soon be able to test solrb on Windows ;) > So I would like to know how to submit a patch. Pleasantly enough, we have this: <http://wiki.apache.org/solr/ HowToContribute> Thanks! Hopefully tonight... For solrb, patches rooted from the solrb directory are cleaner for me. > 1) Failure: > test_bad_connection(ServerTest) [./test/functional/server_test.rb:78]: > exception expected but was > Class: > Message: <"Bad file descriptor - connect(2)"> This test has been brittle, I believe. We can adjust it to be more lenient and simply assert we get an exception thrown. This test in particular is not really testing much of importance, since pointing solrb to a bad Solr URL is gonna be bad news no matter what. But making the exception it checks for more lenient should be fine. > 2) Failure: > test_ping(ServerTest) [./test/functional/server_test.rb:96]: > expected but was > . hmmm... odd. I don't have an explanation for this one. What is the ping request returning? Fire up Solr and hit /admin/ping to see what is returned. Can do! Thanks for your effort on this. Despite my joke above, Windows support is important. Actually there are three Windows users: Me, Myself and I. ;-) Cheers, Mel Erik
