[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466970
]
Ryan McKinley commented on SOLR-20:
---
I have dramatically reworked the client code to fit with the pluggable
ContentSt
On Jan 24, 2007, at 1:01 AM, Yonik Seeley (JIRA) wrote:
Yonik Seeley commented on SOLR-104:
---
Oh, and where possible, it would be nice to have some unit tests.
Yes, please! Lots and lots of unit tests :)
I'm really enamored by code coverage analysis to poin
On 1/24/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
...It is harder to test things that rely on a container, but there are
many techniques to make it easier with mocks...
FWIW, it's very easy to start Jetty in embedded mode from a Java
class, this can be useful for testing.
Improving Solr's t
The solrb code is good enough to deserve an 0.0.1 release to have
folks try it out easier than checking it out from Subversion,
building a .gem (somewhat analogous to a Java JAR), and then
installing it.
What I'd like to do for now is simply run "rake package" locally, and
check in the .g
On 1/24/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
...Yonik/Hoss, others - what do you think should be done to make releases?...
If you mean an actual release (defined in [1] as "any publication
outside the group of people on the product dev list"), the PMC must
vote to approve it, and it mus
On Jan 24, 2007, at 11:35 AM, Erik Hatcher wrote:
I'd rather us do it all here at ASF to keep it in-house and tightly
synced with Solr itself.
You can run your own gem server very easily. Perhaps a gem server for
apache projects might be a good long term goal? In my opinion putting
the gem
On Jan 24, 2007, at 11:53 AM, Bertrand Delacretaz wrote:
On 1/24/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
...Yonik/Hoss, others - what do you think should be done to make
releases?...
If you mean an actual release (defined in [1] as "any publication
outside the group of people on the pr
On Jan 24, 2007, at 11:54 AM, Edward Summers wrote:
On Jan 24, 2007, at 11:35 AM, Erik Hatcher wrote:
I'd rather us do it all here at ASF to keep it in-house and
tightly synced with Solr itself.
You can run your own gem server very easily. Perhaps a gem server
for apache projects might be
On Jan 24, 2007, at 12:11 PM, Erik Hatcher wrote:
Indeed, but it isn't the end of the world for them to add a --
source on there.
Absolutely not the end of the world--just not the ruby way :-)
It'll be "solrb" though, not "solr" - it seems better to keep it a
separate name so it doesn't app
On 1/24/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
On Jan 24, 2007, at 11:53 AM, Bertrand Delacretaz wrote:
> On 1/24/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
>
>> ...Yonik/Hoss, others - what do you think should be done to make
>> releases?...
>
> If you mean an actual release (defined in [
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467116
]
Yonik Seeley commented on SOLR-20:
--
> * it is based on commons-httpclient-3.0.1.jar
Cool, +1
> * I'm using wt=JSON rat
[
https://issues.apache.org/jira/browse/SOLR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467139
]
mrball commented on SOLR-69:
Thanks for writing this!
Just a shot in the dark: Would it be possible to use this on fields t
> * I'm using wt=JSON rather then XML. (It maps to a hash easier)
Heh... I quickly checked out the code, but didn't see where you were parsing
the code, or where the JSONObject class referenced is.
Anyway, if you want the *best* JSON parser on the planet, check out
http://www.nabble.com/Apache-
Hi Ryan,
The big API question/style i'm struggling with is
SolrResponse rsp = client.process( req );
vs
SolrResponse rsp = req.execute( client ); // execute may not be the
right word
The first one is more natural, and is how things are actually
processed. The second one allows eliminates
On Jan 24, 2007, at 2:10 PM, Yonik Seeley wrote:
I would think we could set up a nightly build to go to
people.apache.org/builds/lucene/solr/solrb/nightly
and perhaps release candidates could go in
people.apache.org/builds/lucene/solr/solrb/
Definitely!
I got my zones account, and have file
On 1/24/07, Ken Krugler <[EMAIL PROTECTED]> wrote:
Hi Ryan,
>The big API question/style i'm struggling with is
>
>SolrResponse rsp = client.process( req );
> vs
>SolrResponse rsp = req.execute( client ); // execute may not be the
>right word
>
>The first one is more natural, and is how things
On Jan 24, 2007, at 12:21 PM, Edward Summers wrote:
On Jan 24, 2007, at 12:11 PM, Erik Hatcher wrote:
Indeed, but it isn't the end of the world for them to add a --
source on there.
Absolutely not the end of the world--just not the ruby way :-)
Then why is there a --source switch? ;)
What
On Jan 24, 2007, at 4:05 PM, Ken Krugler wrote:
SolrQueryResponse rsp = (SolrQueryResponse)client.process( req );
vs
SolrQueryResponse rsp = queryRequest.execute( client );
This might seem outlandish but have you considered modeling a server
instead of a client? Then you can send request mes
On Jan 24, 2007, at 4:49 PM, Erik Hatcher wrote:
What I'd like to do is get Apache moved towards being Ruby savvy.
The ideal, to me, is getting deployments of releases to work
cleanly with "gem install" from the Apache infrastructure. No
offense to rubyforge at all (hi Rich and Tom!), I'm
[
https://issues.apache.org/jira/browse/SOLR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467179
]
Bertrand Delacretaz commented on SOLR-69:
-
Intuitively, without having checked exactly how it's implemented, I t
This might seem outlandish but have you considered modeling a server
instead of a client? Then you can send request messages to it and get
back response messages.
SolrSelectResponse response = server.select(selectOptions);
I like the model, but the I want to be able easily write a client f
On Jan 22, 2007, at 6:14 PM, Yonik Seeley wrote:
Chris Hostetter <[EMAIL PROTECTED]> wrote:
as i said, i'd rather invert the use case set to find where "ordering
isn't important" and change those to Maps
That might be a *lot* of changes...
What's currently broken, just faceting or anything e
On Jan 23, 2007, at 4:52 PM, J.J. Larrea wrote:
In fact, it would probably please too-lazy-to-translate-facet-value-
strings front-end coders if there were a way to provide a label for
the missing count, e.g.
None
No authorship
indicated
There is much more to facet name mapping f
[
https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clay Webster updated SOLR-84:
-
Attachment: logo-solr-source-files-take2.zip
I took the contents of the zip file and made a logo without the
[
https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clay Webster updated SOLR-84:
-
Attachment: solr-logo-20070124.JPG
> New Solr logo?
> --
>
>
ter: Bertrand Delacretaz
>Priority: Minor
> Attachments: logo-solr-source-files-take2.zip,
> solr-84-source-files.zip, solr-logo-20061214.jpg, solr-logo-20061218.JPG,
> solr-logo-20070124.JPG
>
>
> Following up on SOLR-76, our trainee Nicolas Barbay (nic
On Jan 24, 2007, at 6:53 PM, Ryan McKinley wrote:
new SolrPing().process( server );
doesn't
server.ping();
look cleaner?
//Ed
files.zip, solr-logo-20061214.jpg, solr-logo-20061218.JPG,
> solr-logo-20070124.JPG, solr.jpg
>
>
> Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here)
> sarraux-dessous.ch) has reworked his logo proposal to be more "solar".
> This can either be the st
files.zip, solr-logo-20061214.jpg, solr-logo-20061218.JPG,
> solr-logo-20070124.JPG, solr.jpg, solr.jpg
>
>
> Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here)
> sarraux-dessous.ch) has reworked his logo proposal to be more "solar".
> This can e
sue Type: Improvement
>Reporter: Bertrand Delacretaz
>Priority: Minor
> Attachments: logo-solr-source-files-take2.zip,
> solr-84-source-files.zip, solr-logo-20061214.jpg, solr-logo-20061218.JPG,
> solr-logo-20070124.JPG, solr.jpg, solr.jpg
>
>
>
On Jan 24, 2007, at 6:53 PM, Ryan McKinley wrote:
> new SolrPing().process( server );
doesn't
server.ping();
look cleaner?
I can't argue with you there!
I may be taking Hoss's point #4 on
https://issues.apache.org/jira/browse/SOLR-20#action_12464641 too
seriously. My revised version is
On 1/25/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> On Jan 24, 2007, at 6:53 PM, Ryan McKinley wrote:
> > new SolrPing().process( server );
>
> doesn't
>
>server.ping();
>
> look cleaner?
>
I can't argue with you there!
I may be taking Hoss's point #4 on
https://issues.apache.org/jira/
Sorry Hoss if I came down too hard against the view that "*" should mean "all
docs". With the renewed clarity that getting a little sleep brings, I better
appreciate the merits of your position. And that it's dangerous trying to
decide what makes sense for other people.
Obviously from a pract
: > ...It is harder to test things that rely on a container, but there are
: > many techniques to make it easier with mocks...
:
: FWIW, it's very easy to start Jetty in embedded mode from a Java
: class, this can be useful for testing.
I'm in favor of both of these things: it would be great if t
: I'd like to hear from hoss though, since he was following along more
: than I was, esp at the start of that marathon thread.
FYI: I'm starting to look at this now.
i send this mail only because Ryan is so damn fast and I'd like to
encourage him to take a break and watch some TV or something so
35 matches
Mail list logo
