[ https://issues.apache.org/jira/browse/SOLR-15440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christine Poerschke resolved SOLR-15440. ---------------------------------------- Resolution: Fixed > contrib/ltr FieldValueFeature: DocValues use for stored fields > -------------------------------------------------------------- > > Key: SOLR-15440 > URL: https://issues.apache.org/jira/browse/SOLR-15440 > Project: Solr > Issue Type: Sub-task > Components: contrib - LTR > Reporter: Christine Poerschke > Assignee: Christine Poerschke > Priority: Major > Fix For: main (10.0), 9.4 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > SOLR-12697 in Solr 8.9 is intending to add {{FieldValueFeature}} support > "stored=false docValues=true" a.k.a. pure DocValues fields. > The SOLR-12697 changes are implemented in a backwards compatible manner i.e. > existing behaviour for "stored=trued docValues=true" a.k.a. stored DocValues > fields does not change. > This ticket here is to explore how backwards compatibility could potentially > be broken (in a safe manner) in future e.g. > * Solr 9.4 breaks backwards compatibility for {{FieldValueFeature}} but > provides a deprecated {{LegacyFieldValueFeature}} with the existing behaviour > for users who need that. > * Solr 9.X or 10.0 removes the deprecated {{LegacyFieldValueFeature}} class > and users still needing the legacy behaviour need to create and maintain an > equivalent local custom class. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org