Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Ref Guide: minor typos/fixes for 8.1 ref guide

This commit is contained in:
Cassandra Targett 2019-06-07 13:47:09 -05:00
parent 24f7a0bf51
commit c598e27ae7
2 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
solr/solr-ref-guide/src/collections-api.adoc
View File

@ -1533,12 +1533,13 @@ http://localhost:8983/solr/admin/collections?action=COLLECTIONPROP&name=coll&pro
---- ----
[[colstatus]] [[colstatus]]
== COLSTATUS: Detailed low-level status of collection's indexes == COLSTATUS: Detailed Status of a Collection's Indexes
The COLSTATUS command provides a detailed description of the collection status, including low-level index The COLSTATUS command provides a detailed description of the collection status, including low-level index
information about segments and field data. information about segments and field data.
This command also checks the compliance of Lucene index field types with the current Solr collection This command also checks the compliance of Lucene index field types with the current Solr collection
schema and indicates the names of non-compliant fields, ie. Lucene fields with field types incompatible schema and indicates the names of non-compliant fields, i.e., Lucene fields with field types incompatible
(or different) from the corresponding Solr field types declared in the current schema. Such incompatibilities may (or different) from the corresponding Solr field types declared in the current schema. Such incompatibilities may
result from incompatible schema changes or after migration of result from incompatible schema changes or after migration of
data to a different major Solr release. data to a different major Solr release.
@ -1567,7 +1568,7 @@ size and their RAM usage will be provided.
=== COLSTATUS Response === COLSTATUS Response
The response will include an overview of the collection status, the number of The response will include an overview of the collection status, the number of
active / inactive shards and replicas, and additional index information active or inactive shards and replicas, and additional index information
of shard leaders. of shard leaders.
=== Examples using COLSTATUS === Examples using COLSTATUS

6
solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
View File

@ -224,7 +224,7 @@ The following changes impact query behavior.
* Authentication plugins can now intercept internode requests on a per-request basis. * Authentication plugins can now intercept internode requests on a per-request basis.
* The Basic Authentication plugin now has an option `forwardCredentials` to prevent Basic Auth headers from being sent for inter-node requests. * The Basic Authentication plugin now has an option `forwardCredentials` to let Basic Auth headers be forwarded on inter-node requests in case of distributed search, instead of falling back to PKI.
* Metrics are now reported for authentication requests. * Metrics are now reported for authentication requests.
@ -278,7 +278,9 @@ When upgrading to Solr 7.7.x, users should be aware of the following major chang
*Admin UI* *Admin UI*
* The Admin UI now presents a login screen for any users with authentication enabled on their cluster. Clusters with <<basic-authentication-plugin.adoc#basic-authentication-plugin,Basic Authentication>> will prompt users to enter a username and password. On clusters configured to use <<kerberos-authentication-plugin.adoc#kerberos-authentication-plugin,Kerberos Authentication>>, users will be directed to configure their browser to provide an appropriate Kerberos ticket. * The Admin UI now presents a login screen for any users with authentication enabled on their cluster.
Clusters with <<basic-authentication-plugin.adoc#basic-authentication-plugin,Basic Authentication>> will prompt users to enter a username and password.
On clusters configured to use <<kerberos-authentication-plugin.adoc#kerberos-authentication-plugin,Kerberos Authentication>>, authentication is handled transparently by the browser as before, but if authentication fails, users will be directed to configure their browser to provide an appropriate Kerberos ticket.
+ +
The login screen's purpose is cosmetic only - Admin UI-triggered Solr requests were subject to authentication prior to 7.7 and still are today. The login screen changes only the user experience of providing this authentication. The login screen's purpose is cosmetic only - Admin UI-triggered Solr requests were subject to authentication prior to 7.7 and still are today. The login screen changes only the user experience of providing this authentication.