Sorry. Let me add more info. (I assumed that anyone who tried it would see
the problem right away but that might not be the case.)
> You haven't shown the SOLR field type definitions.
Values of all non-String types in my index are not being shown.
In my case, this includes long, tint and date typ
On 28.05.2010 22:06, Chris Hostetter wrote:
and one "text_prefix"
defined similarly but with an additional EdgeNGramTokenFilter used when
indexing to generate "prefix" tokens. then search those fields using
dismax...
To be sure that I understand this right:
Am I right that I should not stopwor
There is only one primary key in a single index. If the id of your
different document types do collide, you can simply add a prefix or suffix
to make them unique.
Bill
On Fri, May 28, 2010 at 1:12 PM, Moazzam Khan wrote:
> Thanks for all your answers guys. Requests and consultants have a many
Hi. I'm trying to get Solr to index a database in which one column is a
filename of a PDF document I'd like to index. My configuration looks like this:
I'm using Solr from trunk (as of two days ago). The import process completes
without errors, and
No, not nearly enough information.
You haven't shown the SOLR field type definitions.
You haven't provided, say, the output from SOLR if you add &debugQuery=on.
You haven't shown the terms from either SOLR admin or Luke that they
actually see in the index.
You haven't identified the version of
Oh, here's a modified/improved version of what I described in my first email:
1. Queries like "id:123" which work fine in /solr/admin web interface but
returns nothing in Luke. Query "*:*" returns all records fine in Luke. I
expect Luke returns the same result as /solr/admin since it's essentially
Then you have to provide a lot more detail about what you did
and what you're seeing and what you think you should see. You
might review this page:
http://wiki.apache.org/solr/UsingMailingLists
Best
Erick
On Sun, May 30, 2010 at 1:41 PM, jlist9 wrote:
> I find in the Plugins tab that the defaul
The JVM arg seems to overwrite that just fine:
-Dsolr.data.dir=/opt/solr/example/data
On Sun, May 30, 2010 at 12:14 AM, Abdelhamid ABID wrote:
> .. and to unset dataDir just leave it blank
> ${solr.data.dir:}
>
> On Sun, May 30, 2010 at 12:15 AM, Chris Hostetter
> wrote:
>
>>
>> : Most likely yo
I find in the Plugins tab that the default is PersianAnalyzer. I switched
to StandardAnalyzer and tried a few different Lucene Compatibility values
but it didn't help :-(
On Sun, May 30, 2010 at 4:40 AM, Erick Erickson wrote:
> The Solr admin page as access to (and uses) the field
> definitions y
Hi Markus,
I was facing the same problem a few days ago and found an explanation in
the mail archive that clarifies my question regarding the usage of
Solr's WordDelimiterFilterFactory:
http://markmail.org/message/qoby6kneedtwd42h
Best,
Sascha
markus.rietz...@rzf.fin-nrw.de wrote:
i am won
The Solr admin page as access to (and uses) the field
definitions you've put in the config file. Luke has no
knowledge of this configuration, you have to choose
your analyzer from the drop down and select the one
closest to what's in your config file for SOLR. Are you
perhaps using an analyzer in L
.. and to unset dataDir just leave it blank
${solr.data.dir:}
On Sun, May 30, 2010 at 12:15 AM, Chris Hostetter
wrote:
>
> : Most likely you have missed to point data directory in solrconf.xml,
> : this should help :
> : http://wiki.apache.org/solr/SolrConfigXml#dataDir_parameter
>
> right .. dou
12 matches
Mail list logo