One trick I use a lot with VwR is simply to do $object.class in a
template, hit refresh and see what type of object it is. The consult
javadocs/code to see how to navigate that object.
Highlighting support is something that I meant to put into the
templates shipped, as it is something
I've done a fair number of migrations, but it's kind of hard to give generic
advice on it. Specific questions as you dig in would be best. I'd probably,
at least, just start with a simple schema that models most of your data and get
Solr up and ingesting it. Then run some queries against it
Hi,
since we did some kind of migration in a similar situation in the
recent
past, I might add some (hopefully helpful) remarks:
If You use a Lucene-based application right now, You might already
have
an idea of which fields You want to store in Solr. Since You already
do
analyzing of
That's the expected result and I'm pretty happy with it.
But with this field :
field name=variableEltDDIXML
required=true
type=string
multiValued=false
indexed=true
stored=true
compressed=false
Hello,
We are working on Solr in Action [1]. One of the well received chapters from
LIA #1[2] was the Case Studies chapter, where external contributors described
how they used Lucene. We are getting good feedback about this chapter from LIA
#2 reviewers, too.
Solr in Action also has a Case
Siddhant,
Check the enhanced dismax patch in JIRA if you need fielded queries to work
with dismax.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
From: Siddhant Goel siddhantg...@gmail.com
To: solr-user@lucene.apache.org
Sent: Wed, January
Do you also suggest applying that latest patch to the Solr 1.4 GA version of
the source code (branch-1.4)?
I'm a little worried about it breaking Solrj due to the merge issues
encountered (see below). Would I need to stop using Solrj as my client, and
start using staight HTTP requests to take
Here is my query:
(virt* AND machine fingerprinting) OR (virt* AND encryption) OR (virt* AND
anonymous) OR (virt* AND analytic*) AND owned:true
It can be broken down to:
(A) OR (B) OR (C) OR (D) AND E
A, B, C and D are themselves AND boolean clauses.
The E clause at the end is not behaving the
Mark,
Does it help if you rewrite your query using +/- syntax (required,
prohibited), or nothing for should? Because that's what happens under the
hood (terms are required, prohibited, or should occur).
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original
That is a reasonable question. The problem here is that my users have already
created numerous queries just like this one, using ANDs and ORs. My users
are very technical and they have been using the results of these queries for
months now to perform analysis that drives business decisions. I
HI Mark,
Does this help?
http://wiki.apache.org/lucene-java/BooleanQuerySyntax
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
From: markwaddle m...@markwaddle.com
To: solr-user@lucene.apache.org
Sent: Thu, January 14, 2010 3:38:34 PM
Subject:
I have 2 data import files, and I'd like to be able to switch between without
renaming either file, and without changing solrconfig.xml. Does the
DataImportHandler support that? I tried passing a 'config' parameter with
the 'reload-config' command, but that didn't work.
Thanks,
Wojtek
--
View
I thought of another way: have two data import request handlers configured in
solrconfig.xml, one for each file.
wojtekpia wrote:
I have 2 data import files, and I'd like to be able to switch between
without renaming either file, and without changing solrconfig.xml. Does
the
Hello,
System : Debian 5.0
Java , tomcat solr installed from the repositories.
Java version 1.6_12 , tomcat 5.5 and solr 1.2.0 .
I am trying to use the schema.xml and the solrconfig.xml from the Drupal
module, but they fail to work.
The error I am getting is :
Error loading class
Hi,
Solr 1.2.0 didn't have TrieIntField.
Use the latest Solr - Solr 1.4.0
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
From: reallove thereall...@gmail.com
To: solr-user@lucene.apache.org
Sent: Thu, January 14, 2010 5:43:23 PM
Subject: Solr
On Wed, Jan 13, 2010 at 05:38:33PM -0500, Paul Rosen wrote:
Hi all,
The way the indexing works on our system is as follows:
We have a separate staging server with a copy of our web app. The clients
will index a number of documents in a batch on the staging server (this
happens about once
Hello,
Thanks for the answer.
Unfortunately, in the Debian repositories, even in testing, latest Solr
version is 1.3.0 . Can I use that for the Drupal module to work ?
Thank you.
Otis Gospodnetic wrote:
Hi,
Solr 1.2.0 didn't have TrieIntField.
Use the latest Solr - Solr 1.4.0
Otis
--
I'm trying to reduce memory usage when indexing, and I see that using
the binary format may be a good way to do this. Unfortunately I can't
see a way to do this using the EmbeddedSolrServer since only the
CommonsHttpSolrServer has a setRequestWriter method. If I'm running out
of memory
You may want to ask on Drupal's mailing lists. I hear about Drupal and Solr
constantly, I can't imagine them not having Solr 1.4 support, esp. if you say
their configs contain referenes to things that are in Solr 1.4.0.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
-
Hi,
Running out of memory because of XML document when indexing documents sounds
very weird/suspicious.
Are you running out of memory on the server side?
Are you indexing super large batches?
How big is your JVM heap?
How big is your ramBufferSizeMB?
Otis
--
Sematext -- http://sematext.com/
Hi,
The Drupal Solr Module will work with both Solr 1.3 and 1.4
I currently have client installations using both these versions with Drupal
(verison 5 and 6 )
Regards,
Dave
On 14 Jan 2010, at 23:08, Otis Gospodnetic wrote:
You may want to ask on Drupal's mailing lists. I hear about Drupal
That explains my exact problem, thank you! May I ask how you found that wiki
posting?
Otis Gospodnetic wrote:
HI Mark,
Does this help?
http://wiki.apache.org/lucene-java/BooleanQuerySyntax
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
--
View this message in
The situation is apparently that the latest Drupal requires Solr 1.4
but Debian does not have a Solr 1.4 product. Can you use an earlier
Drupal Solr package?
If you want to backport the current Drupal Solr package to Solr 1.3,
changing the Trie fields to 'sint' etc. might work.
You don't have to
Try this:
http://www.lucidimagination.com/search/?q=boolean+query
On Thu, Jan 14, 2010 at 3:45 PM, markwaddle m...@markwaddle.com wrote:
That explains my exact problem, thank you! May I ask how you found that wiki
posting?
Otis Gospodnetic wrote:
HI Mark,
Does this help?
Hi, folks,
I am using Solr 1.3 pretty successfully, but am running into an issue that
hits once in a long while. I'm still using 1.3 since I have some custom
code I will have to port forward to 1.4.
My basic setup is that I have data sources continually pushing data into
Solr, around 20K adds
25 matches
Mail list logo