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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Component/s: FUN - Functions
• Assignee: Dmitry Lychagin
• Reporter: Dmitry Lychagin
• Created: 18/Jul/18 03:04
• Updated: 19/Jul/18 05:25
• Resolved: 19/Jul/18 05:25

Description

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.