Thanks. I see. It seems that slf4j-nop-1.5.5.jar is the only jar file missing
in solrj-lib, so I suggest that it should be included in the next release.
Per Halvor
-Opprinnelig melding-
Fra: Chris Hostetter [mailto:hossman_luc...@fucit.org]
Sendt: 17. november 2009 20:51
Til:
Hi,
not sure this is something new in Solr 1.4, but I just noticed that
facets results are serialized differently with standard and dismax when
using wt=ruby.
Standard returns:
'my_facet'={'20344'=1}
Whereas dismax has:
'my_facet'=['20344',1]
Admittedly this is not a big deal, it's easy
Hello
I indexed an html document with a decimal HTML Entity encodings: the character
é (e with an acute accent) is encoded as #233; The exact content of the
document is:
htmlbody#231;a va m#233;m#233; ?/body/html
A search for 'mémé' returns no document. If I put the line above in solr
I have the following field configured in schema.xml:
field name=title type=text indexed=true stored=true
omitNorms=false boost=3.0 /
Where text is the type which came with the Solr distribution. I have
not been able to get this configuration to alter any document scores,
and if I look at the
Andrea,
I'd guess you have json.nl=arrarr set for your dismax handler (or
request).
Erik
On Nov 18, 2009, at 12:01 PM, Andrea Campi wrote:
Hi,
not sure this is something new in Solr 1.4, but I just noticed that
facets results are serialized differently with standard and dismax
Erik,
Erik Hatcher wrote:
Andrea,
I'd guess you have json.nl=arrarr set for your dismax handler (or
request).
sigh, you're right, sorry for the noise :/
Andrea
Hi,
I've played around with Solr's VelocityResponseWriter (which is indeed a
very useful feature for rapid prototyping). I've realized that Velocity
uses ISO-8859-1 as default character encoding. I've changed this setting
to UTF-8 in my velocity.properties file (inside the conf directory),
Hi Erik,
Erik Hatcher wrote:
Can you give me a test document that causes an issue? (maybe send me a
Solr XML document in private e-mail). I'll see what I can do once I
can see the issue first hand.
Thank you! Just try the utf8-example.xml file in the exampledoc
directory. After having
Solr includes slf4j-jdk14-1.5.5.jar, if you want to use the nop (or
log4j, or loopback) impl you will need to include that in your own
project.
Solr uses slf4j so that each user can decide their logging
implementation, it includes the jdk version so that something works
off-the-shelf,
Thanks
So going by you reply, can i assume that if there is a configuration change
to my schema I have to again index documents,
There is no short cut of updating the index.
Because we cant afford to index 2 million documents again and again.
There should be some utility or command line which
Specifying the file.encoding did work, although I don't think it is a suitable
workaround for my use case. Any idea what my next step is to having a bug
opened.
Thanks,
Joe
Date: Wed, 18 Nov 2009 16:15:55 +0530
Subject: Re: UTF-8 Character Set not specifed on OutputStreamWriter in
What platform are you using? Windows does not use UTF-8 by default,
and this can cause subtle problems. If you can do the same thing on
other platforms (Linux, Mac) that would help narrow down the problem.
On Wed, Nov 18, 2009 at 8:15 AM, Sascha Szott sz...@zib.de wrote:
Hi Erik,
Erik Hatcher
Ah, thanks for the tip about switching out the jdk jar with the
log4j jar. I think I was running into this issue and couldn't
figure out why Solr logging couldn't be configured when running
inside Hadoop which uses log4j, maybe this was the issue?
On Wed, Nov 18, 2009 at 9:11 AM, Ryan McKinley
Darniz,
Yes, if there is an incompatible schema change, you need to reindex your
documents.
Otis
P.S.
Please include the copy of the response when replying, so the
context/background of your question is easy to figure out.
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Your first definition of text_fr seems to be correct and should work
as expected. I tested it and worked fine (mémé was highlighted).
What was the output of HTMLStripCharFilterFactory in analysis.jsp?
In my analysis.jsp, I got ça va mémé ?.
Koji
Kundig, Andreas wrote:
Hello
I indexed an
Thanks for your reply. Nested boolean queries is a valid concern. I also
realized that isCoordDisabled needs to be considered in
BooleanQuery.hashCode so that a query with coord=false will have a different
cache key in Solr.
On Thu, Nov 12, 2009 at 12:12 PM, Chris Hostetter
16 matches
Mail list logo
