We are planning to incorporate both your requests in the next patch.
The implementation is going to be as follows.mention the xsl file
location as follows
entity processor=XPathEntitityprocessor xslt=file:/c:/my-own.xsl
/entity
So the processing will be done after the XSL transformation. If
Cool. So you're saying that this xslt file will operate on the entire XML
document that was fetched from the URL and just pass it on to solr? Thanks
for supporting this. The XML files I have coming from the my data source
are big but not not too big to risk an out-of-memory error. And I've
Hi all
in my schema.xm I have follwing entry
copyField source=username dest=usernameSort/
but the problem I am facing that when i sort it on usernameSort it does case
sensitive sorting.. i.e firslt uppercase then lowercase.
I want to do case insensitive sorting. Is there anyway when i copyField
In your schema.xml, make sure the type specified for usernameSort field has
the LowerCaseFilterFactory applied on it.
On Mon, Apr 21, 2008 at 9:34 PM, Ismail Siddiqui [EMAIL PROTECTED] wrote:
Hi all
in my schema.xm I have follwing entry
copyField source=username dest=usernameSort/
but the
Hi HH,
Here's a note I sent Solr-dev a while back:
---
I've implemented a Solr plug-in that wraps KStem for Solr use (someone
else had already written a Lucene wrapper for it). KStem is considered
to be more appropriate for library usage since it is much less
aggressive than Porter (i.e.,
Hey-
to create an issue, make an account on jira and post it...
https://issues.apache.org/jira/browse/SOLR
Give that a try and holler if you have trouble.
ryan
On Apr 21, 2008, at 12:31 PM, Wagner,Harry wrote:
Hi HH,
Here's a note I sent Solr-dev a while back:
---
I've implemented a Solr
Michael,
To answer your questions:
I completely deleted the index each time before retesting.
and the java command as shown by ps does show -Xbatch.
The program is running on:
uname -a
Linux lab8.betech.virginia.edu 2.6.18-53.1.14.el5 #1 SMP Tue Feb 19
07:18:21 EST 2008 i686 i686
Hi all,
In the latest trunk version, default='true' doesn't have the effect I
would have expected running in multi core mode.
The example multicore.xml has:
core name=core0 instanceDir=core0 default=true/
core name=core1 instanceDir=core1 /
But queries such as
/solr/select?q=*:*
and
On Mon, Apr 21, 2008 at 4:13 PM, Jim Adams [EMAIL PROTECTED] wrote:
Could you point me to an example somewhere?
The command line tool curl can do either GET or POST:
curl http://localhost:8983/solr/select --data 'q=foorows=100'
-Yonik
: to create an issue, make an account on jira and post it...
: https://issues.apache.org/jira/browse/SOLR
:
: Give that a try and holler if you have trouble.
To elaborate more (and save some time on the question answering of the
correct procedures) ...
Michael,
Following up on this most recent post. I remembered that the initial
records were translated into utf-8 prior to indexing, whereas the
updates records are in the marc-8 encoding internally, and the program
is written to translate them on the fly as they are read in before
indexing
Is it possible to boost the query that MoreLikeThis returns before
sending it to Solr? I mean, technically is possible, because you can add
a factor to the whole query but...does it make sense? (Remember that
MoreLikeThis can already boosts each term inside the query).
For example, this could
Could you point me to an example somewhere?
Thanks!
On Wed, Apr 16, 2008 at 10:08 PM, Chris Hostetter [EMAIL PROTECTED]
wrote:
: I know there is a 'GET' to send queries to Solr. But is there a POST
: interface to sending queries? If so, can someone point me in that
: direction?
POST
hymmm -- default should be removed and should not do anything.
The intended behavior is that /solr/select?q=*:* should be 404, you
would need to call
/solr/core0/select or /solr/core1/select to get anything.
So yes, this is a bug. I'll remove the old default=true bit and
file a bug to
14 matches
Mail list logo
