Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 53AAD200C43 for ; Sun, 26 Mar 2017 20:39:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 524BF160B87; Sun, 26 Mar 2017 18:39:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 975F5160B82 for ; Sun, 26 Mar 2017 20:39:46 +0200 (CEST) Received: (qmail 51131 invoked by uid 500); 26 Mar 2017 18:39:45 -0000 Mailing-List: contact notifications-help@asterixdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.apache.org Delivered-To: mailing list notifications@asterixdb.apache.org Received: (qmail 51122 invoked by uid 99); 26 Mar 2017 18:39:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Mar 2017 18:39:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 42469C0B7C for ; Sun, 26 Mar 2017 18:39:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id jkCwGfX3e_l4 for ; Sun, 26 Mar 2017 18:39:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AACD65F245 for ; Sun, 26 Mar 2017 18:39:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C96F9E0436 for ; Sun, 26 Mar 2017 18:39:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 816AB21DD5 for ; Sun, 26 Mar 2017 18:39:41 +0000 (UTC) Date: Sun, 26 Mar 2017 18:39:41 +0000 (UTC) From: "Chen Luo (JIRA)" To: notifications@asterixdb.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ASTERIXDB-1859) "Exception Message:null" when creating a feed on non-existing type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 26 Mar 2017 18:39:47 -0000 [ https://issues.apache.org/jira/browse/ASTERIXDB-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-1859: -------------------------------- Description: When creating a data feed on a non-existing type, AsterixDB gives an error message: {code}Error: Invalid feed parameters. Exception Message:null.{code} The error message could be more meaningful by informing that user that the type is non-existent. Moreover, no stacktrace is printed to logs. Steps to reproduce: simply create a feed on a non-existing type. {code} create feed Feed1 using socket_adapter ( ("sockets"="red:10001"), ("address-type"="nc"), ("type-name"="unknownType"), ("format"="adm") ) {code} was: When creating a data feed on a non-existing type, AsterixDB gives an error message: "Error: Invalid feed parameters. Exception Message:null". The error message could be more meaningful by informing that user that the type is non-existent. Moreover, no stacktrace is printed to logs. Steps to reproduce: simply create a feed on a non-existing type. create feed Feed1 using socket_adapter ( ("sockets"="red:10001"), ("address-type"="nc"), ("type-name"="unknownType"), ("format"="adm") ); > "Exception Message:null" when creating a feed on non-existing type > ------------------------------------------------------------------ > > Key: ASTERIXDB-1859 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-1859 > Project: Apache AsterixDB > Issue Type: Bug > Components: Feeds > Reporter: Chen Luo > Priority: Minor > > When creating a data feed on a non-existing type, AsterixDB gives an error message: {code}Error: Invalid feed parameters. Exception Message:null.{code} The error message could be more meaningful by informing that user that the type is non-existent. Moreover, no stacktrace is printed to logs. > Steps to reproduce: simply create a feed on a non-existing type. > {code} > create feed Feed1 using socket_adapter > ( > ("sockets"="red:10001"), > ("address-type"="nc"), > ("type-name"="unknownType"), > ("format"="adm") > ) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)