Understood, however code is rarely random/undefined. Does lucene look at %
docs in each state, or the first doc or something else?
On Sun, Jun 9, 2019 at 1:58 PM Erick Erickson
wrote:
> It’s basically undefined. When segments are merged that have dissimilar
> definitions like this what can
You would be far better off taking the question to Sitecore support.
The Solr community has no way of knowing the specifics of that
offering.
Best,
Erick
On Wed, Jun 5, 2019 at 3:26 PM varma mahesh wrote:
>
> ++solr-user@lucene.apache.org
>
> On Thu 6 Jun, 2019, 1:19 AM varma mahesh, wrote:
>
Hi team,
Please reply for the above query.
It’s basically undefined. When segments are merged that have dissimilar
definitions like this what can Lucene do? Consider:
Faceting on a text (not sortable) means that each individual token in the index
is uninverted on the Java heap and the facets are computed for each individual
term.
Hi there,
We recently changed a field from TextField + no docValues to
SortableTextField which has docValues enabled by default. Once I did this I
do not see any facet values for the field. I know that once all the docs
are re-indexed facets should work again, however can someone clarify the
Hi：
When I use LTR, there are 72 features, 500 models and 200 million data.
During use, LTR execution was found to be extremely slow, with each query above
5s.
Through the analysis found in LTRScoringQuery ModelWeight scorer method
of class 72 when creating FeatureScorer
