[
https://issues.apache.org/jira/browse/SOLR-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18083956#comment-18083956
]
Lucas Kot-Zaniewski commented on SOLR-8127:
-------------------------------------------
[~dsmiley] I've added a [PR to backport this to
9.11|https://github.com/apache/solr/pull/4472] as it is slightly less than
trivial. The main issue are around backwards compatibility of the default
narrowing behavior only applying to solrj clients while leaving xml clients
with potentially breaking behavior. Rolling back to the old behavior is pretty
trivial (distrib=false) but could be made more prominent in the docs. I've
commented on the sections I'm most concerned about. If you have some cycles I'd
appreciate a quick look. To be clear this still breaks for 10.0->10.1
migrations but I suppose there will probably be far fewer of those than
9.10->9.11
> Luke request handler does not know about dynamic fields on other shards fast
> enough
> -----------------------------------------------------------------------------------
>
> Key: SOLR-8127
> URL: https://issues.apache.org/jira/browse/SOLR-8127
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis, SolrCloud
> Affects Versions: 4.10.2
> Environment: 3 shards
> Reporter: Alex K
> Assignee: Lucas Kot-Zaniewski
> Priority: Major
> Labels: dynamic, luke, pull-request-available, replication,
> sharding
> Time Spent: 5h
> Remaining Estimate: 0h
>
> Add a document with a new (never seen before) dynamic field. It will not be
> visible through Luke requests on the other shards for quite a while, and
> there is no documentation regarding exactly how long it will take. The result
> is that a query to Luke must be made to every shard in the cluster if all
> dynamic fields are needed.
> All shards should be aware of a new dynamic field within seconds, if not
> milliseconds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
