Hi James,
the problem is most likely a xml error in either schema.xml or
solrconfig.xml. Go through your Tomcat logs, if it is an xml error you
should find the line where the xml parsing went wrong.
Kind regards,
Nick
On 9/18/06, James liu <[EMAIL PROTECTED]> wrote:
thk Nick.
i do you tell
Hi Nick,
It is very funny. when i reboot my pc,it is ok and i do nothing.
my new question is how to add lucene-analyzers-2.0.0.jar to tomcat or jetty.
i add useful classes to solr.war which exist
"C:\cygwin\tmp\solr-nightly\example\webapps\solr.war",,,but it is not
effect...
do u know how to s
Additionally, we should mock out for testing reasons, e.g. in file
test/mocks/test/acts_as_solr.rb:
require "#{File.dirname(__FILE__)}/../../../vendor/plugins/
acts_as_solr/lib/acts_as_solr.rb"
module SolrMixin #:nodoc:
module Acts #:nodoc:
module ARSolr #:nodoc:
i look expression about them in schema.xml.
but i m not clear.
My
understand: if sortMissingLast is true do last in descending sort. for example:
field name : pname, if sortMissingLast is true, pname will be sorted desc
and we can't find result with pname, only other field information.
am i w
not find example in wiki.
anyone know?
--
regards
jl
: My
: understand: if sortMissingLast is true do last in descending sort. for
example:
: field name : pname, if sortMissingLast is true, pname will be sorted desc
: and we can't find result with pname, only other field information.
sortMissingLast is used to determine how you want documents t
: Subject: no example to CollectionDistribution?
:
: not find example in wiki.
:
:
: anyone know?
you really need to be more specific James: what kinds of examples are you
looking for? ... the CollectionDistribution describes in depth how the
replication/distribution works, and has examples of t
Hi, I wanted to inquire if anybody would find an update flag useful that
only replaced the subset of data (ie a certain field) getting passed in,
instead of the whole record.
Pseudo-code for what I'm describing:
125125
true
+ RU
- EN
I'm not into the code of Solr at all but I know that Solr is based on
the lucene core which has no kind of update mechanism. To update a
document using lucene you have to delete and reinsert the document.
That might be the reason for the solr behaviour as well.
You should consider that lucene is
maybe i should get cron through cygwin..
my system is win2003,not unix.
today i try ./snappuller,,,but it seems wrong and i set master port,
directory,snap directory
tomorrow i will try again.
2006/9/18, Chris Hostetter <[EMAIL PROTECTED]>:
: Subject: no example to CollectionDistribut
Hi James,
I also needed the DutchAnalyzer from Lucene in my Solr project. I did it the
following way. Which is probably the hard way, because my Java knowledge
isn't that great.
1. I unzipped the solr-nightly build
2. I downloaded the latest code from lucene, preferrably from svn :
http://svn.ap
Been playing around with the news 'facets search' and it works very
well, but it's really slow for some particular applications. I've been
trying to use it to display the most frequent authors of articles; this
is from a huge (15 millions articles) database and names of authors are
rare and het
Just a little follow-up - I did a little more testing, and the query
takes 20 seconds no matter what - If there's one document in the results
set, or if I do a query that returns all 13 documents.
It seems something isn't right... it looks like solr is doing faceted
search on the whole ind
thank u, with your step and add junit, it is ok.
you can analyzer your language?
i modify schema:
but nothing changed.
2006/9/19, Nick Snels <[EMAIL PROTECTED]>:
Hi James,
I also needed the DutchAnalyzer from Lucene in my Solr
On 9/18/06, Michael Imbeault <[EMAIL PROTECTED]> wrote:
Been playing around with the news 'facets search' and it works very
well, but it's really slow for some particular applications. I've been
trying to use it to display the most frequent authors of articles
I noticed this too, and have been
On 9/18/06, Michael Imbeault <[EMAIL PROTECTED]> wrote:
Just a little follow-up - I did a little more testing, and the query
takes 20 seconds no matter what - If there's one document in the results
set, or if I do a query that returns all 13 documents.
Yes, currently the same strategy is al
Yonik Seeley wrote:
I noticed this too, and have been thinking about ways to fix it.
The root of the problem is that lucene, like all full-text search
engines, uses inverted indicies. It's fast and easy to get all
documents for a particular term, but getting all terms for a document
documents is
Another followup: I bumped all the caches in solrconfig.xml to
size="1600384"
initialSize="400096"
autowarmCount="400096"
It seemed to fix the problem on a very small index (facets on last and
first author fields, + 12 range date facets, sub 0.3 seconds for
queries). I'll check
18 matches
Mail list logo
