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

ASF GitHub Bot commented on KAFKA-2714:
---------------------------------------

GitHub user apovzner opened a pull request:

    https://github.com/apache/kafka/pull/393

    KAFKA-2714: Added integration tests for exceptional cases in fetching

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apovzner/kafka cpkafka-84

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/393.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #393
    
----
commit 4f175d813270ae2943dd4466c51bedbf11e819ea
Author: Anna Povzner <a...@confluent.io>
Date:   2015-10-29T22:21:01Z

    MINOR: Added integration tests for exceptional cases in fetching

commit 6aa6aaf4b4f3ebb4f101fc0a5088195d52a2a0ba
Author: Anna Povzner <a...@confluent.io>
Date:   2015-10-30T00:00:50Z

    MINOR: Checking correct values in exceptions thrown in integration tests 
for exceptional cases in fetching

----


> Add integration tests for exceptional cases in Fetching for new consumer
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-2714
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2714
>             Project: Kafka
>          Issue Type: Test
>            Reporter: Anna Povzner
>            Assignee: Anna Povzner
>
> We currently don't have integration tests for exceptional cases in fetches 
> for new consumer. This ticket is to create the following test scenarios:
> 1. When reset policy is NONE, verify that NoOffsetForPartitionException is 
> thrown if no initial position is set.
> 2. When reset policy is NONE, verify that OffsetOutOfRange is thrown if you 
> seek out of range.
> 3. Verify RecordTooLargeException is thrown if a message is too large for the 
> configured fetch size.



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

Reply via email to