[ 
https://issues.apache.org/jira/browse/SOLR-8713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169829#comment-15169829
 ] 

Shawn Heisey commented on SOLR-8713:
------------------------------------

bq. points towards Solr 4.x wiki

The moinmoin wiki is *not* for 4.x.  A lot of the content has gotten out of 
date, but other parts of it are updated regularly and have fully current 
information.

That older wiki needs an overhaul.  Some of the information needs to be removed 
because the information in the reference guide is better and completely 
supersedes what's there now, but there is still some value in having duplicate 
information for certain topics, because the wiki version can be presented 
differently, in a format that's better for quick lookups than the reference 
guide, which is intended to be full documentation.  A good example of this is 
the following page:

https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters

I use this page all the time, because it's easily searchable for a particular 
analysis component and has quick-n-dirty examples.  I don't recall seeing 
anything in the reference guide like that page.


> New UI points to the wiki for Query Syntax instead of the Reference Guide
> -------------------------------------------------------------------------
>
>                 Key: SOLR-8713
>                 URL: https://issues.apache.org/jira/browse/SOLR-8713
>             Project: Solr
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: master
>            Reporter: Tomás Fernández Löbbe
>            Priority: Trivial
>              Labels: newdev
>
> Old Admin UI points to 
> https://cwiki.apache.org/confluence/display/solr/Query+Syntax+and+Parsing but 
> the new one points to http://wiki.apache.org/solr/SolrQuerySyntax



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to