[ 
https://issues.apache.org/jira/browse/SOLR-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex K updated SOLR-8127:
-------------------------
    Description: 
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.

  was: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.


> Luke 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
>              Labels: dynamic, luke, replication, sharding
>
> 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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to