[
https://issues.apache.org/jira/browse/SOLR-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080036#comment-18080036
]
Jan Høydahl commented on SOLR-8127:
-----------------------------------
Changelog yaml file for this issue fails to validate
- SOLR-8127-distributed-luke.yml — links is a plain string, not a list
{code:java}
links:
name: SOLR-8127
url: https://issues.apache.org/jira/browse/SOLR-8127
{code}
Should be
{code:java}
links:
- name: SOLR-8127
url: https://issues.apache.org/jira/browse/SOLR-8127
{code}
> 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]
