HI
I made that change of quotes and case sensitivity. But now i am getting the
below exception while running delta-import:
Document # 1
at
org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.init(JdbcDataSource.java:186)
at
Actually, even in 2.3.1, CheckIndex checks for docs-out-of-order both
within and across segments, so now I'm at a loss as to why it's not
catching your case. Any of these indexes small enough to post
somewhere i could access?
Mike
James Brady wrote:
Hi,My indices sometime become
On Mon, Feb 23, 2009 at 2:09 PM, con convo...@gmail.com wrote:
HI
I made that change of quotes and case sensitivity. But now i am getting the
below exception while running delta-import:
Document # 1
at
Jacob,
What Solr version are you using? There is a bug in SolrHighlighter of
Solr 1.3,
you may want to look at:
https://issues.apache.org/jira/browse/SOLR-925
https://issues.apache.org/jira/browse/LUCENE-1500
regards,
Koji
Jacob Singh wrote:
Hi,
We ran into a weird one today. We have a
We are using Solr trunk (1.4) - currently nightly exported - yonik
- 2009-02-05 08:06:00
-Peter
On Mon, Feb 23, 2009 at 8:07 AM, Koji Sekiguchi k...@r.email.ne.jp wrote:
Jacob,
What Solr version are you using? There is a bug in SolrHighlighter of Solr
1.3,
you may want to look at:
Hello,
The wiki states 'When duplicate doc IDs are received, Solr chooses the
first doc and discards subsequent ones', I was wondering whether the
first doc is the doc of the shard which responds first or the doc in
the first shard in the shards GET parameter?
Regards,
gwk
Have a look at the StatsComponent, added after Solr 1.3 release
though. You can grab a nightly build to have it built-in.
More info available here: http://www.lucidimagination.com/search/?q=StatsComponent
Erik
On Feb 23, 2009, at 9:10 AM, Yves Hougardy wrote:
Hi,I'm trying to
gwk wrote:
Hello,
The wiki states 'When duplicate doc IDs are received, Solr chooses the
first doc and discards subsequent ones', I was wondering whether the
first doc is the doc of the shard which responds first or the doc in
the first shard in the shards GET parameter?
Regards,
gwk
If you mean at indexing time, you set field boost via data-config.xml. That
boost is parsed from there and set to the lucene document going through
DocBuilder,java, SolrInputDocuemnt.java and DocuemntBuilder.java
In case you want to set full-document boost (not just to a field) you can do
it
Excellent, I have created a new request handler that has all my shards,
boosts and other defaults as /business. /select is set to be the default
request handler. The queries seem to run fine now and after a bit of spot
checking they seem to be getting the same results. I have one question
though.
On Mon, Feb 23, 2009 at 10:12 AM, jdleider nab...@justinleider.com wrote:
How can I be sure the shards are applying the same boosts as the one
receiving the query?
Defaults always apply at any search handler... so if you put default
params on /business, they will become part of the shard
How fast is the search if the MergeFactor of Lucene Index is set to 20 or
more?did somebody uses Luke to optimize the indexing process? I would like
to know how fast is Luke.
Thanks
On Tue, Jan 27, 2009 at 3:52 PM, Ian Connor ian.con...@gmail.com wrote:
When you query by *:*, what order does
I finally found the reason of this behavior. I realize that if I waited a
couple of minutes, Firefox would send the if-none-match header which was
responded by the 304 code by solr.
What happens is that Firefox keeps a disk cache. If a response contains the
header Last-Modified, even if there is
Great this works.
BTW, there seems to be a problem w/ LocalSolrQueryComponent. It doesn't seem
to be respecting any filtering parameters in the solr request (fq).
thanks,
Rajiv
pjaol wrote:
Hi
Most of the localsolr / locallucene doc's are a little out of date I'll
get to updating
Hi Shalin,
Which auto-warming I have to remove to make commits faster. The below
configuration have in solrconfig.xml. Also, what is maxWarmingSearchers value.
filterCache
class=solr.LRUCache
size=512
initialSize=512
autowarmCount=128/
!-- queryResultCache caches
Some of the wildcards work, but not all of them. Unsurprisingly, the ones
that seem to work are ones that are wildcards in the 'base' of the word.
Thanks for the tip on the lowercase before stop words.
On Wed, Feb 18, 2009 at 12:35 AM, Otis Gospodnetic
otis_gospodne...@yahoo.com wrote:
Jim,
Say you have a bunch of solr servers that index new data, and then some
replica/slave setup that snappulls from the master on a cron or some
schedule. Live internet facing queries hit the replica, not the master, as
indexes/commits on the master slow down queries.
But even the query-only solr
New to Lucene / SOLr, but reading and learning fast.
I'm missing some fundamental mental link to understand how the facetted
browsing works in SOLr. I have read the Wiki pages on facets and on
configuration files. I have looked in the examples provided with SOLr. And
searched Google / the
On Mon, Feb 23, 2009 at 6:27 PM, Villemos, Gert
gert.ville...@logica.com wrote:
My problem is; where are the facets defined? I expect to se them in the
configuration, yet I dont.
Solr can facet on the fly. The first time you request faceting on a
field, it may take longer though as internal
My problem is; where are the facets defined? I expect to se them in the
configuration, yet I dont.
Solr can facet on the fly. The first time you request faceting on a
field, it may take longer though as internal data structures are built
and cached. The only current requirement is that a
Hello,
I was wondering if there was any facility to directly manipulate search results
based on business criteria to place documents at a fixed position in those
results. For example, when I issue a query, the first four results would be
based on natural search relevancy, then the fifth result
Hi Brian,
If you have enough servers - take that machine that's doing snapinstall out of
the pool for a bit, do snapinstall, warm it up well, put it back in the pool.
You'd really need to have enough servers, so that when you do this you can
avoid having multiple live query slaves with
server:/solr/select?q=field:''anything can go here; -- Lexical error,
encountered EOF after : \\'\'anything can go here
server:/solr/select?q=field:'anything' anything can go here; -- Same
problem
server:/solr/select?q=field:'anything' anything can go here\; -- No
problem (but ClientUtils's
What are the differences between using an sint and an integer, aside
from the range queries on sint? If I've indexed a field as an
integer, and I try to sort on it, will there be performance problem?
About 1.5 million documents in index.
--
Jonathan Haddad
http://www.rustyrazorblade.com
: server:/solr/select?q=field:'anything' anything can go here\; -- No
: problem (but ClientUtils's escape does not escape semicolons.)
ClientUtils doesn't escape it because it's not a special character in the
SolrQueryParser.
it *is* a special character to the OldLuceneQParserPlugin if (and
: I went ahead and added it since it does not hurt anything to escape more
: things -- it just makes the final string ugly.
: In 1.3 the escape method covered everything:
H good call, i didn't realize the escape method had been so
blanket in 1.3. this way we protect people who were
26 matches
Mail list logo
