-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
partition and offset #3
Comments
In standalone mode, the offset is stored as a file in local filesystem. In distributed mode, the offset is stored in kafka topic. When the connector is up again, it will try to recover from last offset first. |
it doesn't work, I show you my worker.properties file and the connector properties file Am I doing something wrong? |
@darthmiguel check /tmp/connect.offsets to see if the offset is correctly written into file. |
�� |
Do you fix your probem? I have the same one as you do @darthmiguel |
@sd1700092 @darthmiguel Did you find a solution to this? |
I was able to capture the LPUSH command and obtain the value to put it on my kafka topic. The problem that I have now is: I stop the connector and when it resumes, it doesn't read from it left off.
So I can't read whatever data that was entered to redis while the connector was down.
Any ideas???
The text was updated successfully, but these errors were encountered: