Hi,
Any ideas on how could we register single request handler for handling
multiple (wildcarded) contexts/resource uri's ?
(something like) :
requestHandler name=/app/* class=solr.StandardRequestHandler
requestHandler name=/app/*/query class=solr.StandardRequestHandler
Current logic in
Sure - overriding the SolrDispatchFilter seems like a right way to go
(especially maintenance-wise :) ).
Thanks :)
ps. - as far as the : - situation is concerned - that was useful -
but i guess it didn't look nice ;)
(anyway - i guess that the :-trim filter must have persisted there
in
Hi,
In such setup, you would definitely want to use zookeeper in
conjunction with Solr for at least two things :
a) deploy management / (having cron-based pulls for a 128-node setup
could be a nightmare without appropriate sync guarantees,
coordination, etc)
b) configuration distribution
Hi !
For custom faceting of numerical fields (and similar applications), it
would be super-useful if the list of terms for each numerical field in
the index
(accessible via FieldCache.StringIndex.lookup), could be stored in
numerical rather than natural (alphabetical) order.
(For example
Ah, indeed :)
Thanks,
.Alek
On Oct 14, 2008, at 3:21 PM, Steven A Rowe wrote:
Hi Alek,
On 10/13/2008 at 8:29 PM, Aleksandar Bradic wrote:
For custom faceting of numerical fields (and similar
applications), it would be super-useful if the list of
terms for each numerical field in the index
Hi all,
Any ideas on how to use custom Lucene Filter (lucene.search.Filter) in
conjuction with SolrIndexSearcher ?
The case is writing custom Filter performing arbitrary records
selection and AND-ing it to the existing filters passed in the query.
However, the ResponseBuilder filters are
Ah, right.
FilteredQuery works just great
Thanks, Yonik
Best,
.Alek
On Jun 16, 2009, at 9:45 PM, Yonik Seeley wrote:
On Tue, Jun 16, 2009 at 3:31 PM, Aleksandar
Bradicaleksan...@vast.com wrote:
Any ideas on how to use custom Lucene Filter (lucene.search.Filter)
in
conjuction with
