Yep, I get it. But from the tests I did it tips it enough for those
cases to be rare (and probably justified).
Thx
On 3/19/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: wouldn't doing something like this in the query :
: (field1:tag1 tag2) OR (field1:tag1 AND tag2)
: The documents that have
: I surrounded the html with the following:
:
This is not a safe way to XML encode arbitrary text ... CDATA is
automaticly closed when ]]> is encountered .. in your case, the HTML page
itself contains the sequence "]]>" inside of a tag ... so the
parser is assuming everything after that is part
I'm trying to put this html page into my solr instance.
http://creditboards.com/forums/index.php?showtopic=30893
http://creditboards.com/forums/index.php?showtopic=30893
I surrounded the html with the following:
Then I got the XmlPullParserException. If you take a close look at the
source of
: it would maybe be a good idea to have Lucene check the *stored* value for
: duplicate keys ... that seems so much more logical to me !
: (imho, it makes no sense to check the *indexed* value for duplicate keys,
: but maybe there is a reason ?)
it's probably a terminology issue ... stored fields
: So (at least in theory - I haven't tried it) you should be able to use
: Saxon instead of the standard XSLT library, by making the Saxon jars
: available to your Solr instance, and configuring which
: TransformerFactory to use as described for example in:
the normal plugin lib directory might n
: So I probably got that wrong, with the multivalued fields. I thought
: they not only not throw an error but really index both values.
: What happens when I use a multivalue field and that is field appears two
: times in a add/update doc? Is the second value lost?
sorry ,i guess i should have cl
: handler by name) in the solrconfig.xml file, or does this require me to
: write a custom RequestHandler in java to perform this?
it would be a custom java class that you could load at runtime by putting
in the "lib" directory and refering to it in your solrconfig.xml (ie: no
modifications necce
Thanks for the help Bertrand. It was very easy to move it over. I
updated the Wiki page.
Solr grouping ahoy!
http://wiki.apache.org/solr/XsltResponseWriter
On Mar 19, 2007, at 4:59 AM, Bertrand Delacretaz wrote:
On 3/16/07, Brian Whitman <[EMAIL PROTECTED]> wrote:
...It's my understandi
:
: I have the following Query:
: q=field1:tag1 tag2^0.5 OR field2:tag1
: tag2^0.5&version=2.2&start=0&rows=170&indent=on&fl=*,score
:
: And i want to do :
: 1. Return back ONLY documents that contain both tag1 AND tag2 in
: field1. when i try using Lucene syntax (+tag1 or +(tag1)) i get an
: excep
: wouldn't doing something like this in the query :
: (field1:tag1 tag2) OR (field1:tag1 AND tag2)
: The documents that have all the tags (tag1 and tag2) will comply with
: both conditions and get scores from both while the documents that
: don't have both tags will only get a score from the 1st
On Mar 19, 2007, at 11:05 AM, Otis Gospodnetic wrote:
If you can run your app on Rails, look at Flare: http://
wiki.apache.org/solr/Flare
Indeed. Flare is _designed_ to be a Solr UI in Rails. It currently
is fairly rudimentary, though we now have solid faceted browsing,
full-text search
If you can run your app on Rails, look at Flare:
http://wiki.apache.org/solr/Flare
It would be gool to gave a Grails version of Flareif anyone has extra time
on their hands...hah.
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Se
Hello
I would like to build a simple web front end (e.g. google.com) for the
users of solr. Which is the best way to archive this goal? Has someone
already built a simple query interface (gui)?
My query interface should have:
- paging
- summary of documents with the relevant search terms
- hi
thanks for your reply... it kind of solved our problem !
we were in fact using Tokenizers that produce multiple tokens ...
so i guess there is no other way for us then to use the copyfield
workaround.
it would maybe be a good idea to have Lucene check the *stored* value for
duplicate keys ...
On 3/16/07, Brian Whitman <[EMAIL PROTECTED]> wrote:
...It's my understanding that the javax.xml.transform used by the
XSLTResponseWriter is 1.0 only-- at least, it does not understand any
of the 2.0 stuff I've thrown at it. I am new to world of XSL, thanks
to Solr, but it seems Saxon-B is a goo
Chris Hostetter schrieb:
> : I would be shocked if you noticed any performance difference between a
> : single-valued field and a multivalued field with one entry.
>
> there shouldnt' be any difference at all in search performance, or index
> size ... marking a field multiValued should only have t
16 matches
Mail list logo
