On Mar 9, 2007, at 6:46 AM, rubdabadub wrote:
On 3/9/07, Erik Hatcher [EMAIL PROTECTED] wrote:
We use jetty on a few applications with no problem. I recommend it
unless and until you outgrow it (but I doubt you will). Resin, in
my past experience with it, is fantastic. But no need to even
On 3/9/07, rubdabadub [EMAIL PROTECTED] wrote:
...The site is a local portal and the traffic is very high and I am not
sure if Jetty is enough maybe it is
Just an additional note on this: asking four people about what very
high traffic means might also give you five different answers ;-)
I use jetty and tomcat 6 under win2003.
They all work well.
2007/3/10, Bertrand Delacretaz [EMAIL PROTECTED]:
On 3/9/07, rubdabadub [EMAIL PROTECTED] wrote:
...The site is a local portal and the traffic is very high and I am not
sure if Jetty is enough maybe it is
Just an
Thanks for the feedback! I was planning to test but I wanted to know what
other were using. I have been using tomcat extensively but got tired of it (no
technical reason).
Jetty sounds too simple so I thought I ask :-) Never tried Resin but it has some
good reputation.
The local portal is using
Hi,
I've been working on adding some Solr-integration into my current project, but
have run into a problem with non-ascii characters.
I send a document like the following:
---
?xml version=1.0 encoding=UTF-8?
adddoc
field name=question_id228/field
field name=question_titleVedhæft billede
On Saturday 10 March 2007 21:39, Bertrand Delacretaz wrote:
On 3/10/07, Morten Fangel [EMAIL PROTECTED] wrote:
...I send a document like the following:
---
?xml version=1.0 encoding=UTF-8?...
I assume you're using your own code to send the document?
Indeed. Solr will be integrated
It is better to use application/xml. See RFC 3023.
Using text/xml; charset=UTF-8 will override the XML
encoding declaration. application/xml will not.
wunder
On 3/10/07 12:39 PM, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
On 3/10/07, Morten Fangel [EMAIL PROTECTED] wrote:
...I send a
On Saturday 10 March 2007 22:18, Walter Underwood wrote:
It is better to use application/xml. See RFC 3023.
Using text/xml; charset=UTF-8 will override the XML
encoding declaration. application/xml will not.
Thanks for the info. I've changed the header accordingly.
-fangel
On 3/10/07, Walter Underwood [EMAIL PROTECTED] wrote:
It is better to use application/xml. See RFC 3023.
Using text/xml; charset=UTF-8 will override the XML
encoding declaration. application/xml will not...
I agree, but did you try this with our example setup, started with
java -jar start.jar?
If it does something different, that is a bug. RFC 3023 is clear. --wunder
On 3/10/07 1:49 PM, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
On 3/10/07, Walter Underwood [EMAIL PROTECTED] wrote:
It is better to use application/xml. See RFC 3023.
Using text/xml; charset=UTF-8 will override the
On 3/10/07, Walter Underwood [EMAIL PROTECTED] wrote:
If it does something different, that is a bug. RFC 3023 is clear. --wunder..
Sure - just wanted to confirm what I'm seeing, thanks!
-Bertrand
How can i boost some tokens over others in the same field (at Index
time) ? If this is not supported directly, what's the best way around
this problem (what's the hack to solve this :) ).
Thanks,
Shai
What are you trying to achieve? Let's start with the problem
instead of picking one solution which Solr doesn't support. --wunder
On 3/10/07 5:08 PM, shai deljo [EMAIL PROTECTED] wrote:
How can i boost some tokens over others in the same field (at Index
time) ? If this is not supported
Venkatesh Seetharam wrote:
The hash idea sounds really interesting and if I had a fixed number of
indexes it would be perfect.
I'm infact looking around for a reverse-hash algorithm where in given a
docId, I should be able to find which partition contains the document
so I
can save
14 matches
Mail list logo
