.util.NamedList. I can't find this
class. There's a
> import org.apache.util.NamedList, but not a package called common.
>
> Thanks,
>
> jds
>
> On 6/15/07, Ryan McKinley (JIRA) <[EMAIL PROTECTED]> wrote:
>>
>>
>> [
>>
https://i
Thanks,
>
> jds
>
> On 6/15/07, Ryan McKinley (JIRA) <[EMAIL PROTECTED]> wrote:
>>
>>
>> [
>>
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
>>
>>
>> Ryan McKinley re
dency on import
org.apache.solr.common.util.NamedList. I can't find this class. There's a
import org.apache.util.NamedList, but not a package called common.
Thanks,
jds
On 6/15/07, Ryan McKinley (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apac
,
jds
On 6/15/07, Ryan McKinley (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
Ryan McKinley resolved SOLR-20.
---
Resolution: Fixed
Added to trunk
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-20.
---
Resolution: Fixed
Added to trunk... any new problems should get their own issue.
> A simple J
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505313
]
Ryan McKinley commented on SOLR-20:
---
solr 1.2 was released ~1 week ago so the next official stable release is at
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505304
]
Michael Young commented on SOLR-20:
---
We are planning to replace our custom Lucene implementation with Solr in the
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504912
]
Ryan McKinley commented on SOLR-20:
---
I'm integrating SOLR-20 with trunk now...
The basic stuff is no problem.
Ryan McKinley (JIRA) wrote:
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-20:
-
I'm integrating SOLR-20 with trunk now...
The basic stuff is no pr
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-20:
-
Assignee: Ryan McKinley
> A simple Java client for updating and search
to look at:
SOLR-135 and/or SOLR-193
I hope to get SOLR-20 integrated into trunk soon, so there is plenty of
time for it to mature before the next release. It is now reasonably
solid (thanks to help from Will Johnson)
thanks
ryan
ps. I think the "next solr" is better clients/apps -- flare etc
jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502885
> ]
>
> Ryan McKinley commented on SOLR-20:
> ---
>
> I don't know if you are on solr-dev, Yonik noted that the QTime does not
> i
: Has anyone thought of adding the docsum time to the qtime or possibly
: adding separate timing information for the real 'solr query time'.
it's pretty much impossible to include in the response a value which
indicates the total amount of time needed to generate the response...
1) the response
On 8-Jun-07, at 10:57 AM, Will Johnson wrote:
Has anyone thought of adding the docsum time to the qtime or possibly
adding separate timing information for the real 'solr query time'.
While my bosses are very pleased that most searches seem to take
~5ms it
does seem a bit misleading.
docsum
is a reason not to.
- will
-Original Message-
From: Ryan McKinley (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Friday, June 08, 2007 1:09 PM
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-20) A simple Java client for updating
and searching
[
https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502885
]
Ryan McKinley commented on SOLR-20:
---
I don't know if you are on solr-dev, Yonik noted that the QTime doe
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502872
]
Walter Ferrara commented on SOLR-20:
Latest rev works perfectly thanks.
I've been making some time test with
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502852
]
Yonik Seeley commented on SOLR-20:
--
FYI partialURLEncodeVal was meant for readable, yet unambiguous logging...
hence
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Ferrara updated SOLR-20:
---
Comment: was deleted
> A simple Java client for updating and search
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502490
]
Walter Ferrara commented on SOLR-20:
yeah, i eventually modified the function to be just
public static void
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502489
]
Ryan McKinley commented on SOLR-20:
---
Hi Walter-
I just updated http://solrstuff.org/svn/solrj/ to use
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502470
]
Walter Ferrara edited comment on SOLR-20 at 6/7/07 11:50 AM:
-
[I'm new to solr
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502470
]
Walter Ferrara commented on SOLR-20:
[I'm new to solrj, so everything I'm write can be useless]
While
Has anyone had a chance to look at:
SOLR-135 and/or SOLR-193
I hope to get SOLR-20 integrated into trunk soon, so there is plenty of
time for it to mature before the next release. It is now reasonably
solid (thanks to help from Will Johnson)
thanks
ryan
ps. I think the "next sol
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499831
]
Ryan McKinley commented on SOLR-20:
---
Hi Ben-
Thanks for the patch. Will Johnson added the options to the java
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499730
]
Ben Incani commented on SOLR-20:
The SolrClientImpl does not implement the following optional attributes for
"ad
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493006
]
Ryan McKinley commented on SOLR-20:
---
great! Any feedback/help would be wonderful.
I hope it is not *too* long
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492902
]
Will Johnson commented on SOLR-20:
--
the new api's work great, thanks! what's the plan for this going fo
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492716
]
Ryan McKinley commented on SOLR-20:
---
aaah, It was compiling with java 6.
I just added stax-api-1.0.jar and cleaned
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492700
]
Will Johnson commented on SOLR-20:
--
the trunk version at http://solrstuff.org/svn/solrj/ seems to be missing a
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492608
]
Ryan McKinley commented on SOLR-20:
---
For anyone interested, I've finished a major overhaul of the client at:
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490121
]
Ryan McKinley commented on SOLR-20:
---
For now, I'd still recommend using solr-client.zip
The code on solrstuff.o
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490117
]
Will Johnson commented on SOLR-20:
--
is there an updated package or anyone working on such a thing at the moment?
the
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488702
]
carlos orrego commented on SOLR-20:
---
I am using the client library nad have no issues with adding docs to solr. But
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Lei updated SOLR-20:
-
Attachment: solrclient_addqueryfacet.zip
org.apache.solr.client.impl.ResultsParser.java
On 3/22/07, Thierry Collogne (JIRA) <[EMAIL PROTECTED]> wrote:
I think that is all. If I forgot something, post it here. One remark. The
setHighlightSurroundingTags method can only take simple tags,
no tags containing quotes or such.
Out of curiosity, why is this? Solr should be able to handl
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483051
]
Thierry Collogne commented on SOLR-20:
--
I found that there was no way of adding highlight paramters to an
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478810
]
Frederic Hennequin commented on SOLR-20:
Hello, we have been testing the solr-client and think we have found a
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474078
]
Ryan McKinley commented on SOLR-20:
---
I don't think this one is quite ready to go, but anyone interested can s
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474032
]
Erik Hatcher commented on SOLR-20:
--
My bad... it was SOLR-86 that interested me, and I've just committed it.
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474012
]
Erik Hatcher commented on SOLR-20:
--
I want this on trunk also. I'll be reviewing it and testing it out
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473993
]
rubdabadub commented on SOLR-20:
Hi:
I was really hoping that this patch will make it to trunk soon. I been using it
On 1/25/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: IMO, we should strive to be nice and not repeat keys when the
: NamedList is more of the Map variety than the List.
we should try .. but we can't garuntee .. i don't have any compelling
cases where i've needed to reuse the same name, but
: IMO, we should strive to be nice and not repeat keys when the
: NamedList is more of the Map variety than the List.
we should try .. but we can't garuntee .. i don't have any compelling
cases where i've needed to reuse the same name, but i've certainly written
plenty of code that puts multiple
On 1/25/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: I'm using a slightly modified version of the json.org code. It stores
: things in a LinkedHashMap (to maintain order) and formats dates
: explicitly.
Uh... watch out with that ... a LinkedHashMap is first and for most a Map,
so it doesn't
: > > * I'm using wt=JSON rather then XML. (It maps to a hash easier)
: I'm using a slightly modified version of the json.org code. It stores
: things in a LinkedHashMap (to maintain order) and formats dates
: explicitly.
Uh... watch out with that ... a LinkedHashMap is first and for most a Map
Hoss's point #4 on
https://issues.apache.org/jira/browse/SOLR-20#action_12464641 too
seriously. My revised version is designed totally around Requests
processing a handler's response. The server does not even know what
handlers it may be running - it is just the transport layer between
t
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.
On Jan 24, 2007, at 6:53 PM, Ryan McKinley wrote:
new SolrPing().process( server );
doesn't
server.ping();
look cleaner?
//Ed
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 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 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
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
> * 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-
[
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 us
[
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
: Do you think the package name should change?
:
: org.apache.solr.client.SolrClient
: vs
: org.apache.solr.client.solrj.SolrClient;
yeah ... that way if down the road someone comes up with a radically new
Java API (that we can't even fathom yet) they can call it "solrad" and put
it in clients/ja
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464648
]
J.J. Larrea commented on SOLR-20:
-
Regarding Hoss' point #3, perhaps it's time to reorganize into something l
olrj
ResultsParser class currently having a single public method...
agreed. i'll remove the XML exceptions...
- - - - -
Thanks for your feedback. I apologize for filling up your inbox these
past few days!
thanks
ryan
On 1/14/07, Hoss Man (JIRA) <[EMAIL PROTEC
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-20:
-
Summary: A simple Java client for updating and searching (was: A simple
Java client with Java APIs for add
On Sat, 2007-01-06 at 23:56 -0800, Ryan McKinley wrote:
> I just posted a solr client that does search and update to SOLR-20.
>
> With the addition of:
> \solr\client\ruby\solrb
>
> it seems appropriate to put this (or equivalent) in:
> \solr\client\java\solrj
>
>
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463372
]
Ryan McKinley commented on SOLR-20:
---
added APL to zip
> A simple Java client with Java APIs for add(), del
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-20:
--
Attachment: solr-client.zip
> A simple Java client with Java APIs for add(), delete(), commit()
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SOLR-20:
Component/s: (was: update)
clients - java
> A simple Java client w
On Jan 7, 2007, at 2:56 AM, Ryan McKinley wrote:
I just posted a solr client that does search and update to SOLR-20.
With the addition of:
\solr\client\ruby\solrb
it seems appropriate to put this (or equivalent) in:
\solr\client\java\solrj
It all depends on what else you have in mind for
I just posted a solr client that does search and update to SOLR-20.
With the addition of:
\solr\client\ruby\solrb
it seems appropriate to put this (or equivalent) in:
\solr\client\java\solrj
This version only depends on xpp3-1.1.3.4.O.jar. It is currently
using the
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462800
]
Ryan McKinley commented on SOLR-20:
---
I just posted a new version of a java client. This moves things to proper
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-20:
--
Attachment: solr-client.zip
> A simple Java client with Java APIs for add(), delete(), commit()
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12461517 ]
Fuad Efendi commented on SOLR-20:
-
My previous comment is visible to jira-users only, sorry.
Code submitted by Ryan looks great!
> A simple Java client with J
[ http://issues.apache.org/jira/browse/SOLR-20?page=all ]
Ryan McKinley updated SOLR-20:
--
Attachment: solr-client.zip
I've attached the client code i have written that merges SOLR-20 & SOLR-30. It
can add, delete, commit, optimize and search.
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12461050 ]
Fuad Efendi commented on SOLR-20:
-
SOLR-20: add, delete, commit, optimize
SOLR-30: search
So, should be merged.
HttpClient seems to be right choice (easily
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12457598 ]
Otis Gospodnetic commented on SOLR-20:
--
SOLR-20 and SOLR-30 seem to be lingering in JIRA.
Is the plan to merge them, and get the code into Solr?
> A simple J
On 11/22/06, Walter Underwood <[EMAIL PROTECTED]> wrote:
> I took pains to make things streamable.. I'd hate to discard that.
> How do other servers handle streaming back a response and hitting an error?
Does Lucene access fetch information from disk while we iterate
through the search results?
On 11/20/06 5:51 PM, "Yonik Seeley" <[EMAIL PROTECTED]> wrote:
>> : If you really want to handle failure in an error response, write that
>> : to a string and if that fails, send a hard-coded string.
>>
>> Hmmm... i could definitely get on board an idea like that.
>
> I took pains to make things
>turning a plain-text stack trace into a XML
>or JSON stack trace doesn't seem like a big win.
Some errors have business meaning.
'XML/JSON stack trace' IS a stack trace IIF it is not related to business
rules violation. If it is a business rule violation - it is neither 'stack
trace' nor HTTP er
On 11/20/06, Fuad Efendi <[EMAIL PROTECTED]> wrote:
Here, we are passing 'Empty Query' error message with a full stack trace as
an entity body of HTTP 404 response.
It's actually returning 400:
$ curl -i http://localhost:8983/solr/select/
HTTP/1.1 400 Bad Request
Date: Tue, 21 Nov 2006 03:56:3
>On the update side of things, I think it would be nice if one could
>check the HTTP status code and if it's OK (200), don't bother XML
>parsing the body.
Do you mean 304 'Not Modified'? Agree, we should handle it in SOLR (it is
not SOAP indeed!); we should handle 'last modified', 'expiration' et
One way to think about this is to assume caches, proxies, and load balancing
in the HTTP path, then think about their behavior. A 500 response may make
the load balancer drop this server from the pool, for example. A 200 OK
can be cached, so temporary errors shouldn't be sent with that code.
On 11
: "/solr/select?q=" is a tricky case. Three options:
...there's kind of a chicken/egg problem with this discussion ... the egg
being "what should the HTTP response look like in an 'error' situation"
the chicken being "what is the internal API to allow a RequestHandler to
denote an 'error' situati
On 11/20/06 5:51 PM, "Yonik Seeley" <[EMAIL PROTECTED]> wrote:
> Now that I think about it though, one nice change would be to get rid
> of the long stack trace for 400 exceptions... it's not needed, right?
That is correct. A client error (400) should not be reported with a
server stack trace. --
On 11/20/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: Wow, i had completley forgotten that SolrException contained an HTTP
: status code.
Hmmm... acctually, the javadocs for SolrException are a little vague on
the meaning of "code" and there are at least a few places where it's set
to a valu
On 11/20/06, Walter Underwood <[EMAIL PROTECTED]> wrote:
Even without a crawler, we must work with caches and load balancers.
I will be using Solr with a load balancer in production. If Solr is
a broken HTTP server, we will have to build something else.
Agree. Every instance of Solr in CNET th
: Wow, i had completley forgotten that SolrException contained an HTTP
: status code.
Hmmm... acctually, the javadocs for SolrException are a little vague on
the meaning of "code" and there are at least a few places where it's set
to a value that is not a legal HTTP status code...
./src/java/org
On 11/20/06 7:22 PM, "Fuad Efendi" <[EMAIL PROTECTED]> wrote:
> This is just a sample...
>
> 1. What is an Error?
> 2. What is a Mistake?
> 3. What is an application bug?
> 4. What is a 'system crash'?
These are not HTTP concepts. The request on a URI can succeed or fail
or result in other codes.
: In my simplistic Cocoon-based form, end-user gets HTTP 400 when Cocoon tries
: to query http://localhost:8983/solr/select/?q= (empty query; but I have
: workaround in query.js JavaScript); obviously this is not a bug in SOLR
: neither it is an unrecoverable system error nor any kind of HTTP erro
Intresting...
I'd suggest to return 200 with XML-Response in case of any SOLR-related
problem (and leave some job to Tomcat).
Of course if our crawler do not use 'If-modified-since' (such HTTP should be
handled by 'front-end'/httpd/firewall/proxy before reaching JEE/SOLR
container)... We are mix
: > We should probably separate business-related end-user errors (such as
when
: > user submits empty query) and make it XML-like (instead of HTTP 400)
I want to make it more clear... we need to separate errors (end-user
mistakes) from application bugs (exceptions) and from fatal errors (HTTP
Tran
: > We should probably separate business-related end-user errors (such as when
: > user submits empty query) and make it XML-like (instead of HTTP 400)
:
: Speaking as a former web spider maintainer, it is very important to keep
: the HTTP response codes accurate. Never return an error with a 200.
On 11/17/06 2:50 PM, "Fuad Efendi" <[EMAIL PROTECTED]> wrote:
>
> We should probably separate business-related end-user errors (such as when
> user submits empty query) and make it XML-like (instead of HTTP 400)
Speaking as a former web spider maintainer, it is very important to keep
the HTTP resp
http://localhost:8983/solr/select/?q={request-param:query}"/>
context://samples/solr/example.xsl - copied from SOLR distribution
--
View this message in context:
http://www.nabble.com/Co
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12450843 ]
Hoss Man commented on SOLR-20:
--
I don't know that there is a specific "right" one at the moment ... Darren's
last comment suggests that he has a bet
JIRA
database for unresolved bugs in Cocoon, found some messages about bad
performance of CInclude Transformer... simples task, but I need to do many
transformations to add dynamic...
Using pure JSP I could done the same just within an hour! and spend saved
time with Facets.
My votes for SOLR-20
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12449911 ]
David Halsted commented on SOLR-20:
---
it is a little confusing -- any chance one of the attachments could be
designated as the right one? Thanks!
> A simple J
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12447549 ]
Fuad Efendi commented on SOLR-20:
-
I'm dieing... which files should I download?
> A simple Java client with Java APIs for add(), delete(), commit() and
&g
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12438790 ]
Yonik Seeley commented on SOLR-20:
--
Ping...
any chance you could make your latest version available?
> A simple Java client with Java APIs for add(), del
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12428555 ]
Darren Erik Vengroff commented on SOLR-20:
--
Please ignore that last attachment. It contains an earlier version of the code
than I intended, and has a
[ http://issues.apache.org/jira/browse/SOLR-20?page=all ]
Darren Erik Vengroff updated SOLR-20:
-
Attachment: solr-client-sources.jar
Here is the latest version of the client code, in the form of
solr-client-source.jar. The big difference here is
[ http://issues.apache.org/jira/browse/SOLR-20?page=all ]
Darren Erik Vengroff updated SOLR-20:
-
Attachment: solr-client-java-2.zip.zip
Good catch Philip. For the benefit of future downloaders, here's a complete
zip file with everything incl
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12421774 ]
Philip Jacob commented on SOLR-20:
--
delete() in the DocumentManagerClient ought to be doing this:
1234
It's currently doing this:
1234
> A simple Jav
[
http://issues.apache.org/jira/browse/SOLR-20?page=comments#action_12415247 ]
Yonik Seeley commented on SOLR-20:
--
Great! Now we need to figure out where it lives, and how to work out the
dependencies (a solr-util.jar that a client could use, or perhaps
1 - 100 of 122 matches
Mail list logo
