[
https://issues.apache.org/jira/browse/SOLR-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943612#comment-14943612
]
Upayavira commented on SOLR-8127:
---------------------------------
The Luke Request Handler inquires of an index, not a collection. Therefore,
adding a document with a not-yet-seen dynamic field to another shard will never
show on the current shard. This functionality long precedes SolrCloud and has
not been updated to take account of it. You must think of the
LukeRequestHandler as requesting index information relating to the shard you
are querying, and no others.
Not sure if there is something to be done with this ticket. Converting the
LukeRequestHandler to handle distributed requests would be neat, but isn't what
is described here.
> 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
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
