[jira] [Commented] (ASTERIXDB-2416) Confusing type mismatch error message for internal field access and collection functions

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ASTERIXDB-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548806#comment-16548806 ] 

ASF subversion and git services commented on ASTERIXDB-2416:
------------------------------------------------------------

Commit 4547639bb4fd8aa098ea5402da445b1c5e36a991 in asterixdb's branch refs/heads/master from [~dlychagin-cb]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=4547639 ]

[ASTERIXDB-2416][FUN] Remove some internal function names from error messages

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- Remove function names from type mismatch error messages
  raised by the following functions: field-access-by-index(),
  field-access-by-name(), field-access-nested(),
  any-collection-member(), scan-collection()

Change-Id: I625faf91a33f981964465cc60b77a27f4aecb6a8
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2785
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Till Westmann <ti...@apache.org>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>


> Confusing type mismatch error message for internal field access and collection functions
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-2416
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2416
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: FUN - Functions
>            Reporter: Dmitry Lychagin
>            Assignee: Dmitry Lychagin
>            Priority: Minor
>
> Type mismatch error for internal functions can be confusing for users because it includes the internal function name which is not present in the query. 
> For example, 
> Error: function field-access-by-name expects its 1st input parameter to be type object but the actual input type is string
> The proposal is to eliminate function name and parameter number from the error message for the following internal functions: any-collection-member(), scan-collection(), field-access-by-index(), field-access-by-name(), field-access-nested()
> The source location information should be sufficient for user to identify the problem.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)