You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Sushil Mohanty (JIRA)" <ji...@apache.org> on 2015/09/02 10:33:46 UTC

[jira] [Assigned] (LENS-265) improve the brief error in case of no fact found error

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

Sushil Mohanty reassigned LENS-265:
-----------------------------------

    Assignee: Sushil Mohanty  (was: Himanshu Gahlaut)

> improve the brief error in case of no fact found error 
> -------------------------------------------------------
>
>                 Key: LENS-265
>                 URL: https://issues.apache.org/jira/browse/LENS-265
>             Project: Apache Lens
>          Issue Type: Improvement
>          Components: cube
>            Reporter: Rajat Khandelwal
>            Assignee: Sushil Mohanty
>             Fix For: 2.4
>
>
> So basically every fact was rejected with a reason. Some reasons are just error codes, some have additional details with them(e.g. in case of column not found, which columns were not found) Now there's an ordering between reasons. The max of reasons is picked and the brief error message is generated based on the facts that were rejected with the max reason and (if exists) any details of the reason. 
> This approach is good enough but there's scope for improvement. The brief error message can also look at the smaller errors and include additional details  for the user. e.g. all facts except one say a column 'c' was not found and one fact says it's not partitioned with the time partition queried. Then final error can say that the column 'c' is not queriable with the given time dimension.
> Consider this jira to be the place to put more such cases. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)