, but will mess up your queries at query
time, so set them to "0" in the query analyzer
Also, make sure you have autoGeneratePhraseQueries="true" on the field type,
but that's not the issue here.
-- Jack Krupansky
-Original Message-
From: Sandeep Mestry
Sent:
small test documents with
similar values and see if the 50 limit seems to account for behavior that
you see with that test dataset.
-- Jack Krupansky
-Original Message-
From: Ryan Wilson
Sent: Thursday, May 16, 2013 11:37 AM
To: solr-user@lucene.apache.org
Subject: Re: Strange fuzzy
\\somefile.pdf
or
"D:\\somedir\\somefile.pdf"
-- Jack Krupansky
-Original Message-
From: Daniel Baughman
Sent: Thursday, May 16, 2013 11:33 AM
To: solr-user@lucene.apache.org
Subject: Deleting an entry from a collection when they key has ":" in it
Hi All,
I seem to be
Technically, core Solr does not require a unique key. A lot of features in
Solr do require unique keys, and it is recommended that you have unique
keys, but it is not an absolute requirement.
-- Jack Krupansky
-Original Message-
From: Daniel Baughman
Sent: Thursday, May 16, 2013 1:50
enateAll="0" splitOnCaseChange="1"
splitOnNumerics="0" preserveOriginal="0" />
-- Jack Krupansky
-Original Message-
From: Sandeep Mestry
Sent: Thursday, May 16, 2013 5:50 PM
To: solr-user@lucene.apache.org
Subject: Re: Question about Edismax - Solr 4.0
H
(Erik: Or he can get the LucidWorks Search product and then use "near" and
"before" operators so that he doesn't need the surround query parser!)
-- Jack Krupansky
-Original Message-
From: Erik Hatcher
Sent: Thursday, May 16, 2013 6:11 PM
To: solr-user@luce
he second field.
You'll have the explicitly escape the spaces in your queries using a
backslash. You can't enclose the query in quotes since that would disable
the wildcard.
You could also use regex queries on that field:
/.*san.m.*/
-- Jack Krupansky
-Original Message
figuration before
going wild.
You can also have more than 2 shards and put more than one shard on a node
to allow for easier expansion.
-- Jack Krupansky
-Original Message-
From: Abhishek tiwari
Sent: Friday, May 17, 2013 8:01 AM
To: solr-user@lucene.apache.org
Subject: Solr cloud
AnimalAsPayloadTokenFilterFactory or a generalized
AttributeAsPayloadTokenFilterFactory that takes the name of the attribute
("animal").
-- Jack Krupansky
-Original Message-
From: Thomas Portegys
Sent: Friday, May 17, 2013 6:08 PM
To: solr-user@lucene.apache.org
Subject: Ques
\s+)?(good|excellent)/
Ends with:
/this\\s+is\\s+(\\w\\s+)?(good|excellent)$/
Exact match:
/^this\\s+is\\s+(\\w\\s+)?(good|excellent)$/
Caveat:
BUT... such character-level regex matching is NOT guaranteed to be speedy
and really should only be used for relatively small datasets.
-- Jack Krupans
sqrt(popularity)
See:
http://wiki.apache.org/solr/CommonQueryParameters#Caching_of_filters
But, start simple, with separate, cached, filter queries, and only get fancy
if you have problems with query latency.
-- Jack Krupansky
-Original Message-
From: J Mohamed Zahoor
Sent: Satur
namic fields and/or multi-valued fields with
large numbers of values per document, that is feedback that your design
needs to be denormalized and flattened further.
-- Jack Krupansky
-Original Message-
From: Dmitry Kan
Sent: Monday, May 20, 2013 7:06 AM
To: solr-user@lucene.apache.
Tomcat is notorious for not defaulting to UTF-8 encoding for URLs which is
how the query is passed, which is needed to preserve all these accented
characters.
In Tomcat's server.xml, it should have something like:
The "URIEncoding="UTF-8"" is essential.
-- Jack
Try the Solr Admin UI Analysis page - enter text for both index and query
for your field and see whether the final terms still have their accents.
-- Jack Krupansky
-Original Message-
From: jignesh
Sent: Monday, May 20, 2013 10:46 AM
To: solr-user@lucene.apache.org
Subject: Re: Not
We can conclude that the field type analyzer is NOT the problem. Good
experiment to eliminate one culprit.
-- Jack Krupansky
-Original Message-
From: jignesh
Sent: Monday, May 20, 2013 1:21 PM
To: solr-user@lucene.apache.org
Subject: Re: Not able to search Spanish word with ascent in
if the accents are missing.
curl http://localhost:8983/solr/update?commit=true -H
'Content-type:application/xml' -d '
doc-1
Hola Mañana en le Café, habla el Académie
française!
'
The above worked for me with the standard Solr 4.3 example schema.
-- Jack Krup
n you can return features for clean text with
accents.
Do you really want the HTML in Solr at all? For rich display it is
reasonable, but is that your requirement?
-- Jack Krupansky
-Original Message-
From: Shawn Heisey
Sent: Monday, May 20, 2013 1:52 PM
To: solr-user@lucene.apache.
ot;, "Berlin:Germany", "Berlin GERMANY", etc.
Ultimately, the idea for facets is not that they uniquely identify an
entity, but that a combination of facet selections let you drill down into
the data, such that each facet selection narrows one dimension.
-- Jack Krupansky
-
coding+OR+development)\
&df=features&defType=surround&indent=true"
The LucidWorks Search query parser also supports NEAR, BEFORE, and AFTER
operators, in conjunction with OR and "-" to generate span queries:
q=(java OR groovy OR scala) BEFORE:0 (programming OR coding OR
Any particular reason you would want to limit the documents for facet
calculation? I mean, the whole point of the facet numbers is to let users
know what's out there. You must have some other rationale in mind - what is
it?
-- Jack Krupansky
-Original Message-
From: Achim
I'll make sure to include that specific example in the new Solr book.
-- Jack Krupansky
-Original Message-
From: Mike Hugo
Sent: Tuesday, May 21, 2013 12:29 AM
To: solr-user@lucene.apache.org
Subject: Re: Expanding sets of words
Fantastic! Thanks!
On Mon, May 20, 2013 at 11:
Try again on a machine with more memory. Or did you do that already?
-- Jack Krupansky
-Original Message-
From: Umesh Prasad
Sent: Tuesday, May 21, 2013 1:57 AM
To: solr-user@lucene.apache.org
Subject: Hard Commit giving OOM Error on Index Writer in Solr 4.2.1
Hi All,
I am hitting
Hmmm... I did a quick test and quoted phrase wasn't working for me either.
Oh well.
But... it should work for the LucidWorks Search query parser!
-- Jack Krupansky
-Original Message-
From: Mike Hugo
Sent: Tuesday, May 21, 2013 11:26 AM
To: solr-user@lucene.apache.org
Subjec
t, I'm not
familiar enough with the internal details of the Solr faceting code.
-- Jack Krupansky
-Original Message-
From: Achim Domma
Sent: Tuesday, May 21, 2013 6:39 PM
To: solr-user@lucene.apache.org
Subject: Re: MoreLikeThisHandler + Facets
Our current index contains nearly 400k doc
7;ll make sure that example is in the book as well.
-- Jack Krupansky
-Original Message-
From: Jack Krupansky
Sent: Tuesday, May 21, 2013 11:37 AM
To: solr-user@lucene.apache.org
Subject: Re: Expanding sets of words
Hmmm... I did a quick test and quoted phrase wasn't working for me e
to solve. That short-circuited our focus on
really solving your problem.
-- Jack Krupansky
-Original Message-
From: Dmitry Kan
Sent: Wednesday, May 22, 2013 6:50 AM
To: solr-user@lucene.apache.org
Subject: Re: [custom data structure] aligned dynamic fields
Jack,
Thanks for your resp
The topic has come up, but nobody has expressed a sense of urgency.
It actually has a placeholder Jira:
https://issues.apache.org/jira/browse/SOLR-4774
Feel free to add your encouragement there.
-- Jack Krupansky
-Original Message-
From: Brendan Grainger
Sent: Wednesday, May 22
JSON as a
string field, which Solr appears to be doing correctly.
-- Jack Krupansky
-Original Message-
From: Karthick Duraisamy Soundararaj
Sent: Wednesday, May 22, 2013 8:03 PM
To: solr-user@lucene.apache.org
Subject: Storing and retrieving json
Hello all,
I am facing
update has been
committed as well.
Also, with soft commit, documents should be visible must more rapidly.
Do you have some other, unmentioned requirement that you feel is biasing you
against a sensible poller? Clue us in as to the nature of such a
requirement.
-- Jack Krupansky
-Origin
is not acceptable. But I'd recommend the tuned poller.
"would require a whole bunch of logic" - and you think the commit hooks and
your push model implementation (on both Solr and client side) will be less
logic?!!
-- Jack Krupansky
-Original Message-
From: Fredri
first. Then mimic that in
your customization.
-- Jack Krupansky
-Original Message-
From: Christian Köhler
Sent: Thursday, May 23, 2013 8:25 AM
To: solr-user@lucene.apache.org
Subject: Solr 4.3 fails to load MySQL driver
Hi,
in my attempt to migrate for m 3.6.x to 4.3.0 I stumbled
specifications and
numerous examples, including sample input and outputs (the LucidWorks Solr
Reference does a better job with examples as well.)
The book has been written in parallel with branch_4x and that will continue.
-- Jack Krupansky
dateProcessorFactory, LastFieldValueUpdateProcessorFactory,
MaxFieldValueUpdateProcessorFactory, MinFieldValueUpdateProcessorFactory
-- Jack Krupansky
-Original Message-
From: world hello
Sent: Thursday, May 23, 2013 7:50 PM
To: solr-user@lucene.apache.org
Subject: FW: howto: get the value from a multivalued field
s why you see "and" included in the parsed query as if it
were a term. And I believe it turns "text:()" into "text:"()"", which makes
the original Lucene error go away, but the "()" analyzes to nothing and
generates no term in the query.
So,
position.
Whether your app is using the filter for that purpose remains to be seen.
Removing duplicates from the raw input token stream would impact the term
frequency.
-- Jack Krupansky
-Original Message-
From: Dotan Cohen
Sent: Friday, May 24, 2013 3:03 AM
To: solr-user
er and edismax query
parser do.
But, are you sure you really mean "fuzzy search", as opposed to, say,
spellcheck?
-- Jack Krupansky
-Original Message-
From: Sagar Chaturvedi
Sent: Friday, May 24, 2013 2:43 AM
To: solr-user@lucene.apache.org
Subject: Fuzzy search in solr
Hi
what remediation it was performing..
-- Jack Krupansky
-Original Message-
From: Shankar Sundararaju
Sent: Friday, May 24, 2013 1:01 PM
To: solr-user@lucene.apache.org
Subject: Re: Can anyone explain this Solr query behavior?
Hi Jack Krupansky,
Thank you for your reply. I would like to
Thanks, Erick. I could do the experiment of publishing both spiral and
perfect found and see which "wins". Spiral does have the one downside of not
standing out on a shelf. But, for now, I'll focus on getting the (rough
draft) e-book available ASAP.
-- Jack Krupansky
-O
The only comment I was trying to make here is the relationship between the
RemoveDuplicatesTokenFilterFactory and the KeywordRepeatFilterFactory.
No, stemmed terms are not considered the same text as the original word. By
definition, they are a new value for the term text.
-- Jack Krupansky
Fuzzy query is invoked just like any other query:
.../select?q=alpha~1
-- Jack Krupansky
-Original Message-
From: Sagar Chaturvedi
Sent: Sunday, May 26, 2013 11:27 PM
To: solr-user@lucene.apache.org
Subject: RE: Fuzzy search in solr
Thank you jack for the response.
Fuzzy search is
The intent is that optimize is obsolete and should no longer be used,
especially with tiered merge policy running. In other words, merging should
be occurring on the fly in Lucene now. What release of Solr are you running?
-- Jack Krupansky
-Original Message-
From: heaven
Sent
te/extract?literal.id=doc-1\
&commit=true&uprefix=attr_" -F "my.pdf=@my.pdf"
Once you fixed out which of the metadata you want to keep, either add those
metadata attribute names to your schema, or
add explicit SolrCell field mappings for each piece of metadata:
&
If you would like to Solr-ize your contribution, that would be great. The
focus of the book will be hard-core Solr.
-- Jack Krupansky
-Original Message-
From: Koji Sekiguchi
Sent: Monday, May 27, 2013 8:07 AM
To: solr-user@lucene.apache.org
Subject: Re: Note on The Book
Hi Jack
is
really absolutely needed.
3. Try to understand why #1 is not sufficient and resolve the cause(s), so
that optimize is no longer needed.
-- Jack Krupansky
-Original Message-
From: Yonik Seeley
Sent: Monday, May 27, 2013 9:46 AM
To: solr-user@lucene.apache.org
Subject: Re: Overlapp
he Solr index directory contents or even the directory
itself need to be explicitly deleted first? I believe it is the latter, but
the former "seems" to work, most of the time. Deleting the directory itself
"seems" to be the best answer, to date - but no guarantees!
-- Jack
have "sub-documents", which is the "get out of jail free" card
that a lot of people expect with multi-valued (and dynamic) fields.
If you want an object to be a first-class object, make it a separate Solr
document. Bite the bullet, and live with it.
-- Jack Krupan
:)
-- Jack Krupansky
-Original Message-
From: Alexandre Rafalovitch
Sent: Tuesday, May 28, 2013 10:41 AM
To: solr-user@lucene.apache.org
Subject: Re: Paging with all Hits
I feel that the strength of the Jack's rant is somewhat unprovoked by
the original question. I also feel tha
k your composite key field name as well. And set
the delimiter string as well in the concat update processor.
I managed to reverse the field order from what you requested (userid,
docid).
I used the standard Solr example schema, so I used dynamic fields for the
two ids, but use your own field names.
that is
not mangling the encodings.
I just tried a test where I copied the text from your email response and
added the XML header line you used, and it posted fine to Solr, but I am
running Solr 4.3. I used vi under Cygwin for the editing.
-- Jack Krupansky
-Original Message-
From
The order in the ID should be purely dependent on the order of the field
names in the processor configuration:
docid_s
userid_s
-- Jack Krupansky
-Original Message-
From: Rishi Easwaran
Sent: Tuesday, May 28, 2013 2:54 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Composite
e multiple input fields - whether
this is a bug or a feature or simply undefined.
-- Jack Krupansky
-Original Message-
From: Rishi Easwaran
Sent: Tuesday, May 28, 2013 3:54 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Composite Unique key from existing fields in schema
I though
We'll have a blog for the book. We hope to have a first
raw/rough/partial/draft published as an e-book in maybe 10 days to 2 weeks.
As soon as we get that process under control, we'll start the blog. I'll
keep your email on file and keep you posted.
-- Jack Krupansky
-O
order will change the output order. Also, field names are stored in a
HashSet anyway, which would tend to scramble their order.
-- Jack Krupansky
-Original Message-
From: Rishi Easwaran
Sent: Tuesday, May 28, 2013 6:01 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Composite
query client's will be most comfortable with.
-- Jack Krupansky
-Original Message-
From: Kamal Palei
Sent: Tuesday, May 28, 2013 10:54 PM
To: solr-user@lucene.apache.org
Subject: Re: How apache solr stores indexes
Thanks Alex.
I am in dilemma how do I store the skill sets with
very open to requests - what people really wish a book
would actually do for them. The only request we won't be open to is to do it
all in only 300 pages.
-- Jack Krupansky
-Original Message-
From: Erick Erickson
Sent: Wednesday, May 29, 2013 7:19 AM
To: solr-user@lucene.a
You need to UUEncode the & with %26:
...solr/select?q=kelile%26dimle
Normally, & introduces a new URL query parameter in the URL.
-- Jack Krupansky
-Original Message-
From: Furkan KAMACI
Sent: Wednesday, May 29, 2013 10:55 AM
To: solr-user@lucene.apache.org
Subject:
So, make it:
solr/select?q="kelile%26dimle"
-- Jack Krupansky
-Original Message-
From: Carlos Bonilla
Sent: Wednesday, May 29, 2013 11:39 AM
To: solr-user@lucene.apache.org
Subject: Re: Escaping & character at Query
Hi, I meant:
solr/select?q="kelile&di
Just replace the stripped markup with the equivalent number of spaces to
maintain positions.
Was there some specific problem you were encountering?
-- Jack Krupansky
-Original Message-
From: jasimop
Sent: Wednesday, May 29, 2013 4:12 PM
To: solr-user@lucene.apache.org
Subject
Markus,
Okay, more pages it is!
-- Jack Krupansky
-Original Message-
From: Markus Jelsma
Sent: Wednesday, May 29, 2013 5:35 PM
To: solr-user@lucene.apache.org
Subject: RE: Note on The Book
Jack,
I'd prefer tons of information instead of a meager 300 page book that leaves
a l
ope better with straight Java code than cryptic regular
expression sequences.
-- Jack Krupansky
-Original Message-
From: jasimop
Sent: Thursday, May 30, 2013 12:46 AM
To: solr-user@lucene.apache.org
Subject: Re: Problem with PatternReplaceCharFilter
Honestly, I have no idea how
No, there is not.
-- Jack Krupansky
-Original Message-
From: Sagar Chaturvedi
Sent: Thursday, May 30, 2013 3:03 AM
To: solr-user@lucene.apache.org
Subject: RE: Support for Mongolian language
I have already checked this link. Could not find any hint about Mongolian
language. Is there
You can just use "NOW/DAY" for a filter that would only change once a day:
[NOW/DAY-60DAY TO NOW/DAY]
Oops... make that:
[NOW/DAY-60DAY TO NOW/DAY+1DAY]
Otherwise, it would miss dates after the start of today.
Even better, make it:
[NOW/DAY-60DAY TO *]
-- Jack Krupansky
---
ltivalued field:
doc-id
-- Jack Krupansky
-Original Message-
From: Dotan Cohen
Sent: Thursday, May 30, 2013 7:55 AM
To: solr-user@lucene.apache.org
Subject: Removing a single value from a multiValue field
I have a Solr application with a multiValue field 'tags'. All field
I wrote "Otherwise, it would miss dates after the start of today", but that
should be "Otherwise, it would miss documents with times after the start of
today if the current time is before noon."
But use "*" and you will be better off anyway.
-- Jack Krupansky
--
is covered in the book, separate chapters for XML
and JSON, each with dozens of examples like this.
-- Jack Krupansky
-Original Message-
From: Dotan Cohen
Sent: Thursday, May 30, 2013 9:36 AM
To: solr-user@lucene.apache.org
Subject: Re: Removing a single value from a multiValue field
27; -d '
[{"id": "doc-1",
"title": "Hello World",
"features": ["Fast", "Cheap"],
"bad_field_name": "Junk",
"abstract": "Not in schema either"}]'
Results:
"
t;],
"other_t":"Other text",
"more_t":"Some more text. The end",
That stripped the HTML only from the "features" field, and expanded the
named character entity as well.
Add multiple for multiple fields, or use "fieldRegex",
Try using the "text_general" field type and see how reasonable or
unreasonable the standard tokenizer is at identifying reasonable word breaks
for some sample Mongolian text.
Use the Solr Admin UI Analyzer page to see what the various term analysis
filters output.
-- Jack
Please do not use an existing message thread for another topic - that is
known as "thread hijacking" and is a very discourteous thing to do. Please
start a new message thread. You didn't "correct" the subject line, you
CHANGED it. Please DO NOT do that on this
Please do not respond to hijacked message threads, other than to encourage
the sender to start a new message thread.
-- Jack Krupansky
-Original Message-
From: Shreejay
Sent: Friday, May 31, 2013 5:10 AM
To: solr-user@lucene.apache.org
Subject: Re: Highlighting fields
Are the
Great. That was an example from the book.
-- Jack Krupansky
-Original Message-
From: Kalyan Kuram
Sent: Friday, May 31, 2013 4:04 PM
To: solr-user@lucene.apache.org
Subject: RE: Strip HTML Tags and Store
Thanks it worked..!!
From: j...@basetechnology.com
To: solr-user
what
the result is.
And review the various "text_*" field types in the standard Solr example
schema to see examples that use a stemming filter and make sure you use a
similar technique. It could simply be that you haven't picked a field type
that includes a stemming filter.
If you have a space in field value, either enclose the entire field value in
quotes:
"TEST1 TEST"
Or escape each space with a single backslash:
TEST1\ TEST
In your example, the space in the first term is preceded by a double
backslash and the space in the second term is unescaped.
Ah... now I understand - they are separate terms in the same field.
You want:
NORM_BUS_NME:(TEST TEST1 TEST2)^35.44 OR TRIGRAM_NORM_BUS_NME:(TEST TEST1
TEST2)^20
Even so, I'm not confident that I really know what you are really after -
try explaining in simple English first.
--
do you WANT the Solr key field to look like? I mean,
YOU are the data architect, right? What requirements do you have? When your
Solr application users receive the key values in the responses to queries,
what expectations do you expect to set for them?
-- Jack Krupansky
-Original Message
Same answer. Whether it is 2, 3, 10 or 1000 tables, you, the data architect
must decide how to uniquely identify Solr documents. In general, when
joining n tables, combine the n keys into one composite key. Either do it on
the SQL query side, or with a Solr update request processor.
-- Jack
for using the
application, so if they are detected as performing long or stupid queries,
log the details and administratively take action, such as denying them
access (or billing them for excessive resource usage.)
-- Jack Krupansky
-Original Message-
From: Bernd Fehling
Sent: Monda
No, but you can with the LucidWorks Search query parser:
f1:(cat dog fox bat fish cow)~50% f2:(cat dog fox bat fish zebra)~2
See:
http://docs.lucidworks.com/display/lweug/Minimum+Match+for+Simple+Queries
-- Jack Krupansky
-Original Message-
From: Eric Wilson
Sent: Monday, June 03
itect. Solr doesn't
really care.
The real bottom line is that you need to be clear about your data model
requirements. For example, how will your users be querying the data and what
results will they expect.
-- Jack Krupansky
-Original Message-
From: Raheel Hasan
Sent: Monda
Check out the support for external scripting of update request processors:
http://lucene.apache.org/solr/4_3_0/solr-core/org/apache/solr/update/processor/StatelessScriptUpdateProcessorFactory.html
Are there any of your requirements that that doesn't address?
-- Jack Krupansky
-Ori
There is the "timeAllowed" parameter:
http://wiki.apache.org/solr/CommonQueryParameters#timeAllowed
-- Jack Krupansky
-Original Message-
From: Roman Chyla
Sent: Monday, June 03, 2013 11:53 AM
To: solr-user@lucene.apache.org
Subject: Re: how are you handling killer queries
Also, just to be clear, MM/minMatch, is not an option for a "field" but for
a full BooleanQuery. I mean, you can't have two different MM values within
the same BooleanQuery, except with nested BooleanQuerys, where each BQ has
its own MM.
-- Jack Krupansky
-Original Mes
Sorry about that. Unfortunately, scripting is only on the update side. But I
imagine athat a lot of the logic could be repurposed for the query side.
-- Jack Krupansky
-Original Message-
From: Achim Domma
Sent: Monday, June 03, 2013 2:31 PM
To: solr-user@lucene.apache.org
Subject: Re
blem you are trying to resolve.
-- Jack Krupansky
-Original Message-
From: Marcin Rzewucki
Sent: Tuesday, June 04, 2013 6:38 AM
To: solr-user@lucene.apache.org
Subject: search&scroll
Hi,
Is there something similar to ElasticSearch search&scroll function, but in
Solr ? For me, it
It is merely a performance optimization. Lucene is already blazing fast at
basic tf-idf query, so that form of "hack" is not needed.
-- Jack Krupansky
-Original Message-
From: Furkan KAMACI
Sent: Tuesday, June 04, 2013 10:07 AM
To: solr-user@lucene.apache.org
Subject: S
ave a tool to automatically flatten and denormalize complex
objects and graphs and database joins, great. Please describe what it
actually does in a little more (but not excessive) detail.
-- Jack Krupansky
-Original Message-
From: Tuğcem Oral
Sent: Tuesday, June 04, 2013 8:57 AM
To:
Best to submit your inquiry as a DataStax support ticket or on their support
forum. They have people standing by ready to support you.
-- Jack Krupansky
-Original Message-
From: Saikat Kanjilal
Sent: Tuesday, June 04, 2013 12:41 PM
To: solr-user@lucene.apache.org
Subject: Creating a
The double quotes are required for curl simply because of the "&", which
tells the shell to run the preceding command in the background. The quotes
around the full URL escape the "&".
-- Jack Krupansky
-Original Message-
From: Saikat Kanjilal
Sent: Tuesda
mandatory, which is why they have separate libs.
-- Jack Krupansky
-Original Message-
From: Raheel Hasan
Sent: Wednesday, June 05, 2013 5:57 AM
To: solr-user@lucene.apache.org
Subject: Files included from the default SolrConfig
Hi,
I am trying to optimize solr.
The default solrConfig
exact same document twice would not result in a change in the index
(unless you had a date field with a value of "NOW".) Copy field only uses
values from the current document.
-- Jack Krupansky
-Original Message-
From: Robert Krüger
Sent: Wednesday, June 05, 2013 10
To further boost adjacent terms.
But the edismax pf/pf2/pf3 options might be good enough for you.
-- Jack Krupansky
-Original Message-
From: Shawn Heisey
Sent: Wednesday, June 05, 2013 11:10 AM
To: solr-user@lucene.apache.org
Subject: Re: Phrase matching with set union as opposed to s
"apache-solr-dataimporthandler-.*\.jar" - note that the "apache-" prefix has
been removed from Solr jar files.
-- Jack Krupansky
-Original Message-
From: O. Olson
Sent: Wednesday, June 05, 2013 12:01 PM
To: solr-user@lucene.apache.org
Subject: No files added to
ngrams?
See:
http://lucene.apache.org/core/4_3_0/analyzers-common/org/apache/lucene/analysis/ngram/NGramFilterFactory.html
-- Jack Krupansky
-Original Message-
From: Prathik Puthran
Sent: Wednesday, June 05, 2013 11:59 AM
To: solr-user@lucene.apache.org
Subject: Configuring lucene to
"Is there any other documentation that I should review?"
It's in the works! Within a week or two.
-- Jack Krupansky
-Original Message-
From: Dotan Cohen
Sent: Wednesday, June 05, 2013 12:06 PM
To: solr-user@lucene.apache.org
Subject: Re: Phrase matching with set unio
]
One of the values should be the value of the field that is the source of the
copyField. Maybe the other value will give you a clue as to where it came
from.
Check your SolrJ code - maybe you actually do try to initialize a value in
the field that is the copyField target.
-- Jack Krupansky
Sounds like the Solr Admin UI is too-aggressively encoding the query part of
the URL for display. Each query parameter value needs to be encoded, not the
entire URL query string as a whole.
-- Jack Krupansky
-Original Message-
From: ethereal
Sent: Wednesday, June 05, 2013 4:11 PM
To
has_location_b
false
-- Jack Krupansky
-Original Message-
From: kevinlieb
Sent: Wednesday, June 05, 2013 5:43 PM
To: solr-user@lucene.apache.org
Subject: search for docs where location not present
I have a location-type field in my schema where I store lat / lon of a
document when this
. The point is that you get to decide how the node
will be chosen.
So, go ahead and come up with your own function that takes one of your
unique keys and generates a shard number. A simple approach is to hash the
key, and take the low bits modulo the number of shards.
-- Jack Krup
I don't recall seeing any such filter. Sounds like a good idea though.
Although, maybe it is another good idea that really isn't too necessary for
solving many real world problems.
-- Jack Krupansky
-Original Message-
From: Dotan Cohen
Sent: Thursday, June 06, 2013 3:45 A
1. Try a simple curl command to add the document.
2. Check to see if maybe there is a duplicate copyField directive in your
schema. How many copyField directives do you have?
At least we know that it is exactly the same value duplicated and not some
other value.
-- Jack Krupansky
1501 - 1600 of 2693 matches
Mail list logo
