[
https://issues.apache.org/jira/browse/SOLR-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076047#comment-18076047
]
ASF subversion and git services commented on SOLR-8127:
-------------------------------------------------------
Commit cac69ae12dad7c4b15e682bb3d6ff98f9ec3d00a in solr's branch
refs/heads/main from Luke Kot-Zaniewski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=cac69ae12da ]
SOLR-8127 Distributed Luke (#4149)
* Fans out to one replica per shard by default when in Solr Cloud mode as well
as with `shards` explicitly specified in non-Cloud mode
* Any index information that can't be aggregated, i.e. directory, version,
indexCommit, etc., will be placed for every *responding* shard in a new shards
response field. This only gets returned when shards.info=true
* docs and docCount were widened to long as they can now overflow. For javabin
codec compatibility the server will narrow these to int for old calling
SolrClients (when it is safe to do so)
* Previously show=doc mode would error if it couldn't find a matching doc but
now returns an empty response and a 200 status code
* show=doc in distributed mode works only with Solr document Id but not with
lucene docId, i.e. "id=..." works but "docId=..." does not.
* When in distributed mode Luke handler will validate index and schema flags of
each field for consistency and error with an informative message in case of any
mismatch.
* You can go back to the old, non-distributed behavior in Cloud mode by
specifying distrib=false
* For single-sharded Solr Clouds there is no behavior change (this is a special
case).
Co-authored-by: David Smiley <[email protected]>
> 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
> 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]
