On Wed, Jul 22, 2009 at 11:35 AM, Grant Ingersoll wrote:
>> My initial thoughts are to index each description as a separate field and
>> append the language identifier to the field name, for example, three
>> fields
>> with description_en, description_de, descrtiption_fr. Is this the best
>> appro
On Wed, Jul 22, 2009 at 10:44 AM, Jeff Newburn wrote:
> How do I go about enabling the gc logging for solr?
It depends how you are running solr. You basically want to make sure
that when the JVM is started up with the java command, that it gets
some additional arguments [1]. So for example if you
I haven't read this whole thread, so maybe it's already come up. Have
you turned on the garbage collection logging to see if the jvm is busy
cleaning up when you are seeing the slowness? Maybe the jvm is
struggling to keep the heap size within a particular limit?
//Ed
On Wed, Jul 22, 2009 at 10:2
Here at the Library of Congress we've got several production Solr
instances running v1.3. We've been itching to get at what will be v1.4
and were wondering if anyone else happens to be using it in production
yet. Any information you can provide would be most welcome.
//Ed
Jacob,
If you are interested in contributing any of your code to the solrpy
project [1] please let us know, either on here or on the solrpy
discussion list [2].
One of the motivations for putting the code up at code.google.com was
to make it easy for people to quickly contribute enhancements/fixe
It should be easy_install-able:
% easy_install solrpy
//Ed
On Tue, Dec 23, 2008 at 12:47 PM, jlist9 wrote:
> Maybe I'm using an older version. I'll give it a try and report back. Thanks.
>
> On Tue, Dec 23, 2008 at 3:26 AM, Ed Summers wrote:
>> Yes I
Yes I've used it with Unicode, see test_unicode in the unittests [1].
In fact one of the reasons why it was moved to google-code was so we
could rapidly fix some of the outstanding problems with the python
client. If you can demonstrate a bug using the unittests we've got for
it that would be great
On Mon, Dec 22, 2008 at 4:53 AM, Mark Jarecki wrote:
> I was just wondering if there were any new Python libraries compatible with
> SOLR 1.3 available or in development? All I can find are libraries for 1.2.
Did you see:
http://code.google.com/p/solrpy/
I'm using it with v1.3
//Ed
On Mon, Mar 24, 2008 at 12:13 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> AFAIK, no one has fixed the outstanding bugs and indicated it was
> ready to be committed.
What is the preferred approach to fixing bugs in patches? Attaching new patches?
//Ed
On Mon, Mar 24, 2008 at 6:32 AM, Leonardo Santagada
<[EMAIL PROTECTED]> wrote:
> Thanks, I think most of the stuff that I wanted to do is there... I
> will take a closer look and if there is omething missing I will add to
> that. Why is this on the issue tracker and was not commited to the svn?
Do you mean something like:
http://svn.apache.org/repos/asf/lucene/solr/trunk/client/python/solr.py
//Ed
On Dec 14, 2007 10:20 AM, Owens, Martin <[EMAIL PROTECTED]> wrote:
> I'm having some trouble understanding how the solr writer intergrates into
> python, I can't find any examples so does
Thanks for the additional context and the pointers to STARTS. I
realize solr-user is hardly a venue for discussing the details of
OpenSearch so I'll refrain from commenting any further. I apologize
for the harshness of my FUD comment.
//Ed
On Nov 26, 2007 5:35 PM, Walter Underwood <[EMAIL PROTECTED]> wrote:
> GData is really pretty useful. OpenSearch was just sloppy. Some element
> names were capitalized, some weren't. A bunch of stuff specific to A9's
> UI was mixed in. They insisted on using RSS in addition to Atom for a new
> appl
On Oct 12, 2007 10:13 AM, Walter Underwood <[EMAIL PROTECTED]> wrote:
> OpenSearch was a pretty poor design and is dead now, so I wouldn't
> expect any new implementations. Google's GData (based on Atom)
> reuses the few useful OpenSearch elements needed for things
> like number of hits. Solr's Ato
I'd say yes. Solr supports Unicode and ships with language specific
analyzers, and allows you to provide your own custom analyzers if you
need them. This allows you to create different definitions
for the languages you want to support. For example here is an example
field type for French text whic
On 10/18/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> I have a large number of servers, each running 1-2 containers, each
> having 1-2 solr deployments (fixed). If I want a new Solr instance,
> I just start a new container (possibly on a new server). I treat it
> like a process, and can shut it do
You might find the dynamic fields useful. From the schema.xml:
So you could have a document like:
Ed Summers
Library of Congress
without having to explicitly name these fields in the schema.xml. Does
that help at all?
//Ed
B
18 matches
Mail list logo
