It's all about "sol(a)r", ya know? More day light, please!
Hi,
I'm trying to integrate the Lucene-based spellchecker
(http://wiki.apache.org/jakarta-lucene/SpellChecker + contrib/spellchecker
under Lucene) with Solr (http://issues.apache.org/jira/browse/SOLR-81) in order
to provide a query spellchecking service (you enter Speers and it suggest
pant^H^H
: Thanks. The problem is, it is not easy to do an incremental update on the
: data set.
: In which case, I guess the index needs to be created in a different path and
: we need to move
: files around. However, since the documents are added over HTTP, how does one
: even create
: the index in a dif
i use fb 6.1
when i use
# sh rsyncd-enable
it show me：
cd: can't cd to rsyncd-enable/..
.: Can't open /usr/local/www/data/solr/example/solr/bin/bin/scripts-util: No
such file or directory
--
regards
jl
: I guess the updates can also be done the same way then. So, I just have
: to create multiple context paths with different schema.xml files in each ?
: Thanks.
you wouldn't even need idffernet schema.xml files ... they could all be
symlinks to the same schema.xml, only the data directories would
the wiki shows how to configure everything. see "Multiple Solr Webapps" on:
http://wiki.apache.org/solr/SolrTomcat
http://wiki.apache.org/solr/SolrJetty
http://wiki.apache.org/solr/SolrResin
On 12/21/06, escher2k <[EMAIL PROTECTED]> wrote:
I guess the updates can also be done the same way
I guess the updates can also be done the same way then. So, I just have
to create multiple context paths with different schema.xml files in each ?
Thanks.
ryan mckinley wrote:
>
> You can run multiple webapps on a single app server (running on a single
> port). Just give each index a seperate
You can run multiple webapps on a single app server (running on a single
port). Just give each index a seperate context path. for example, you
could have:
http://xyz:8765/index1/select/?q=xxx
http://xyz:8765/index2/select/?q=xxx
http://xyz:8765/index3/select/?q=xxx
On 12/21/06, escher2k <[E
There would have to be only one app server running on a single port and
adding new indexes
is pretty easy. Currently we have four separate indexes which we run off of
Lucene using Jakarta
and the index to use is read from a config file. This definitely seems
easier from a management perspective.
What is the advantage to running multiple indexes from a single Solr
instance over multiple Solr instances each serving a single index?
Erik
On Dec 21, 2006, at 3:26 PM, escher2k wrote:
I looked at the forums and found that it is not possible to have
multiple
indexes associated w
Thanks. The problem is, it is not easy to do an incremental update on the
data set.
In which case, I guess the index needs to be created in a different path and
we need to move
files around. However, since the documents are added over HTTP, how does one
even create
the index in a different path on
On 12/21/06, escher2k <[EMAIL PROTECTED]> wrote:
Hi,
We currently use Lucene to do index user data every couple of hours - the
index is completely rebuilt,
the old index is archived and the new one copied over to the directory.
Example -
/bin/cp ${LOG_FILE} ${CRON_ROOT}/index/help/
/bin/rm -r
I looked at the forums and found that it is not possible to have multiple
indexes associated with one app server instance ? Is the best way to run
multiple app server instances ? It would be a nice enhancement to support
parameterization of the index to be used.
--
View this message in context:
Hi,
We currently use Lucene to do index user data every couple of hours - the
index is completely rebuilt,
the old index is archived and the new one copied over to the directory.
Example -
/bin/cp ${LOG_FILE} ${CRON_ROOT}/index/help/
/bin/rm -rf ${INDEX_ROOT}/archive/help.${DATE}
/bin/cp -R ${C
14 matches
Mail list logo
