Skip to content

SOLR-8362: proposal for polyField docValues support for TextField#321

Closed
magibney wants to merge 17 commits intoapache:mainfrom
magibney:SOLR-8362
Closed

SOLR-8362: proposal for polyField docValues support for TextField#321
magibney wants to merge 17 commits intoapache:mainfrom
magibney:SOLR-8362

Conversation

@magibney
Copy link
Contributor

See: SOLR-8362
Cotinuation of: apache/lucene-solr#1691

This PR introduces docValues support for TextField, supporting

  1. sort use case (including configurable post-analysis sort -- a drop-in replacement for SortableTextField, but with more flexibility)
  2. facet/significant-terms use case
  3. useDocValuesAsStored/valueSource/function/streamingExpression use case (configurable to support arbitrarily large size limits)

The rationale behind this PR is essentially the same as laid out in this comment. The main difference in this PR (as opposed to apache/lucene-solr#1691 described in that comment) is that this PR abandons the hope for Lucene-native support for post-analysis docValues (see LUCENE-10023) and instead generates post-analysis docValues by "pre-analyzing" (at the cost of duplicate effort) in TextField.createFields(...).

Lots of relevant context can also be found at: SOLR-11917.

magibney added 15 commits July 24, 2020 15:09
The purpose of this commit is to record the local (normally
uncommitted) changes to support development against a
local lucene snapshot. In addition to the changes recorded
in this commit, a system property change is called for,
which may be achieved by specifying `-DluceneSnapshot` on
the command line, or (particularly useful when gradle is
not invoked directly -- e.g., for IDE development), by
adding the following to `gradle.properties` file:

# Uncomment below if developing against a local lucene snapshot
systemProp.luceneSnapshot
This reverts commit 74117e4.

As a consequence of the decision to not move forward with merging
LUCENE-10023, we pull analysis in support of tokenized docValues
into Solr, and no longer need to rely on a Lucene SNAPSHOT version
@magibney
Copy link
Contributor Author

note: precommit will fail due to nocommits, but existing and new tests all should pass.

@magibney
Copy link
Contributor Author

For anyone curious about this PR at a high level, the refguide additions might be a good place to start:
https://github.com/apache/solr/pull/321/files#diff-c3bd51eeb7d80321dcfd4b8ee946a4c5f17fc22b563fb57dd727baae7461ed46

@github-actions
Copy link

This PR had no visible activity in the past 60 days, labeling it as stale. Any new activity will remove the stale label. To attract more reviewers, please tag someone or notify the dev@solr.apache.org mailing list. Thank you for your contribution!

@github-actions github-actions bot added the stale PR not updated in 60 days label Feb 24, 2024
@github-actions
Copy link

github-actions bot commented Oct 6, 2024

This PR is now closed due to 60 days of inactivity after being marked as stale. Re-opening this PR is still possible, in which case it will be marked as active again.

@github-actions github-actions bot added the closed-stale Closed after being stale for 60 days label Oct 6, 2024
@github-actions github-actions bot closed this Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

closed-stale Closed after being stale for 60 days stale PR not updated in 60 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant