[jira] [Commented] (CAMEL-16992) [Website] Various version related changes
[
https://issues.apache.org/jira/browse/CAMEL-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418846#comment-17418846
]
ASF GitHub Bot commented on CAMEL-16992:
github-actions[bot] commented on pull request #628:
URL: https://github.com/apache/camel-website/pull/628#issuecomment-925354388
Preview is available at https://pr-628--camel.netlify.app
--
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.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Website] Various version related changes
> -
>
> Key: CAMEL-16992
> URL: https://issues.apache.org/jira/browse/CAMEL-16992
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: David Jencks
>Assignee: David Jencks
>Priority: Major
>
> This includes several version related changes to the website:
> * Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot,
> and camel-karat.
> * Mark the 'latest' camel version as prerelease and set the display-version
> to "3.12.0 (Prerelease)"
> * Encourage xrefs to go to the correct version by moving the "eip-vc"
> attribute to the user-manual component descriptor (the only component it
> should be used from) and removing all uses of it and 'latest@component' from
> the components component in the main, 3.11.x, and 3.7.x branches of camel.
>
> After the first round of PRs for main, camel-3.11.x, camel-3.7.x, camel-2.x
> and camel-website I realized there are still some problems with links to
> `latest@component` from the user-manual and 2.x. We should not link to
> unreleased doc versions, so these should link to (currently) 3.11.x. Now
> that 'latest' is marked prerelease, leaving out the version in the xref will
> result in this behavior. Since this will make the eip-vc attribute just
> `components` I'm going to replace uses of {eip-vc} with its value. This will
> affect main user-manual and camel-2.x.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16992) [Website] Various version related changes
[
https://issues.apache.org/jira/browse/CAMEL-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated CAMEL-16992:
-
Description:
This includes several version related changes to the website:
* Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot, and
camel-karat.
* Mark the 'latest' camel version as prerelease and set the display-version to
"3.12.0 (Prerelease)"
* Encourage xrefs to go to the correct version by moving the "eip-vc" attribute
to the user-manual component descriptor (the only component it should be used
from) and removing all uses of it and 'latest@component' from the components
component in the main, 3.11.x, and 3.7.x branches of camel.
After the first round of PRs for main, camel-3.11.x, camel-3.7.x, camel-2.x and
camel-website I realized there are still some problems with links to
`latest@component` from the user-manual and 2.x. We should not link to
unreleased doc versions, so these should link to (currently) 3.11.x. Now that
'latest' is marked prerelease, leaving out the version in the xref will result
in this behavior. Since this will make the eip-vc attribute just `components`
I'm going to replace uses of {eip-vc} with its value. This will affect main
user-manual and camel-2.x.
was:
This includes several version related changes to the website:
* Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot, and
camel-karat.
* Mark the 'latest' camel version as prerelease and set the display-version to
"3.12.0 (Prerelease)"
* Encourage xrefs to go to the correct version by moving the "eip-vc" attribute
to the user-manual component descriptor (the only component it should be used
from) and removing all uses of it and 'latest@component' from the components
component in the main, 3.11.x, and 3.7.x branches of camel.
> [Website] Various version related changes
> -
>
> Key: CAMEL-16992
> URL: https://issues.apache.org/jira/browse/CAMEL-16992
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: David Jencks
>Assignee: David Jencks
>Priority: Major
>
> This includes several version related changes to the website:
> * Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot,
> and camel-karat.
> * Mark the 'latest' camel version as prerelease and set the display-version
> to "3.12.0 (Prerelease)"
> * Encourage xrefs to go to the correct version by moving the "eip-vc"
> attribute to the user-manual component descriptor (the only component it
> should be used from) and removing all uses of it and 'latest@component' from
> the components component in the main, 3.11.x, and 3.7.x branches of camel.
>
> After the first round of PRs for main, camel-3.11.x, camel-3.7.x, camel-2.x
> and camel-website I realized there are still some problems with links to
> `latest@component` from the user-manual and 2.x. We should not link to
> unreleased doc versions, so these should link to (currently) 3.11.x. Now
> that 'latest' is marked prerelease, leaving out the version in the xref will
> result in this behavior. Since this will make the eip-vc attribute just
> `components` I'm going to replace uses of {eip-vc} with its value. This will
> affect main user-manual and camel-2.x.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16995) [camel-karaf] Support multiple CamelContexts in CamelBlueprintTestSupport
Gert Vanthienen created CAMEL-16995: --- Summary: [camel-karaf] Support multiple CamelContexts in CamelBlueprintTestSupport Key: CAMEL-16995 URL: https://issues.apache.org/jira/browse/CAMEL-16995 Project: Camel Issue Type: Improvement Components: karaf Affects Versions: 3.11.2 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: 3.12.0 When using the CamelBlueprintTestSupport class on a larger project, you can easily end up with a situation where multiple bundles contain Blueprint descriptors containing a CamelContext. The CamelBlueprintTestSupport class currently uses the first available CamelContext in the registry, but it would be nice if you could explicitly indicate which context you want to test. An OSGi filter expression would be a good way to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13768) camel-kafka: seek to specific offset and KafkaConsumer access
[
https://issues.apache.org/jira/browse/CAMEL-13768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-13768:
-
Summary: camel-kafka: seek to specific offset and KafkaConsumer access
(was: Seek to specific offset and KafkaConsumer access )
> camel-kafka: seek to specific offset and KafkaConsumer access
> --
>
> Key: CAMEL-13768
> URL: https://issues.apache.org/jira/browse/CAMEL-13768
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 2.24.1, 3.x
>Reporter: michael elbaz
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.12.0
>
>
> 1. Provide a way to rewind kafka offset to specific offset (improve seekTo ?)
> there is no way to do that using camel-kafka component. The main idea is to
> replay older kafka messages without starting from the beginning.
>for example:
> https://blog.sysco.no/integration/kafka-rewind-consumers-offset/
> {code:java}
> boolean flag = true;
> while (true) {
> ConsumerRecords records = consumer.poll(100);
> if(flag) {
> Map query = new HashMap<>();
> query.put(
> new TopicPartition("simple-topic-1", 0),
> Instant.now().minus(10, MINUTES).toEpochMilli());
> // Get offset from timestamp
> Map result =
> consumer.offsetsForTimes(query);
> // Rewind offset to previous position using seekTo
> result.entrySet()
> .stream()
> .forEach(entry -> consumer.seek(entry.getKey(),
> entry.getValue().offset()));
> flag = false;
> }
> for (ConsumerRecord record : records)
> System.out.printf("offset = %d, key = %s, value = %s%n",
> record.offset(), record.key(), record.value());
> }
> {code}
> 2. Provide a way to access kafkaConsumer
>Add camel header with reference to kafkaConsumer to be able to perform
> some Kafka api call.We can use the same way that we do with KafkaManualCommit
> {code:java}
> public void process(Exchange exchange) {
> KafkaManualCommit manual =
> exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> KafkaManualCommit.class);
> manual.commitSync();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15403) camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
[
https://issues.apache.org/jira/browse/CAMEL-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418669#comment-17418669
]
Freeman Yue Fang commented on CAMEL-15403:
--
[~coheigea], sure ,done!
> camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
> --
>
> Key: CAMEL-15403
> URL: https://issues.apache.org/jira/browse/CAMEL-15403
> Project: Camel
> Issue Type: Test
> Components: camel-xmlsecurity
>Affects Versions: 3.4.2
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.5.0, 3.4.4
>
>
> It's caused by a newline "\n" isn't expected in the test payload for JDK
> 1.8_261.
> I noticed that we've already had code like
> {code}
> if (TestSupport.getJavaMajorVersion() >= 9) {
> includeNewLine = false;
> }
> {code}
> to determine need this newline or not. And I believe the lastest JDK8(Oracle
> JDK8 261) surely take the same logic as JDK9+ now.
> We need also check the 1.8 minor version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15403) camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
[
https://issues.apache.org/jira/browse/CAMEL-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418668#comment-17418668
]
Colm O hEigeartaigh commented on CAMEL-15403:
-
Thanks [~ffang] ! Could you merge to 3.7.x as well?
> camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
> --
>
> Key: CAMEL-15403
> URL: https://issues.apache.org/jira/browse/CAMEL-15403
> Project: Camel
> Issue Type: Test
> Components: camel-xmlsecurity
>Affects Versions: 3.4.2
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.5.0, 3.4.4
>
>
> It's caused by a newline "\n" isn't expected in the test payload for JDK
> 1.8_261.
> I noticed that we've already had code like
> {code}
> if (TestSupport.getJavaMajorVersion() >= 9) {
> includeNewLine = false;
> }
> {code}
> to determine need this newline or not. And I believe the lastest JDK8(Oracle
> JDK8 261) surely take the same logic as JDK9+ now.
> We need also check the 1.8 minor version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15403) camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
[
https://issues.apache.org/jira/browse/CAMEL-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418649#comment-17418649
]
Freeman Yue Fang edited comment on CAMEL-15403 at 9/22/21, 3:12 PM:
Hi [~coheigea],
Thanks for the info!
I can reproduce this on my mac with Azul Zulu Builds of OpenJDK as well,
actually this exists in the latest Zulu 8
{code}
Java version: 1.8.0_302, vendor: Azul Systems, Inc.,
{code}
also.
Seems Azul Zulu JDK8 not that keen to sync up new behaviior from JDK9 later.
I will commit a fix to address this soon.
Fixed on main and camel-3.11.x branches
Best Regards
Freeman
was (Author: ffang):
Hi [~coheigea],
Thanks for the info!
I can reproduce this on my mac with Azul Zulu Builds of OpenJDK as well,
actually this exists in the latest Zulu 8
{code}
Java version: 1.8.0_302, vendor: Azul Systems, Inc.,
{code}
also.
Seems Azul Zulu JDK8 not that keen to sync up new behaviior from JDK9 later.
I will commit a fix to address this soon.
Best Regards
Freeman
> camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
> --
>
> Key: CAMEL-15403
> URL: https://issues.apache.org/jira/browse/CAMEL-15403
> Project: Camel
> Issue Type: Test
> Components: camel-xmlsecurity
>Affects Versions: 3.4.2
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.5.0, 3.4.4
>
>
> It's caused by a newline "\n" isn't expected in the test payload for JDK
> 1.8_261.
> I noticed that we've already had code like
> {code}
> if (TestSupport.getJavaMajorVersion() >= 9) {
> includeNewLine = false;
> }
> {code}
> to determine need this newline or not. And I believe the lastest JDK8(Oracle
> JDK8 261) surely take the same logic as JDK9+ now.
> We need also check the 1.8 minor version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15403) camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
[
https://issues.apache.org/jira/browse/CAMEL-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418649#comment-17418649
]
Freeman Yue Fang commented on CAMEL-15403:
--
Hi [~coheigea],
Thanks for the info!
I can reproduce this on my mac with Azul Zulu Builds of OpenJDK as well,
actually this exists in the latest Zulu 8
{code}
Java version: 1.8.0_302, vendor: Azul Systems, Inc.,
{code}
also.
Seems Azul Zulu JDK8 not that keen to sync up new behaviior from JDK9 later.
I will commit a fix to address this soon.
Best Regards
Freeman
> camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
> --
>
> Key: CAMEL-15403
> URL: https://issues.apache.org/jira/browse/CAMEL-15403
> Project: Camel
> Issue Type: Test
> Components: camel-xmlsecurity
>Affects Versions: 3.4.2
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.5.0, 3.4.4
>
>
> It's caused by a newline "\n" isn't expected in the test payload for JDK
> 1.8_261.
> I noticed that we've already had code like
> {code}
> if (TestSupport.getJavaMajorVersion() >= 9) {
> includeNewLine = false;
> }
> {code}
> to determine need this newline or not. And I believe the lastest JDK8(Oracle
> JDK8 261) surely take the same logic as JDK9+ now.
> We need also check the 1.8 minor version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16993) camel-kafka: update migration guide
[ https://issues.apache.org/jira/browse/CAMEL-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-16993. -- Resolution: Fixed Merged. > camel-kafka: update migration guide > --- > > Key: CAMEL-16993 > URL: https://issues.apache.org/jira/browse/CAMEL-16993 > Project: Camel > Issue Type: Task > Components: camel-kafka, documentation >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.12.0 > > > Consumer stream option was removed. The documentation needs to be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13768) Seek to specific offset and KafkaConsumer access
[
https://issues.apache.org/jira/browse/CAMEL-13768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-13768:
-
Affects Version/s: 3.x
> Seek to specific offset and KafkaConsumer access
> -
>
> Key: CAMEL-13768
> URL: https://issues.apache.org/jira/browse/CAMEL-13768
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 2.24.1, 3.x
>Reporter: michael elbaz
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.12.0
>
>
> 1. Provide a way to rewind kafka offset to specific offset (improve seekTo ?)
> there is no way to do that using camel-kafka component. The main idea is to
> replay older kafka messages without starting from the beginning.
>for example:
> https://blog.sysco.no/integration/kafka-rewind-consumers-offset/
> {code:java}
> boolean flag = true;
> while (true) {
> ConsumerRecords records = consumer.poll(100);
> if(flag) {
> Map query = new HashMap<>();
> query.put(
> new TopicPartition("simple-topic-1", 0),
> Instant.now().minus(10, MINUTES).toEpochMilli());
> // Get offset from timestamp
> Map result =
> consumer.offsetsForTimes(query);
> // Rewind offset to previous position using seekTo
> result.entrySet()
> .stream()
> .forEach(entry -> consumer.seek(entry.getKey(),
> entry.getValue().offset()));
> flag = false;
> }
> for (ConsumerRecord record : records)
> System.out.printf("offset = %d, key = %s, value = %s%n",
> record.offset(), record.key(), record.value());
> }
> {code}
> 2. Provide a way to access kafkaConsumer
>Add camel header with reference to kafkaConsumer to be able to perform
> some Kafka api call.We can use the same way that we do with KafkaManualCommit
> {code:java}
> public void process(Exchange exchange) {
> KafkaManualCommit manual =
> exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> KafkaManualCommit.class);
> manual.commitSync();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-13768) Seek to specific offset and KafkaConsumer access
[
https://issues.apache.org/jira/browse/CAMEL-13768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske resolved CAMEL-13768.
--
Resolution: Fixed
The changes were merged. Closing.
> Seek to specific offset and KafkaConsumer access
> -
>
> Key: CAMEL-13768
> URL: https://issues.apache.org/jira/browse/CAMEL-13768
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 2.24.1
>Reporter: michael elbaz
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.x
>
>
> 1. Provide a way to rewind kafka offset to specific offset (improve seekTo ?)
> there is no way to do that using camel-kafka component. The main idea is to
> replay older kafka messages without starting from the beginning.
>for example:
> https://blog.sysco.no/integration/kafka-rewind-consumers-offset/
> {code:java}
> boolean flag = true;
> while (true) {
> ConsumerRecords records = consumer.poll(100);
> if(flag) {
> Map query = new HashMap<>();
> query.put(
> new TopicPartition("simple-topic-1", 0),
> Instant.now().minus(10, MINUTES).toEpochMilli());
> // Get offset from timestamp
> Map result =
> consumer.offsetsForTimes(query);
> // Rewind offset to previous position using seekTo
> result.entrySet()
> .stream()
> .forEach(entry -> consumer.seek(entry.getKey(),
> entry.getValue().offset()));
> flag = false;
> }
> for (ConsumerRecord record : records)
> System.out.printf("offset = %d, key = %s, value = %s%n",
> record.offset(), record.key(), record.value());
> }
> {code}
> 2. Provide a way to access kafkaConsumer
>Add camel header with reference to kafkaConsumer to be able to perform
> some Kafka api call.We can use the same way that we do with KafkaManualCommit
> {code:java}
> public void process(Exchange exchange) {
> KafkaManualCommit manual =
> exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> KafkaManualCommit.class);
> manual.commitSync();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-13768) Seek to specific offset and KafkaConsumer access
[
https://issues.apache.org/jira/browse/CAMEL-13768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-13768:
-
Fix Version/s: (was: 3.x)
3.12.0
> Seek to specific offset and KafkaConsumer access
> -
>
> Key: CAMEL-13768
> URL: https://issues.apache.org/jira/browse/CAMEL-13768
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 2.24.1
>Reporter: michael elbaz
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.12.0
>
>
> 1. Provide a way to rewind kafka offset to specific offset (improve seekTo ?)
> there is no way to do that using camel-kafka component. The main idea is to
> replay older kafka messages without starting from the beginning.
>for example:
> https://blog.sysco.no/integration/kafka-rewind-consumers-offset/
> {code:java}
> boolean flag = true;
> while (true) {
> ConsumerRecords records = consumer.poll(100);
> if(flag) {
> Map query = new HashMap<>();
> query.put(
> new TopicPartition("simple-topic-1", 0),
> Instant.now().minus(10, MINUTES).toEpochMilli());
> // Get offset from timestamp
> Map result =
> consumer.offsetsForTimes(query);
> // Rewind offset to previous position using seekTo
> result.entrySet()
> .stream()
> .forEach(entry -> consumer.seek(entry.getKey(),
> entry.getValue().offset()));
> flag = false;
> }
> for (ConsumerRecord record : records)
> System.out.printf("offset = %d, key = %s, value = %s%n",
> record.offset(), record.key(), record.value());
> }
> {code}
> 2. Provide a way to access kafkaConsumer
>Add camel header with reference to kafkaConsumer to be able to perform
> some Kafka api call.We can use the same way that we do with KafkaManualCommit
> {code:java}
> public void process(Exchange exchange) {
> KafkaManualCommit manual =
> exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> KafkaManualCommit.class);
> manual.commitSync();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16974) camel-kafka: make the resume strategy configurable
[ https://issues.apache.org/jira/browse/CAMEL-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-16974. -- Resolution: Fixed The changes were merged. Closing. > camel-kafka: make the resume strategy configurable > -- > > Key: CAMEL-16974 > URL: https://issues.apache.org/jira/browse/CAMEL-16974 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.12.0 > > > With the changes from CAMEL-16949, the resume strategy is more easily > configurable. We should expose this SPI, document it and make it configurable > for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15403) camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
[
https://issues.apache.org/jira/browse/CAMEL-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418487#comment-17418487
]
Colm O hEigeartaigh commented on CAMEL-15403:
-
[~ffang] Looks like this fix causes other JDK vendors to fail. Right now the
tests fail for me with:
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (Zulu 8.48.0.53-CA-linux64) (build 1.8.0_265-b11)
> camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
> --
>
> Key: CAMEL-15403
> URL: https://issues.apache.org/jira/browse/CAMEL-15403
> Project: Camel
> Issue Type: Test
> Components: camel-xmlsecurity
>Affects Versions: 3.4.2
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.5.0, 3.4.4
>
>
> It's caused by a newline "\n" isn't expected in the test payload for JDK
> 1.8_261.
> I noticed that we've already had code like
> {code}
> if (TestSupport.getJavaMajorVersion() >= 9) {
> includeNewLine = false;
> }
> {code}
> to determine need this newline or not. And I believe the lastest JDK8(Oracle
> JDK8 261) surely take the same logic as JDK9+ now.
> We need also check the 1.8 minor version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (CAMEL-16974) camel-kafka: make the resume strategy configurable
[ https://issues.apache.org/jira/browse/CAMEL-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16974 started by Otavio Rodolfo Piske. > camel-kafka: make the resume strategy configurable > -- > > Key: CAMEL-16974 > URL: https://issues.apache.org/jira/browse/CAMEL-16974 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.12.0 > > > With the changes from CAMEL-16949, the resume strategy is more easily > configurable. We should expose this SPI, document it and make it configurable > for the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-13768) Seek to specific offset and KafkaConsumer access
[
https://issues.apache.org/jira/browse/CAMEL-13768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-13768 started by Otavio Rodolfo Piske.
> Seek to specific offset and KafkaConsumer access
> -
>
> Key: CAMEL-13768
> URL: https://issues.apache.org/jira/browse/CAMEL-13768
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 2.24.1
>Reporter: michael elbaz
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.x
>
>
> 1. Provide a way to rewind kafka offset to specific offset (improve seekTo ?)
> there is no way to do that using camel-kafka component. The main idea is to
> replay older kafka messages without starting from the beginning.
>for example:
> https://blog.sysco.no/integration/kafka-rewind-consumers-offset/
> {code:java}
> boolean flag = true;
> while (true) {
> ConsumerRecords records = consumer.poll(100);
> if(flag) {
> Map query = new HashMap<>();
> query.put(
> new TopicPartition("simple-topic-1", 0),
> Instant.now().minus(10, MINUTES).toEpochMilli());
> // Get offset from timestamp
> Map result =
> consumer.offsetsForTimes(query);
> // Rewind offset to previous position using seekTo
> result.entrySet()
> .stream()
> .forEach(entry -> consumer.seek(entry.getKey(),
> entry.getValue().offset()));
> flag = false;
> }
> for (ConsumerRecord record : records)
> System.out.printf("offset = %d, key = %s, value = %s%n",
> record.offset(), record.key(), record.value());
> }
> {code}
> 2. Provide a way to access kafkaConsumer
>Add camel header with reference to kafkaConsumer to be able to perform
> some Kafka api call.We can use the same way that we do with KafkaManualCommit
> {code:java}
> public void process(Exchange exchange) {
> KafkaManualCommit manual =
> exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> KafkaManualCommit.class);
> manual.commitSync();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16991) Thread safety with ClientConfigurations object in Huaweicloud components
[ https://issues.apache.org/jira/browse/CAMEL-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16991. - Resolution: Fixed > Thread safety with ClientConfigurations object in Huaweicloud components > > > Key: CAMEL-16991 > URL: https://issues.apache.org/jira/browse/CAMEL-16991 > Project: Camel > Issue Type: Improvement >Reporter: Hokutor >Priority: Major > Fix For: 3.12.0 > > > As pointed in review comment > [https://github.com/apache/camel/pull/6107#discussion_r711522776] , we see > the thread safety issue exists in following components too > - > [camel-huaweicloud-dms|https://github.com/apache/camel/tree/main/components/camel-huawei/camel-huaweicloud-dms] > - > [camel-huaweicloud-functiongraph|https://github.com/apache/camel/tree/main/components/camel-huawei/camel-huaweicloud-functiongraph] > - > [camel-huaweicloud-iam|https://github.com/apache/camel/tree/main/components/camel-huawei/camel-huaweicloud-iam] > - > [camel-huaweicloud-obs|https://github.com/apache/camel/tree/main/components/camel-huawei/camel-huaweicloud-obs] > - > [camel-huaweicloud-smn|https://github.com/apache/camel/tree/main/components/camel-huawei/camel-huaweicloud-smn] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16994) camel-python - Add support for using Python as expression language
Claus Ibsen created CAMEL-16994: --- Summary: camel-python - Add support for using Python as expression language Key: CAMEL-16994 URL: https://issues.apache.org/jira/browse/CAMEL-16994 Project: Camel Issue Type: New Feature Reporter: Claus Ibsen Fix For: 3.x It would be great to get better support for python with Camel. First we can add support for using python as a language with the jython JAR -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16993) camel-kafka: update migration guide
[ https://issues.apache.org/jira/browse/CAMEL-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-16993: - Fix Version/s: 3.12.0 > camel-kafka: update migration guide > --- > > Key: CAMEL-16993 > URL: https://issues.apache.org/jira/browse/CAMEL-16993 > Project: Camel > Issue Type: Task > Components: camel-kafka, documentation >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.12.0 > > > Consumer stream option was removed. The documentation needs to be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16993) camel-kafka: update migration guide
Otavio Rodolfo Piske created CAMEL-16993: Summary: camel-kafka: update migration guide Key: CAMEL-16993 URL: https://issues.apache.org/jira/browse/CAMEL-16993 Project: Camel Issue Type: Task Components: camel-kafka, documentation Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Consumer stream option was removed. The documentation needs to be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
