You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by tzulitai <gi...@git.apache.org> on 2017/08/11 08:05:25 UTC

[GitHub] flink pull request #4526: [FLINK-7407] [kafka] Adapt AbstractPartitionDiscov...

GitHub user tzulitai opened a pull request:

    https://github.com/apache/flink/pull/4526

    [FLINK-7407] [kafka] Adapt AbstractPartitionDiscoverer to handle non-contiguous partition metadata

    ## What is the purpose of the change
    
    Previously, the `AbstractPartitionDiscoverer` tracked discovered partitions by keeping only the largest discovered partition id. All fetched partition metadata with ids smaller than this id would be
    considered as discovered. This assumption of contiguous partition ids is too naive for corner cases where there may be undiscovered partitions that were temporarily unavailable before and were later on always shadowed by discovered partitions with larger partition ids.
    
    ## Brief change log
    
    - Change the use of `Map<String, Integer> topicToLargestDiscoveredId` to a simple `Set<KafkaTopicPartition>` to track already discovered partitions.
    - Minor `hotfix` to remove unused method in `AbstractPartitionDiscoverer`.
    
    ## Verifying this change
    
    This change is verified by a new `AbstractPartitionDiscovererTest.testNonContiguousPartitionIdDiscovery` test. The test features the case where fetched partition metadata is non-contiguous and may have smaller missing partition ids.
    
    Other aspects should be covered by existing tests in `AbstractPartitionDiscovererTest`.
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): **no**
      - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: **no**
      - The serializers: **no**
      - The runtime per-record code paths (performance sensitive): **no**
      - Anything that affects deployment or recovery: **no**
    
    ## Documentation
    
      - Does this pull request introduce a new feature? **no**
      - If yes, how is the feature documented? **not applicable**
    


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

    $ git pull https://github.com/tzulitai/flink FLINK-7407

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

    https://github.com/apache/flink/pull/4526.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 #4526
    
----
commit b29bcb4a19268a1ad212b85cb7de633f23c0a3c6
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
Date:   2017-08-11T07:53:46Z

    [FLINK-7407] [kafka] Adapt AbstractPartitionDiscoverer to handle non-contiguous partition metadata
    
    Previously, the AbstractPartitionDiscoverer tracked discovered
    partitions by keeping only the largest discovered partition id. All
    fetched partition metadata with ids smaller than this id would be
    considered as discovered. This assumption of contiguous partition ids is
    too naive for corner cases where there may be undiscovered partitions
    that were temporariliy unavilable before and were shadowed by
    discoverered partitions with largerer partition ids.
    
    This commit changes to use a set to track seen partitions. This also
    removes the need of pre-sorting fetched partitions.

commit 2dd84c8ba468fcf8552ce8f6a6f4d5c4eb7e4a10
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
Date:   2017-08-11T07:57:52Z

    [hotfix] [kafka] Remove unused shouldAssignToThisSubtask method in AbstractPartitionDiscoverer

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink issue #4526: [FLINK-7407] [kafka] Adapt AbstractPartitionDiscoverer to...

Posted by tzulitai <gi...@git.apache.org>.
Github user tzulitai commented on the issue:

    https://github.com/apache/flink/pull/4526
  
    @aljoscha not yet, this is still mixed in one of my unmerged bathces. Merging this now ..


---

[GitHub] flink pull request #4526: [FLINK-7407] [kafka] Adapt AbstractPartitionDiscov...

Posted by tzulitai <gi...@git.apache.org>.
Github user tzulitai closed the pull request at:

    https://github.com/apache/flink/pull/4526


---

[GitHub] flink issue #4526: [FLINK-7407] [kafka] Adapt AbstractPartitionDiscoverer to...

Posted by tzulitai <gi...@git.apache.org>.
Github user tzulitai commented on the issue:

    https://github.com/apache/flink/pull/4526
  
    Thanks for the review @aljoscha!
    Merging this ..


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink issue #4526: [FLINK-7407] [kafka] Adapt AbstractPartitionDiscoverer to...

Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha commented on the issue:

    https://github.com/apache/flink/pull/4526
  
    Looks good! 👍 This even makes the code simpler.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink issue #4526: [FLINK-7407] [kafka] Adapt AbstractPartitionDiscoverer to...

Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha commented on the issue:

    https://github.com/apache/flink/pull/4526
  
    @tzulitai Did you end up merging this?


---