<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: volume file async-delete API options in ONTAP Rest API Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Rest-API-Discussions/volume-file-async-delete-API-options/m-p/446682#M556</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;file deletes issued through the API to&amp;nbsp;&lt;SPAN&gt;​/storage​/volumes​/{volume.uuid}​/files​/{path} should be async. From the &lt;A href="https://library.netapp.com/ecmdocs/ECMLP2885799/html/#/storage/file_delete" target="_blank" rel="noopener"&gt;API documentation&lt;/A&gt; - "The number of seconds to allow the call to execute before returning. When doing a POST, PATCH, or DELETE operation on a single record, the default is 0 seconds. This means that if an asynchronous operation is started, the server immediately returns HTTP code 202 (Accepted) along with a link to the job. If a non-zero value is specified for POST, PATCH, or DELETE operations, ONTAP waits that length of time to see if the job completes so it can return something other than 202."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hope this helps!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 07 Aug 2023 02:04:24 GMT</pubDate>
    <dc:creator>AlexDawson</dc:creator>
    <dc:date>2023-08-07T02:04:24Z</dc:date>
    <item>
      <title>volume file async-delete API options</title>
      <link>https://community.netapp.com/t5/ONTAP-Rest-API-Discussions/volume-file-async-delete-API-options/m-p/446482#M554</link>
      <description>&lt;P&gt;Anyone knows if there are possibilities to trigger the "volume file async-delete" commands through REST API or from a non-CLI way ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:46:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Rest-API-Discussions/volume-file-async-delete-API-options/m-p/446482#M554</guid>
      <dc:creator>DanF</dc:creator>
      <dc:date>2025-06-04T09:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: volume file async-delete API options</title>
      <link>https://community.netapp.com/t5/ONTAP-Rest-API-Discussions/volume-file-async-delete-API-options/m-p/446682#M556</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;file deletes issued through the API to&amp;nbsp;&lt;SPAN&gt;​/storage​/volumes​/{volume.uuid}​/files​/{path} should be async. From the &lt;A href="https://library.netapp.com/ecmdocs/ECMLP2885799/html/#/storage/file_delete" target="_blank" rel="noopener"&gt;API documentation&lt;/A&gt; - "The number of seconds to allow the call to execute before returning. When doing a POST, PATCH, or DELETE operation on a single record, the default is 0 seconds. This means that if an asynchronous operation is started, the server immediately returns HTTP code 202 (Accepted) along with a link to the job. If a non-zero value is specified for POST, PATCH, or DELETE operations, ONTAP waits that length of time to see if the job completes so it can return something other than 202."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hope this helps!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 02:04:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Rest-API-Discussions/volume-file-async-delete-API-options/m-p/446682#M556</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2023-08-07T02:04:24Z</dc:date>
    </item>
  </channel>
</rss>

