[
https://issues.apache.org/jira/browse/KYLIN-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174018#comment-17174018
]
ASF GitHub Bot commented on KYLIN-4683:
---------------------------------------
hit-lacus commented on pull request #1351:
URL: https://github.com/apache/kylin/pull/1351#issuecomment-671133465
> > Thank you for you effort that you spend on this issue, here is my
suggestion, what do you think?
> > If `offset` is null, please just set it to zero.
>
> I wonder if there is any difference between setting offset to zero and
seekToBeginning.
Please correct me if I was wrong.
Let take the above test by me as an example, after scale up, it should
continue its consumptation from this position:
```json
{
"0":363171,
"1":363198,
"2":363249,
"3":363171,
"4":363199,
"5":363250,
"6":363170,
"7":363196,
"8":363250,
"9":363170,
"10":0,
"11":0,
"12":0,
"13":0,
"14":0,
"15":0
}
```
not this position:
```json
{
"0":0,
"1":0,
"2":0,
"3":0,
"4":0,
"5":0,
"6":0,
"7":0,
"8":0,
"9":0,
"10":0,
"11":0,
"12":0,
"13":0,
"14":0,
"15":0
}
```
So, if you are using `seekToBeginning` API, can you make sure the partition
0 to partition 9 consume at right position?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Fail to consume kafka when partition number get larger
> ------------------------------------------------------
>
> Key: KYLIN-4683
> URL: https://issues.apache.org/jira/browse/KYLIN-4683
> Project: Kylin
> Issue Type: Bug
> Affects Versions: v3.0.2
> Reporter: tianhui
> Priority: Major
> Attachments: image-2020-08-05-17-20-37-270.png
>
>
> I run a testing streaming cube with kafka. At first, the topic has 3
> partitions, and the cube running smoothly. But after I alter kafka topic to 7
> partitions, all receivers stop consuming. !image-2020-08-05-17-20-37-270.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
