Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-41921

FTS backup endpoint returns a empty body until an index has been created

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 7.0.0
    • Cheshire-Cat
    • fts
    • None
    • Untriaged
    • 1
    • No

    Description

      What's the issue?
      Sending a GET request to the '/api/v1/backup' or '/api/v1/bucket/default/backup' endpoint when no FTS indexes/aliases have been created yet returns an empty body.

      What do I expect to see?
      I would expect to see a normal empty response be returned in the same fashion as the previous FTS backup/restore endpoints.

      $ curl -s -u Administrator:asdasd "localhost:9206/api/index" | jq
      {
        "status": "ok",
        "indexDefs": null
      }
      

      What am I actually seeing?
      Before I create an index, I'm seeing:

      $ curl -u Administrator:asdasd "localhost:9206/api/v1/bucket/default/backup?include=default"
      curl: (52) Empty reply from server
      

      After creating and removing an index I'm seeing:

      $ curl -s -u Administrator:asdasd "localhost:9206/api/v1/bucket/default/backup?include=default" | jq
      {
        "status": "ok",
        "indexDefs": {
          "uuid": "7b51d96ca98a220a",
          "indexDefs": {},
          "implVersion": "5.5.0"
        }
      }
      

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              james.lee James Lee
              james.lee James Lee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty