lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Trivial Update of "MakeSolrMoreSelfService" by MikeKlaas
Date Thu, 09 Nov 2006 22:10:46 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The following page has been changed by MikeKlaas:
http://wiki.apache.org/solr/MakeSolrMoreSelfService

The comment on the change is:
fix some typos

------------------------------------------------------------------------------
  
  = Misc =
  
- Some people feel that there should always be a garunteed method for
+ Some people feel that there should always be a guaranteed method for
- using the StandardRequestHandler -- either by not specifiying a qt
+ using the StandardRequestHandler -- either by not specifiying a `qt`
  (even if some other handler is configured with the name "standard") or
  by using qt=standard (and attempting to register any handler by that
  name is an error)
@@ -111, +111 @@

  
  `/admin/form.jsp` currently has a hard coded list of params, regardless of which plugin
is used.
  
- Assuming the param Configuration information described above is added to the solrconfig.xml,
then the behavior of form.jsp could be driven by the `<params>` specified for the default
handler, and an optional qt param could change the params displayed based on the handler selected
(ie: `form.jsp?qt=foo`).  In this case, displaying the description of the handler would also
be useful.
+ Assuming the param Configuration information described above is added to the solrconfig.xml,
then the behavior of form.jsp could be driven by the `<params>` specified for the default
handler, and an optional `qt` param could change the params displayed based on the handler
selected (ie: `form.jsp?qt=foo`).  In this case, displaying the description of the handler
would also be useful.
  
- In addition, form.jsp should look at it's query params for any options that match the params
of the specified qt and change the default form values accordingly (this would allow people
to link to the form with values that override the defaults)
+ In addition, form.jsp should look at it's query params for any options that match the params
of the specified `qt` and change the default form values accordingly (this would allow people
to link to the form with values that override the defaults)
  
- The main `/admin` screen should also be changed, so instead of (or in addition to) the "Full
Interface" link ro form.jsp, there is a form with a pulldown listing each handler `qt` option.
+ The main `/admin` screen should also be changed, so instead of (or in addition to) the "Full
Interface" link to `form.jsp`, there is a form with a pulldown listing each handler `qt` option.
  
  
- The bottom of `form.jsp` may also be a good place to lst all of the registered handlers,
with their descriptions, and the info from the SolrMBean interface methods (or maybe this
should be a seperate page).  Each should have a link back to `form.jsp?qt=__their_qt__`  
+ The bottom of `form.jsp` may also be a good place to lst all of the registered handlers,
with their descriptions, and the info from the `SolrMBean` interface methods (or maybe this
should be a seperate page).  Each should have a link back to `form.jsp?qt=__their_qt__`  
  
  
  = Schema Explorer =
  
- Having a link to the schema.xml file from the `/admin` screen is usefull, but 
+ Having a link to the `schema.xml` file from the `/admin` screen is useful, but 
  given the way fields can inherit/override options form their fieldtype, it's not allways
easy to understand what you are looking at.
  
  A Schema Explorer page should exist, with features like...
@@ -142, +142 @@

  Whenever a field type is displayed "with details", show...
    * the description
    * backing class
-   * options (ie: omitNorms, stored, positionIncrimentGap, etc...)
+   * options (ie: `omitNorms`, `stored`, `positionIncrimentGap`, etc...)
    * analyzer and/or tokenizer/filter chain if they exist
      * descriptions of each if they exist
    * A list of the fields that using this fieldtype (with some indication wether they override
any options) and a link to their details.
@@ -156, +156 @@

      * descriptions of each if they exist
    * list of any fields that this field copies from
    * list of any fields that this field copies to
-   * link to analysis.jsp for this field (this should work even with suffix/prefix dynamic
fields)
+   * link to `analysis.jsp` for this field (this should work even with suffix/prefix dynamic
fields)
  
  = Similarity Info =
  
  == similarity.jsp ==
  
- Along the same links as analysis.jsp, it would be usefull if there was a simple URL that
helped understand what the registered Similarity class was doing.  Each of the methods could
be represented by a small form for entering inputs, and the results of hte function calls
would be returned.
+ Along the same links as `analysis.jsp`, it would be useful if there was a simple URL that
helped understand what the registered `Similarity` class was doing.  Each of the methods could
be represented by a small form for entering inputs, and the results of hte function calls
would be returned.
  
- In the case of lengthNorm, both the raw value returned, as well as the value after it has
been passed through `decodeNorm(encodeNorm(lengthNorm(...)))` should be reutrned.
+ In the case of `lengthNorm`, both the raw value returned, as well as the value after it
has been passed through `decodeNorm(encodeNorm(lengthNorm(...)))` should be returned.
  
- For functions ("f") that take in integer or float arguments, the form should allow a min/max/incriment
triples to be specified, and should return the list resulting from...
+ For functions ("f") that take in integer or float arguments, the form should allow a min/max/increment
triples to be specified, and should return the list resulting from...
     {{{
-    for (int i = min; i <= max; i+=incriment) {
+    for (int i = min; i <= max; i+=increment) {
        list.add( f(i) );
     }
  }}}
@@ -178, +178 @@

  
  == analysis.jsp changes ==
  
- When displaying the tokens resulting from "Indexing" analysis, the number of tokens (and
the field name) could be passed to `decodeNorm(encodeNorm(lengthNorm(...)))` to display what
the lengthNorm would be for documents that had that text as it's whole value.  (this should
check opitNorms for the specified field of course).
+ When displaying the tokens resulting from "Indexing" analysis, the number of tokens (and
the field name) could be passed to `decodeNorm(encodeNorm(lengthNorm(...)))` to display what
the lengthNorm would be for documents that had that text as it's whole value.  (this should
check `omitNorms` for the specified field of course).
  
  When displaying the the tokens resulting from "Query" analysis, the idf for each Term (and
the idf form all of hte terms as a phrase) can be displayed.
  

Mime
View raw message