[ 
https://issues.apache.org/jira/browse/FLINK-12271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-12271:
-----------------------------------
    Labels: auto-deprioritized-major auto-unassigned pull-request-available 
stale-minor  (was: auto-deprioritized-major auto-unassigned 
pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Display input field name list when throw Cannot resolve field exception
> -----------------------------------------------------------------------
>
>                 Key: FLINK-12271
>                 URL: https://issues.apache.org/jira/browse/FLINK-12271
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API
>            Reporter: Hequn Cheng
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available, stale-minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, when we select a field that does not exist, an cannot solve field 
> exception is thrown. For example,
> {code:java}
> org.apache.flink.table.api.ValidationException: Cannot resolve field [_4]
> {code}
> It would be better to also display the input field list to indicate existing 
> fields, such as: 
> {code:java}
> org.apache.flink.table.api.ValidationException: Cannot resolve field [_4], 
> input field list:[_1, _2, _3].
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to