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

[CX] Wrong bucketname in file gives a bad error message

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • CBAS DP
    • CBAS DP
    • analytics
    • None
    • Untriaged
    • Centos 64-bit
    • Unknown
    • CX Sprint 20, CX Sprint 21

    Description

      1. start the local cluster
      2. My file.txt contains:

      drop dataverse couchbase;
      create dataverse couchbase;
      use couchbase;
      create type `value` as open{};
      create type meta as open

      { id:string, vbid:int32, seq:int64, cas:int64, expiration:int32, flags:int32, rev:int64, lock:int32 }

      ;
      create dataset multiple(`value`) with meta(meta) primary key meta().id;
      create feed multiple_feed using `com.couchbase.analytics.CouchbaseConnectorFactory`(
      ("bucket"="multiple_table_db"),
      ("nodes"="127.0.0.1"),
      ("password"="")
      );
      connect feed multiple_feed to dataset multiple;

      I deliberately gave a bucket-name which doesnt exist on the cluster.

      Issue the curl command, we see the following error message:
      root@slv-s20301_c cbas-install]# curl -s --data pretty=true --data format=CLEAN_JSON --data-urlencode statement@file.txt http://localhost:8095/analytics/service
      {
      "requestID": "ed01ff5d-9ab5-4229-901f-e4b773cf5bc1",
      "signature": "*",
      "errors": [

      { "code": "1", "msg": "OnError while emitting onNext value: com.couchbase.client.core.message.config.BucketConfigResponse.class" }

      ],
      "status": "fatal",
      "metrics":

      { "elapsedTime": "1.553808533s", "executionTime": "1.552442846s", "resultCount": "0", "resultSize": "0" }

      }

      Attachments

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

        Activity

          People

            Prerna.Manaktala Prerna Manaktala (Inactive)
            Prerna.Manaktala Prerna Manaktala (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2h
                2h
                Remaining:
                Remaining Estimate - 2h
                2h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty