Hi,
1)How does the commit works with multiple requests?
2)Does SOLR handle the concurrency during updates?
3)Does solr support any thing like, if I enclose the keywords within quotes,
then we are searching for exactly those keywords together. Some thing like
google does, for example if I enclose l
Kindly Note again : we are using Embedded Solr.
On 9/17/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> Venkatraman S wrote:
> > We are using Lucene and are migrating to Solr 1.2 (we are using Embedded
> > Solr). During this process we are stumbling on certain problems :
> >
> > 1) IF the same do
Venkatraman S wrote:
We are using Lucene and are migrating to Solr 1.2 (we are using Embedded
Solr). During this process we are stumbling on certain problems :
1) IF the same document is added again, then it it getting added in the
index again(duplicated); inspite of the fact that the IDs are un
With regards to #3, it is recommended that for faceting, you use a separate
copy of the field with stemming/tokenizing disabled. See :
http://wiki.apache.org/solr/SolrFacetingOverview#head-fc68926c8421055de872acc694a6a966fab705d6
Thanks,
Stu
-Original Message-
From: Venkatraman S
Sent
We are using Lucene and are migrating to Solr 1.2 (we are using Embedded
Solr). During this process we are stumbling on certain problems :
1) IF the same document is added again, then it it getting added in the
index again(duplicated); inspite of the fact that the IDs are unique across
documents.
Hi,
Just a FYI.
I've seen some posts mentioned that Solr can index 100-150 docs/s and the
comparison between embedded solr and HTTP. I've tried to do the indexing
with 1.7+ million docs, each doc has 30 fields among which 10 fields are
indexed/stored and the rest are only stored. The result was
nope, the field options are created on startup -- you can't change them
dynamically (i don't know all the details, but I think it is a file
format issue, not just a configuration issue)
I'm not sure how your app is structured, from what you describe, it
sounds like you need two fields, one t
Hi,
Is it possible to turn off the "store" option based on field value. I would
like to index and store the primary document but for all revisions i only
need to index it and not store it.
Thanks
Bharani
--
View this message in context:
http://www.nabble.com/Control-index-store-at-document-le
Should the EdgeNGramFilter use the same term position for the ngrams
within a single token?
As is, the EdgeNGramTokenFilter increments the term position for each
character. In analysis.jsp, with the input "hello", I get:
term position 1 2 3 4 5
term text h
