Uploaded image for project: 'Apache AsterixDB'
  1. Apache AsterixDB
  2. ASTERIXDB-1860

Inconsistent behavior w.r.t. connecting/disconnecting feed to a non-existing dataset

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: ING - Ingestion
    • Labels:
      None

      Description

      Connecting a feed to a non-existing dataset (whose name is 'unknown_dataset') is successful, and the system shows the message:

      Success: Query Complete.

      However, disconnecting this feed to this dataset is rejected with error message:

      Unknown target dataset :unknown_dataset [CompilationException].

      Then, connecting this feed to the dataset again gives:

      FeedTweetFeed is already connected dataset unknown_dataset [AlgebricksException].

      Thus, it seems once a feed is connected to a non-existing dataset, it cannot be disconnected from it.

      Steps to reproduce:

      1. create a feed named Feed1;
      2. connect Feed1 to a non-existing dataset, e.g., unknown_dataset:
        connect feed Feed1 to dataset unknown_dataset;
        

        Now Feed1 is successfully connected to unknown_dataset.

      3. disconnect Feed1 from unknown_dataset:
        disconnect feed Feed1 from dataset unknown_dataset;
        

        This command is rejected because unknown_dataset is not existing.

      4. connect Feed1 to unknown_dataset again:
        connect feed Feed1 to dataset unknown_dataset;
        

        The system shows Feed1 is already connected to unknown_dataset.

        Attachments

          Activity

            People

            • Assignee:
              idleft Xikui Wang
              Reporter:
              luochen01 Chen Luo
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: