Jdurham2843 commented on code in PR #1126:
URL: https://github.com/apache/solr/pull/1126#discussion_r1007230522


##########
solr/solr-ref-guide/modules/deployment-guide/pages/backup-restore.adoc:
##########
@@ -234,38 +234,43 @@ 
http://localhost:8983/solr/gettingstarted/replication?command=restorestatus&wt=x
 The status value can be "In Progress", "success" or "failed".
 If it failed then an "exception" will also be sent in the response.
 
-=== Create Snapshot API
+[[create-snapshot-api]]
+== CREATE: Create a Snapshot
 
 The snapshot functionality is different from the backup functionality as the 
index files aren't copied anywhere.
 The index files are snapshotted in the same index directory and can be 
referenced while taking backups.
 
 You can trigger a snapshot command with an HTTP command like this (replace 
"techproducts" with the name of the core you are working with):
 
-.Create Snapshot API Example
-[source,text]
+[.dynamic-tabs]
+--
+[example.tab-pane#v1createsnapshot]
+====
+[.tab-label]*V1 API*
+
+[source,bash]
 ----
-http://localhost:8983/solr/admin/cores?action=CREATESNAPSHOT&core=techproducts&commitName=commit1
+curl -X POST 
http://localhost:8983/solr/admin/cores?action=CREATESNAPSHOT&core=techproducts&commitName=commit1
+
 ----
+====
 
-The `CREATESNAPSHOT` request parameters are:
+[example.tab-pane#v2createsnapshot]
+====
+[.tab-label]*V2 API*
 
-`commitName`::
-+
-[%autowidth,frame=none]
-|===
-|Optional |Default: none
-|===
-+
-The name to store the snapshot as.
+With the v2 API, the core and snapshot names are part of the path, no longer 
query parameters.

Review Comment:
   No problem! I actually just copied the structure from elsewhere in the docs, 
so it wasn't much work on my part. I did go ahead and change the wording since 
I thought the "instead of" read better.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to