: I'm wondering if it's possible to run a POST instead of a GET when querying
: Solr, or does this need to be custom coded? Seems like this might be a way
: to get around it.
Yep, Yonik fixed this arround April 7th, Jira's down right now, but it was
tracked in SOLR-7...
http://issues.ap
I'm attempting to send a very long / large query to Solr and I'm
encountering an issue under Jetty for this query that I'm passing. It's
more than likely hitting a hard-coded somewhere for the maximum length of
the URL that was designed as a safety measure. I'm not sure if Tomcat
would fare diff
On 4/18/06, Vish D. <[EMAIL PROTECTED]> wrote:
> Do we have a eta on " Allow multiple independent Solr *webapps* in the same
> app server"?
We've been discussing it on solr-dev
http://www.mail-archive.com/solr-dev%40lucene.apache.org/msg00292.html
> But, it makes sense to run a comparison against
Yonik/Chris,
Do we have a eta on " Allow multiple independent Solr *webapps* in the same
app server"?
After reading up, silently, on the many emails on this topic, I agree with
you that it would be worthwhile to test out the current implementation and
see how it performs. But, it makes sense to r
: Maybe my code is out of date, but I didn't see /solr/conf being used
: as the path.
yeah .. this was changed starting with the 2006-04-01 nightly builds,
Yonik sent out an announcement about it on Mar31. That's when the "solr
home" concept was introduced, and the data directory was changed to
On 4/18/06, Ken Krugler <[EMAIL PROTECTED]> wrote:
2. Cloned/edited the resin.conf file to include a mapping for
Solr, by adding:
webapps/solr-nightly
I normally just copy the war to solr.war, so I don't need the mapping...
3. Started up Resin.
It created the
: Hoss, I've seen you mention "plugin" several times... I presume you
: mean a custom request handler. If not, could you elaborate on what
: you mean?
sorry, yes ... most generally I mean any code which doesn't ship with
Solr, but which is loaded into the JVM at Solr's request because of
configu
On Apr 18, 2006, at 1:22 PM, Yonik Seeley wrote:
On 4/18/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
To add to that: when thinking about "how clients will specify what
extra
info they want" we should consider not only external clients using
HTTP
and the StandardRequestHandler, but also wh
On 4/18/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> To add to that: when thinking about "how clients will specify what extra
> info they want" we should consider not only external clients using HTTP
> and the StandardRequestHandler, but also what the internal API looks like
> for people wantin
Hoss, I've seen you mention "plugin" several times... I presume you
mean a custom request handler. If not, could you elaborate on what
you mean?
Thanks,
Erik
On Apr 18, 2006, at 1:17 PM, Chris Hostetter wrote:
: Focus on the interface:
: - how clients will specify what extra in
: Focus on the interface:
: - how clients will specify what extra info they want
: - how clients typically parse and use the XML (extra bonus if we can
: make it semi-friendly to stylesheets/XSLT), and the ideal syntax for
: representing the extra info
To add to that: when thinking about "how c
Yonik is right. You wouldn't need the web-app configuration in resin.conf
if you rename solr-nightly.war to solr.war. Resin will expand all war files
in its webapps directory automatically.
For Resin, the default location for
conf files: /solr/conf
index directory: /solr/data
As Yonik has point
On 4/18/06, Ken Krugler <[EMAIL PROTECTED]> wrote:
> 2. Cloned/edited the resin.conf file to include a mapping for Solr, by adding:
>
>
> webapps/solr-nightly
>
I normally just copy the war to solr.war, so I don't need the mapping...
> 3. Started up Resin.
>
> It created t
Hi all, and especially Yonik :),
Just for grins, I'm trying Solr with Resin. I did the following:
1. Copied solr-nightly.war into /webapps/.
2. Cloned/edited the resin.conf file to include a mapping for Solr, by adding:
webapps/solr-nightly
3. Started up Resin.
It creat
On 4/17/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
> The current situation with XMLWriter actually pulling the Document
> from the index
Yeah, but seeing people ask for *all* matching documents (or sometimes
evel all documents in the index), makes me think that we need to keep
streamability.
> c
15 matches
Mail list logo
