-
Notifications
You must be signed in to change notification settings - Fork 167
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
Fetch size parameter disscuss. #82
Comments
Hi, |
yes, you are right. If there only have 10 records and fetch size is 100, I want to be able to fetch the 10 records immediately, or return the data currently captured before the fetch size reaches the specified time. |
Hi, is there any solution for this ? |
Hi, |
Is there any general direction? |
What do yo mean by general direction ? |
"I am planning some details to achieve this.", Could you tell me in what way you intend to solve this problem? Overridden some of the oralce JDBC implementation methods? :) |
Not actually. I am planning to add some timer which controls specified duration and propagates data which are not sent to Kafka topic within JDBC fetch process. |
Get it ,thanks, Look forward to your next update~~~ |
Any update? |
Any update about it? I found the performance is not good to fetch the data one by one |
Hi,Erdem
As far as I know,when fetchSize > 1, but sql is 1, logminer will not be able to capture this redo sql due to DB fetch size.
But, when fetchSize = 1, the number of SQL is particularly high,Connector captures very slowly. Is there any way to solve this problem? Like Kafka produce's configuration:"batch.size" and "linger.ms" .
Thanks.
The text was updated successfully, but these errors were encountered: