:I would like to alter the similarity behaviour of solr to remove
: the fieldnorm factor in the similarity calculations. As far as I
: read, I need to recreate my own similarity class and import it into
: solr using the similarity config in schema.xml.
:
:Has anybody already tweaked or
Hi Chris,
thanks for the details, I am meanwhile poking around with my own
class which I defined in the schema.xml everything is working
perfectly there.
But I have still the problem with the normalization, I try to
change several parameters to fix it to 1.0, this does indeed change
Hi,
I have created a process which uses xsl to convert my data to the form
indicated in the examples so that it can be added to the index as the solr
tutorial indicates:
add
doc
field name=fieldvalue/field
...
/doc
/add
In some cases the xsl process will create a field
Thanks Yonik,
That's exactly what I needed to know. I'll adapt my xsl process to
omit null values.
Tricia
On Thu, 27 Jul 2006, Yonik Seeley wrote:
On 7/27/06, Tricia Williams [EMAIL PROTECTED] wrote:
Hi,
I have created a process which uses xsl to convert my data to the form
Solr now has a JSON response format, in addition to Python and Ruby
versions that can be directly eval'd.
http://wiki.apache.org/solr/SolJSON
-Yonik
On 7/26/06, sangraal aiken [EMAIL PROTECTED] wrote:
I removed everything from the Add xml so the docs looked like this:
doc
field name=id187880/field
/doc
doc
field name=id187852/field
/doc
and it still hung at 6,144...
Maybe you can try the following simple Python client to try and rule
out
On 7/27/06, Yonik Seeley [EMAIL PROTECTED] wrote:
class SolrConnection:
def __init__(self, host='localhost:8983', solrBase='/solr'):
self.host = host
self.solrBase = solrBase
#a connection to the server is not opened at this point.
self.conn = httplib.HTTPConnection(self.host)
Hi Sangraal:
Sorry--I tried not to imply that this might affect your issue. You
may have to crank up the solr logging to determine where it is
freezing (and what might be happening).
It is certainly worth investigating why this occurs, but I wonder
about the advantages of using such huge
Yeah, I'm closing them. Here's the method:
-
private String doUpdate(String sw) {
StringBuffer updateResult = new StringBuffer();
try {
// open connection
log.info(Connecting to and preparing to post to SolrUpdate
servlet.);
URL url = new
I haven't been following the thread, but
Not sure if you are using Tomcat or Jetty, but Jetty has a POST size limit (set
somewhere in its configs) that may be the source of the problem.
Otis
P.S.
Just occurred to me.
Tomcat. Jetty. Tom Jerry. Jetty guys should have called their thing
I'm running on Tomcat... and I've verified that the complete post is making
it through the SolrUpdate servlet and into the SolrCore object... thanks for
the info though.
--
So the code is hanging on this call in SolrCore.java
writer.write(result status=\ + status + \/result);
The
You might also try the Java update client here:
http://issues.apache.org/jira/browse/SOLR-20
-Yonik
On 7/27/06, sangraal aiken [EMAIL PROTECTED] wrote:
Commenting out the following line in SolrCore fixes my problem... but of
course I don't get the result status info... but this isn't a problem for me
really.
-Sangraal
writer.write(result status=\ + status + \/result);
While it's possible
I'll give that a shot...
Thanks again for all your help.
-S
On 7/27/06, Yonik Seeley [EMAIL PROTECTED] wrote:
You might also try the Java update client here:
http://issues.apache.org/jira/browse/SOLR-20
-Yonik
14 matches
Mail list logo
