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

ASF GitHub Bot commented on CARBONDATA-239:
-------------------------------------------

Github user sujith71955 commented on a diff in the pull request:

    https://github.com/apache/incubator-carbondata/pull/224#discussion_r82983904
  
    --- Diff: 
core/src/main/java/org/apache/carbondata/scan/scanner/impl/FilterScanner.java 
---
    @@ -78,10 +80,11 @@ public FilterScanner(BlockExecutionInfo 
blockExecutionInfo) {
        * @throws QueryExecutionException
        * @throws FilterUnsupportedException
        */
    -  @Override public AbstractScannedResult scanBlocklet(BlocksChunkHolder 
blocksChunkHolder)
    +  @Override public AbstractScannedResult scanBlocklet(BlocksChunkHolder 
blocksChunkHolder,
    +                                                      QueryStatisticsModel 
queryStatisticsModel)
           throws QueryExecutionException {
         try {
    -      fillScannedResult(blocksChunkHolder);
    +      fillScannedResult(blocksChunkHolder, queryStatisticsModel);
    --- End diff --
    
    Pass the model in constructor so that no need to change in all API


> Failure of one compaction in queue should not affect the others.
> ----------------------------------------------------------------
>
>                 Key: CARBONDATA-239
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-239
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: ravikiran
>            Assignee: ravikiran
>             Fix For: 0.2.0-incubating
>
>
> Failure of one compaction in queue should not affect the others.
> If a compaction is triggered by the user on table1 , and other requests will 
> go to queue.  and if the compaction is failed for table1 then the requests in 
> queue should continue and at the end the beeline will show the failure 
> message to the user.
> if any compaction gets failed for a table which is other than the user 
> requested table then the error in the beeline should not appear.



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

Reply via email to