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

SOLR-14792: Remove /browse references from example and docs

This commit is contained in:
Erik Hatcher 2020-10-01 10:57:57 -04:00
parent 1af17a5f01
commit 45dc2615c7
4 changed files with 3 additions and 60 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
solr/example/films/README.md
View File

@ -69,29 +69,6 @@ This data consists of the following fields:
http://localhost:8983/solr/films/query?q=*:*&facet=true&facet.field=genre
- Browse the indexed films in a traditional browser search interface:
http://localhost:8983/solr/films/browse
Now browse including the genre field as a facet:
http://localhost:8983/solr/films/browse?facet.field=genre
If you want to set a facet for /browse to keep around for every request add the facet.field into the "facets"
param set (which the /browse handler is already configured to use):
```
curl http://localhost:8983/solr/films/config/params -H 'Content-type:application/json' -d '{
"update" : {
"facets": {
"facet.field":"genre"
}
}
}'
```
And now http://localhost:8983/solr/films/browse will display the _genre_ facet automatically.
Exploring the data further -
* Increase the MAX_ITERATIONS value, put in your freebase API_KEY and run the film_data_generator.py script using Python 3.
@ -133,29 +110,6 @@ curl http://localhost:8983/solr/films/schema -X POST -H 'Content-type:applicatio
}
}'
bin/post -c films example/films/films.json
curl http://localhost:8983/solr/films/config/params -H 'Content-type:application/json' -d '{
"update" : {
"facets": {
"facet.field":"genre"
}
}
}'
# END_OF_SCRIPT
```
Additional fun -
```
Add highlighting:
curl http://localhost:8983/solr/films/config/params -H 'Content-type:application/json' -d '{
"set" : {
"browse": {
"hl":"on",
"hl.fl":"name"
}
}
}'
```
try http://localhost:8983/solr/films/browse?q=batman now, and you'll see "batman" highlighted in the results

2
solr/solr-ref-guide/src/initparams-in-solrconfig.adoc
View File

@ -31,7 +31,7 @@ For example, here is one of the `<initParams>` sections defined by default in th
[source,xml]
----
<initParams path="/update/**,/query,/select,/tvrh,/elevate,/spell,/browse">
<initParams path="/update/**,/query,/select,/tvrh,/elevate,/spell">
<lst name="defaults">
<str name="df">_text_</str>
</lst>

2
solr/solr-ref-guide/src/rule-based-authorization-plugin.adoc
View File

@ -241,7 +241,7 @@ The predefined permission names (and their effects) are:
** CLUSTERSTATUS
** REQUESTSTATUS
* *update*: this permission is allowed to perform any update action on any collection. This includes sending documents for indexing (using an <<requesthandlers-and-searchcomponents-in-solrconfig.adoc#updaterequesthandlers,update request handler>>). This applies to all collections by default (`collection:"*"`).
* *read*: this permission is allowed to perform any read action on any collection. This includes querying using search handlers (using <<requesthandlers-and-searchcomponents-in-solrconfig.adoc#searchhandlers,request handlers>>) such as `/select`, `/get`, `/browse`, `/tvrh`, `/terms`, `/clustering`, `/elevate`, `/export`, `/spell`, `/clustering`, and `/sql`. This applies to all collections by default ( `collection:"*"` ).
* *read*: this permission is allowed to perform any read action on any collection. This includes querying using search handlers (using <<requesthandlers-and-searchcomponents-in-solrconfig.adoc#searchhandlers,request handlers>>) such as `/select`, `/get`, `/tvrh`, `/terms`, `/clustering`, `/elevate`, `/export`, `/spell`, `/clustering`, and `/sql`. This applies to all collections by default ( `collection:"*"` ).
* *all*: Any requests coming to Solr.
=== Permission Ordering and Resolution

13
solr/solr-ref-guide/src/solr-tutorial.adoc
View File

@ -751,11 +751,7 @@ There are a great deal of other parameters available to help you control how Sol
==== Range Facets
For numerics or dates, it's often desirable to partition the facet counts into ranges rather than discrete values. A prime example of numeric range faceting, using the example techproducts data from our previous exercise, is `price`. In the `/browse` UI, it looks like this:
.Range facets
image::images/solr-tutorial/tutorial-range-facet.png[Solr Quick Start: Range facets]
For numerics or dates, it's often desirable to partition the facet counts into ranges rather than discrete values. A prime example of numeric range faceting, using the example techproducts data from our previous exercise, is `price`.
The films data includes the release date for films, and we could use that to create date range facets, which are another common use for range facets.
The Solr Admin UI doesn't yet support range facet options, so you will need to use curl or similar command line tool for the following examples.
@ -956,13 +952,6 @@ Solr has sophisticated geospatial support, including searching within a specifie
Some of the example techproducts documents we indexed in Exercise 1 have locations associated with them to illustrate the spatial capabilities. To reindex this data, see <<index-the-techproducts-data,Exercise 1>>.
Spatial queries can be combined with any other types of queries, such as in this example of querying for "ipod" within 10 kilometers from San Francisco:
.Spatial queries and results
image::images/solr-tutorial/tutorial-spatial.png[Solr Quick Start: spatial search]
This is from Solr's example search UI (called `/browse`), which has a nice feature to show a map for each item and allow easy selection of the location to search near. You can see this yourself by going to <http://localhost:8983/solr/techproducts/browse?q=ipod&pt=37.7752%2C-122.4232&d=10&sfield=store&fq=%7B%21bbox%7D&queryOpts=spatial&queryOpts=spatial> in a browser.
To learn more about Solr's spatial capabilities, see the section <<spatial-search.adoc#spatial-search,Spatial Search>>.
== Wrapping Up