Thanks Uwe, this will help us to clarify details and make a decision.
If you write your own data files into a given index directory, it is very
> likely that you may corrupt your index. In later Lucene versions (5.x) we
> are very strict with not allowing files in the index directory, which were
>
components in schema are not loaded from runtimelib yet. Only
solrconfig components are loaded from runtime lib a.k.a blob store
On Thu, Sep 10, 2015 at 11:00 PM, Steve Davids wrote:
> Hi,
>
> I am attempting to migrate our deployment process over to using the
> recently added "Blob Store API" wh
You may better ask this question on the solr-u...@lucene.apache.org list.
Uwe
-
Uwe Schindler
uschind...@apache.org
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/
> -Original Message-
> From: Steve Davids [mailto:sdav...@gmail.com]
> Sent: Thurs
Hi,
I am attempting to migrate our deployment process over to using the
recently added "Blob Store API" which should simplify things a bit when it
comes to cloud infrastructures for us. Unfortunately, after loading the jar
in the .system collection and adding it to our runtimelib config overlay
an
Hi,
Yes, thanks.
If I want to customize this behavior (remove it or make it more or less
important), is it correct to override the Similarity class to implement
a new computeSlopFactor method?
Thank you for your answer.
Regards,
Aurélien MAZOYER
On 10.09.2015 12:37, Alan Woodward wrote:
Hi,
SpanNearQuery will also take into account the ‘width’ of the match, so that
terms that are closer together will score more highly. Is that what you’re
looking for?
Alan Woodward
www.flax.co.uk
On 10 Sep 2015, at 10:43, aurelien.mazo...@francelabs.com wrote:
> Hi all,
>
> SpanNearQuery
Hi all,
SpanNearQuery and SloppyPhraseQuery can have similar behavior in some
use cases. On the one hand, I have to distinguish between ordered and
unordered terms (that’s enabled with SpanNearQuery) but on the other
hand, I want to use the SloppyPhraseScorer, that takes the relative
position
Hi Vlad,
> Can you please share some details about that design decision "Whenever
> Lucene updates something in the index, it creates a new file". Is it right
> understanding that while IndexOutput is open, Lucene continues to use the
> same output/file. But after it closed (for instance applicati
