[
https://issues.apache.org/jira/browse/CAMEL-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119543#comment-17119543
]
Omar Al-Safi edited comment on CAMEL-15130 at 5/29/20, 12:29 PM:
-----------------------------------------------------------------
[~gnodet] I mean the generated config for debezium connectors, for example in
camel-debezium-mysql, are still generated like this:
{code}
@UriParam(label = LABEL_NAME, defaultValue = "500")
private long pollIntervalMs = 500;
{code}
As result, isn't yet known for these fields you can use extended syntax, e.g
`0.5s`. I am working on this now on CAMEL-15136, so the generated config
something like this:
{code}
@UriParam(label = LABEL_NAME, defaultValue = "0.5s", javaType =
"java.time.Duration")
private long pollIntervalMs = 500;
{code}
In order for the converter to pick these fields as well. I hope it makes sense
now
was (Author: omarsmak):
[~gnodet] I mean the generated config for debezium connectors, for example in
camel-debezium-mysql, are still generated like this:
{code}
@UriParam(label = LABEL_NAME, defaultValue = "500")
private long pollIntervalMs = 500;
{code}
As result, isn't yet known for these fields you can extended syntax, e.g
`0.5s`. I am working on this now on CAMEL-15136, so the generated config
something like this:
{code}
@UriParam(label = LABEL_NAME, defaultValue = "0.5s", javaType =
"java.time.Duration")
private long pollIntervalMs = 500;
{code}
In order for the converter to pick these fields as well. I hope it makes sense
now
> camel-debezium - Source code generated for configurations needs to consider
> durations instead of long for time related fields
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-15130
> URL: https://issues.apache.org/jira/browse/CAMEL-15130
> Project: Camel
> Issue Type: Bug
> Components: tooling
> Affects Versions: 3.4.0
> Reporter: Claus Ibsen
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 3.4.0
>
>
> /**
> * Maximum number of milliseconds to wait for records to flush and
> partition
> * offset data to be committed to offset storage before cancelling the
> * process and restoring the offset data to be committed in a future
> * attempt. The default is 5 seconds.
> */
> private Long offsetCommitTimeoutMs = 5sL;
> /**
> * Interval at which to try committing offsets. The default is 1 minute.
> */
> private Long offsetFlushIntervalMs = 60sL;
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
