[
https://issues.apache.org/jira/browse/SOLR-11646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446252#comment-16446252
]
ASF subversion and git services commented on SOLR-11646:
--------------------------------------------------------
Commit 5915e61e42aa0311b8b574949fed8a2ec566a502 in lucene-solr's branch
refs/heads/branch_7x from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5915e61 ]
SOLR-11646: more v2 examples; redesign Implicit Handler page to add v2 api
paths where they exist
> Ref Guide: Update API examples to include v2 style examples
> -----------------------------------------------------------
>
> Key: SOLR-11646
> URL: https://issues.apache.org/jira/browse/SOLR-11646
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation, v2 API
> Reporter: Cassandra Targett
> Assignee: Cassandra Targett
> Priority: Major
>
> The Ref Guide currently only has a single page with what might be generously
> called an overview of the v2 API added in 6.5
> (https://lucene.apache.org/solr/guide/v2-api.html) but most of the actual
> APIs that support the v2 approach do not show an example of using it with the
> v2 style. A few v2-style APIs are already used as examples, but there's
> nothing consistent.
> With this issue I'll add API input/output examples throughout the Guide. Just
> in terms of process, my intention is to have a series of commits to the pages
> as I work through them so we make incremental progress. I'll start by adding
> a list of pages/APIs to this issue so the scope of the work is clear.
> Once this is done we can figure out what to do with the V2 API page itself -
> perhaps it gets archived and replaced with another page that describes Solr's
> APIs overall; perhaps by then we figure out something else to do with it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
