[jira] [Resolved] (CAMEL-17754) camel-core - precondition to hard exclude route configurations
[ https://issues.apache.org/jira/browse/CAMEL-17754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17754. - Fix Version/s: 3.16.0 (was: 3.17.0) Resolution: Fixed Thanks that was really fast and great work > camel-core - precondition to hard exclude route configurations > -- > > Key: CAMEL-17754 > URL: https://issues.apache.org/jira/browse/CAMEL-17754 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Nicolas Filotto >Priority: Major > Fix For: 3.16.0 > > > The same as CAMEL-17555 but for route configurations > (RouteConfigurationDefinition). > With this you could potentially have shared/nested JARs with a common set of > route configurations that have pre-conditions so they will only be included > if the precondition is true. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17755) camel-core - DoSwitch can be Choice with precondition set
[ https://issues.apache.org/jira/browse/CAMEL-17755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502737#comment-17502737 ] Claus Ibsen commented on CAMEL-17755: - [~essobedo] this ticket you are welcome to look at too > camel-core - DoSwitch can be Choice with precondition set > - > > Key: CAMEL-17755 > URL: https://issues.apache.org/jira/browse/CAMEL-17755 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.17.0 > > > With CAMEL-17555 we use the term "precondition" to filter whether the > route/EIP should be included or not (eager). > To standardize on precondition then we can remove DoSwitch and use Choice > instead and add precondition to choice. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17575) camel-examples - Update main example to use base package scanning
[ https://issues.apache.org/jira/browse/CAMEL-17575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502736#comment-17502736 ] Claus Ibsen commented on CAMEL-17575: - If the tests is also failing before you do changes then its okay to go ahead with your modifications. And when you are done you are welcome to comment here, or create a new JIRA with details which examples you have seen test failures with. > camel-examples - Update main example to use base package scanning > - > > Key: CAMEL-17575 > URL: https://issues.apache.org/jira/browse/CAMEL-17575 > Project: Camel > Issue Type: Improvement > Components: examples >Affects Versions: 3.16.0 >Reporter: Claus Ibsen >Assignee: Marouane Trabelsi >Priority: Major > Fix For: 3.16.0 > > > We should update this example to use the new base package scanning, where we > auto detect the route builders, type converters and configuration classes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17575) camel-examples - Update main example to use base package scanning
[ https://issues.apache.org/jira/browse/CAMEL-17575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502577#comment-17502577 ] Marouane Trabelsi commented on CAMEL-17575: --- [~davsclaus] thanks for assigning the role to self-assign tickets. Indeed, I have advanced on this and you should expect a PR by end of the week. Unfortunately I have been slowed down by random test-failures that are totally unrelated to changes (as an example, the _camel-example-main-endpointdsl-aws2-s3-kafka_ modules tests are failing due to producer / consumer synchronization). > camel-examples - Update main example to use base package scanning > - > > Key: CAMEL-17575 > URL: https://issues.apache.org/jira/browse/CAMEL-17575 > Project: Camel > Issue Type: Improvement > Components: examples >Affects Versions: 3.16.0 >Reporter: Claus Ibsen >Assignee: Marouane Trabelsi >Priority: Major > Fix For: 3.16.0 > > > We should update this example to use the new base package scanning, where we > auto detect the route builders, type converters and configuration classes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17754) camel-core - precondition to hard exclude route configurations
[ https://issues.apache.org/jira/browse/CAMEL-17754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502490#comment-17502490 ] Nicolas Filotto commented on CAMEL-17754: - The corresponding PR https://github.com/apache/camel/pull/7142 > camel-core - precondition to hard exclude route configurations > -- > > Key: CAMEL-17754 > URL: https://issues.apache.org/jira/browse/CAMEL-17754 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Nicolas Filotto >Priority: Major > Fix For: 3.17.0 > > > The same as CAMEL-17555 but for route configurations > (RouteConfigurationDefinition). > With this you could potentially have shared/nested JARs with a common set of > route configurations that have pre-conditions so they will only be included > if the precondition is true. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17368) camel-google-functions - Support GKE's workload identity
[ https://issues.apache.org/jira/browse/CAMEL-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17368: - Fix Version/s: 3.17.0 (was: 3.16.0) > camel-google-functions - Support GKE's workload identity > > > Key: CAMEL-17368 > URL: https://issues.apache.org/jira/browse/CAMEL-17368 > Project: Camel > Issue Type: Improvement > Components: camel-google >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.17.0 > > > Like CAMEL-16883 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17369) Camel-google-storage - Support GKE's workload identity
[ https://issues.apache.org/jira/browse/CAMEL-17369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17369: - Fix Version/s: 3.17.0 (was: 3.16.0) > Camel-google-storage - Support GKE's workload identity > -- > > Key: CAMEL-17369 > URL: https://issues.apache.org/jira/browse/CAMEL-17369 > Project: Camel > Issue Type: Improvement > Components: camel-google >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.17.0 > > > Like CAMEL-16883 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17644) Support ability to load properties from Vault/Secrets cloud services
[
https://issues.apache.org/jira/browse/CAMEL-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-17644:
-
Fix Version/s: 3.17.0
(was: 3.16.0)
> Support ability to load properties from Vault/Secrets cloud services
> -
>
> Key: CAMEL-17644
> URL: https://issues.apache.org/jira/browse/CAMEL-17644
> Project: Camel
> Issue Type: Improvement
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.17.0
>
>
> This is slightly different from CAMEL-11030
> With this I'd like to able to do stuff like:
> {code:bash}
> {{aws:token}}
> {code}
> and get the secret value from the secret token on AWS Secrets Manager, this
> could be done for also GCP and Azure.
> For the beginning we are not considering secret rotations, but we'll arrive
> at that during development cycle.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17339) Avoid List as configuration parameter types in Endpoint configurations
[ https://issues.apache.org/jira/browse/CAMEL-17339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17339: - Fix Version/s: 3.17.0 (was: 3.16.0) > Avoid List as configuration parameter types in Endpoint configurations > -- > > Key: CAMEL-17339 > URL: https://issues.apache.org/jira/browse/CAMEL-17339 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.17.0 > > > Let's try to avoid this, it's better to have a comma separated string for > Kamelets purpose, but also because it is much more cleaner in terms of > reifiers. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17593) camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any info
[
https://issues.apache.org/jira/browse/CAMEL-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502457#comment-17502457
]
Andrea Cosentino commented on CAMEL-17593:
--
Feel free to work on this one, I'd like to have it in 3.16.0
> camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any
> info
> ---
>
> Key: CAMEL-17593
> URL: https://issues.apache.org/jira/browse/CAMEL-17593
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
>Affects Versions: 3.13.0
>Reporter: Mikołaj Matejko
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.16.0
>
> Attachments: image-2022-02-03-10-36-40-773.png,
> image-2022-02-03-10-39-12-547.png
>
>
> When you try to send a message using AWS SDK and provide more then 10
> messageAttributes then you will get a clean error what happened, e.g.:
> !image-2022-02-03-10-36-40-773.png!
> When using Camel the behavior is different - Camel is going to skip all
> messageAttributes after the first 10 ones. It won't throw anything nor log
> anything. So it leads to losing information without even knowing it.
> Problematic place:
> {*}Sqs2Producer#translateAttributes{*}!image-2022-02-03-10-39-12-547.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17593) camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any info
[
https://issues.apache.org/jira/browse/CAMEL-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502455#comment-17502455
]
Andrea Cosentino commented on CAMEL-17593:
--
Yes [~davsclaus], it's an hard limit
> camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any
> info
> ---
>
> Key: CAMEL-17593
> URL: https://issues.apache.org/jira/browse/CAMEL-17593
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
>Affects Versions: 3.13.0
>Reporter: Mikołaj Matejko
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.16.0
>
> Attachments: image-2022-02-03-10-36-40-773.png,
> image-2022-02-03-10-39-12-547.png
>
>
> When you try to send a message using AWS SDK and provide more then 10
> messageAttributes then you will get a clean error what happened, e.g.:
> !image-2022-02-03-10-36-40-773.png!
> When using Camel the behavior is different - Camel is going to skip all
> messageAttributes after the first 10 ones. It won't throw anything nor log
> anything. So it leads to losing information without even knowing it.
> Problematic place:
> {*}Sqs2Producer#translateAttributes{*}!image-2022-02-03-10-39-12-547.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17758) add tests in camel-cassandraql-starter
Freeman Yue Fang created CAMEL-17758: Summary: add tests in camel-cassandraql-starter Key: CAMEL-17758 URL: https://issues.apache.org/jira/browse/CAMEL-17758 Project: Camel Issue Type: Test Components: camel-cassandraql, camel-spring-boot-starters, tests Reporter: Freeman Yue Fang Assignee: Freeman Yue Fang Fix For: 3.16.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17757) camel-hbase - Upgrade to 2.4.10
[ https://issues.apache.org/jira/browse/CAMEL-17757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17757. - Resolution: Fixed > camel-hbase - Upgrade to 2.4.10 > --- > > Key: CAMEL-17757 > URL: https://issues.apache.org/jira/browse/CAMEL-17757 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-hbase >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17757) camel-hbase - Upgrade to 2.4.10
Claus Ibsen created CAMEL-17757: --- Summary: camel-hbase - Upgrade to 2.4.10 Key: CAMEL-17757 URL: https://issues.apache.org/jira/browse/CAMEL-17757 Project: Camel Issue Type: Dependency upgrade Components: camel-hbase Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.16.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17756) camel-tika - Upgrade to tika 2.x
[ https://issues.apache.org/jira/browse/CAMEL-17756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17756. - Resolution: Fixed > camel-tika - Upgrade to tika 2.x > > > Key: CAMEL-17756 > URL: https://issues.apache.org/jira/browse/CAMEL-17756 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-tika >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17756) camel-tika - Upgrade to tika 2.x
Claus Ibsen created CAMEL-17756: --- Summary: camel-tika - Upgrade to tika 2.x Key: CAMEL-17756 URL: https://issues.apache.org/jira/browse/CAMEL-17756 Project: Camel Issue Type: Dependency upgrade Components: camel-tika Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.16.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17754) camel-core - precondition to hard exclude route configurations
[ https://issues.apache.org/jira/browse/CAMEL-17754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Filotto reassigned CAMEL-17754: --- Assignee: Nicolas Filotto > camel-core - precondition to hard exclude route configurations > -- > > Key: CAMEL-17754 > URL: https://issues.apache.org/jira/browse/CAMEL-17754 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Nicolas Filotto >Priority: Major > Fix For: 3.17.0 > > > The same as CAMEL-17555 but for route configurations > (RouteConfigurationDefinition). > With this you could potentially have shared/nested JARs with a common set of > route configurations that have pre-conditions so they will only be included > if the precondition is true. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17571) camel-main - Allow to bean inject beans from @Inject and other similar annotations
[ https://issues.apache.org/jira/browse/CAMEL-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17571: Fix Version/s: 3.17.0 (was: 3.16.0) > camel-main - Allow to bean inject beans from @Inject and other similar > annotations > -- > > Key: CAMEL-17571 > URL: https://issues.apache.org/jira/browse/CAMEL-17571 > Project: Camel > Issue Type: New Feature > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.17.0 > > > When running Camel standalone (not spring boot / quarkus / camel-k) but also > with jbang, then it can be good if we can also allow to discover bean > injections via @Inject and similar annotations. You can use Camels own > @BeanInject but you may build a prototype and run standalone, and then later > want to move this over to SB / Camel-K or Quarkus and then its easier if some > of their annotations is already supported. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17745) camel-spring-boot - AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17745. --- Resolution: Fixed > camel-spring-boot - AutoConfigurations models aren't updated > > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.16.0 > > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17745) camel-spring-boot - AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-17745: - Assignee: John Poth > camel-spring-boot - AutoConfigurations models aren't updated > > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.16.0 > > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17575) camel-examples - Update main example to use base package scanning
[ https://issues.apache.org/jira/browse/CAMEL-17575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502225#comment-17502225 ] Claus Ibsen commented on CAMEL-17575: - Marourana do you have time to work on the remainder examples? > camel-examples - Update main example to use base package scanning > - > > Key: CAMEL-17575 > URL: https://issues.apache.org/jira/browse/CAMEL-17575 > Project: Camel > Issue Type: Improvement > Components: examples >Affects Versions: 3.16.0 >Reporter: Claus Ibsen >Assignee: Marouane Trabelsi >Priority: Major > Fix For: 3.16.0 > > > We should update this example to use the new base package scanning, where we > auto detect the route builders, type converters and configuration classes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17755) camel-core - DoSwitch can be Choice with precondition set
Claus Ibsen created CAMEL-17755: --- Summary: camel-core - DoSwitch can be Choice with precondition set Key: CAMEL-17755 URL: https://issues.apache.org/jira/browse/CAMEL-17755 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 3.17.0 With CAMEL-17555 we use the term "precondition" to filter whether the route/EIP should be included or not (eager). To standardize on precondition then we can remove DoSwitch and use Choice instead and add precondition to choice. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17754) camel-core - precondition to hard exclude route configurations
[ https://issues.apache.org/jira/browse/CAMEL-17754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17754: Fix Version/s: 3.17.0 > camel-core - precondition to hard exclude route configurations > -- > > Key: CAMEL-17754 > URL: https://issues.apache.org/jira/browse/CAMEL-17754 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.17.0 > > > The same as CAMEL-17555 but for route configurations > (RouteConfigurationDefinition). > With this you could potentially have shared/nested JARs with a common set of > route configurations that have pre-conditions so they will only be included > if the precondition is true. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17754) camel-core - precondition to hard exclude route configurations
[ https://issues.apache.org/jira/browse/CAMEL-17754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1750#comment-1750 ] Claus Ibsen commented on CAMEL-17754: - [~essobedo] here is another ticket that is related to what you did in CAMEL-17555. This one may also be tricky as route configurations are in the core and for all DSLs > camel-core - precondition to hard exclude route configurations > -- > > Key: CAMEL-17754 > URL: https://issues.apache.org/jira/browse/CAMEL-17754 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > > The same as CAMEL-17555 but for route configurations > (RouteConfigurationDefinition). > With this you could potentially have shared/nested JARs with a common set of > route configurations that have pre-conditions so they will only be included > if the precondition is true. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17754) camel-core - precondition to hard exclude route configurations
Claus Ibsen created CAMEL-17754: --- Summary: camel-core - precondition to hard exclude route configurations Key: CAMEL-17754 URL: https://issues.apache.org/jira/browse/CAMEL-17754 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Claus Ibsen The same as CAMEL-17555 but for route configurations (RouteConfigurationDefinition). With this you could potentially have shared/nested JARs with a common set of route configurations that have pre-conditions so they will only be included if the precondition is true. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17593) camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any info
[
https://issues.apache.org/jira/browse/CAMEL-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502221#comment-17502221
]
Mikołaj Matejko commented on CAMEL-17593:
-
[~davsclaus] 10 is a hardlimit for now, here is a description:
[https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-metadata.html]
"Each message can have up to 10 attributes"
> camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any
> info
> ---
>
> Key: CAMEL-17593
> URL: https://issues.apache.org/jira/browse/CAMEL-17593
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
>Affects Versions: 3.13.0
>Reporter: Mikołaj Matejko
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.16.0
>
> Attachments: image-2022-02-03-10-36-40-773.png,
> image-2022-02-03-10-39-12-547.png
>
>
> When you try to send a message using AWS SDK and provide more then 10
> messageAttributes then you will get a clean error what happened, e.g.:
> !image-2022-02-03-10-36-40-773.png!
> When using Camel the behavior is different - Camel is going to skip all
> messageAttributes after the first 10 ones. It won't throw anything nor log
> anything. So it leads to losing information without even knowing it.
> Problematic place:
> {*}Sqs2Producer#translateAttributes{*}!image-2022-02-03-10-39-12-547.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17593) camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any info
[
https://issues.apache.org/jira/browse/CAMEL-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502220#comment-17502220
]
Claus Ibsen commented on CAMEL-17593:
-
Andrea, are you working on this? If not then I can take a look.
Is the 10 hardlimit on AWS, and would it potentially be changed? As we could
make the 10 a configuration on the component level, so it can be adjusted in
the future.
And can you see this 10 hardlimit somewhere on their documentation (anyone has
a hyperlink)?
> camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any
> info
> ---
>
> Key: CAMEL-17593
> URL: https://issues.apache.org/jira/browse/CAMEL-17593
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
>Affects Versions: 3.13.0
>Reporter: Mikołaj Matejko
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.16.0
>
> Attachments: image-2022-02-03-10-36-40-773.png,
> image-2022-02-03-10-39-12-547.png
>
>
> When you try to send a message using AWS SDK and provide more then 10
> messageAttributes then you will get a clean error what happened, e.g.:
> !image-2022-02-03-10-36-40-773.png!
> When using Camel the behavior is different - Camel is going to skip all
> messageAttributes after the first 10 ones. It won't throw anything nor log
> anything. So it leads to losing information without even knowing it.
> Problematic place:
> {*}Sqs2Producer#translateAttributes{*}!image-2022-02-03-10-39-12-547.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17648) Optimizing File component performance when filtering file names.
[ https://issues.apache.org/jira/browse/CAMEL-17648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502206#comment-17502206 ] Ja commented on CAMEL-17648: I created a small example patch for FileConsumer with a simple optimization that dramatically speeds up polling directory contents with exclude and include patterns. The only drawback I can see is problem with "recursive=true" witch requires editing existing include/exclude patterns to include required subdirectories. [^CAMEL-17648.patch] > Optimizing File component performance when filtering file names. > > > Key: CAMEL-17648 > URL: https://issues.apache.org/jira/browse/CAMEL-17648 > Project: Camel > Issue Type: Improvement > Components: camel-file >Reporter: Ja >Priority: Minor > Fix For: 3.x > > Attachments: CAMEL-17648.patch > > > Currently FileConsumer matches file names after creating GenericFile object > for each file witch can be time consuming especially in shared network > directories. > This could be optimized by matching on name based query parameters (fileName, > include, exclude, antExclude, antInclude, includeExt, excludeExt) before > creating GenericFile objects. > If the file name does not match creating GenericFile objects would not be > necessary. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17648) Optimizing File component performance when filtering file names.
[ https://issues.apache.org/jira/browse/CAMEL-17648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ja updated CAMEL-17648: --- Attachment: CAMEL-17648.patch > Optimizing File component performance when filtering file names. > > > Key: CAMEL-17648 > URL: https://issues.apache.org/jira/browse/CAMEL-17648 > Project: Camel > Issue Type: Improvement > Components: camel-file >Reporter: Ja >Priority: Minor > Fix For: 3.x > > Attachments: CAMEL-17648.patch > > > Currently FileConsumer matches file names after creating GenericFile object > for each file witch can be time consuming especially in shared network > directories. > This could be optimized by matching on name based query parameters (fileName, > include, exclude, antExclude, antInclude, includeExt, excludeExt) before > creating GenericFile objects. > If the file name does not match creating GenericFile objects would not be > necessary. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17602) camel-aws2-sqs - Camel converts Number.Boolean messageAttribute into string "1" or "0" instead of Boolean
[ https://issues.apache.org/jira/browse/CAMEL-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17602. - Resolution: Fixed > camel-aws2-sqs - Camel converts Number.Boolean messageAttribute into string > "1" or "0" instead of Boolean > - > > Key: CAMEL-17602 > URL: https://issues.apache.org/jira/browse/CAMEL-17602 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.13.0, 3.14.1 >Reporter: Mikołaj Matejko >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.14.3, 3.16.0 > > Attachments: image-2022-02-04-12-07-27-282.png, > image-2022-02-04-12-10-04-707.png > > > Sqs2Producer turns Boolean header into messageAttribute with > dataType=Number.Boolean, stringValue="0" or stringValue="1" > !image-2022-02-04-12-07-27-282.png|width=505,height=103! > However Sqs2Consumer seems to incorrectly convert messageAttribute into > header while constructing Exchange - instead of turning the "1" -> true, "0" > -> false it leaves the values as "1", "0" strings. Shouldn't it convert it > directly to Boolean (true, false)? > !image-2022-02-04-12-10-04-707.png|width=601,height=148! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17743) camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17743. --- Resolution: Fixed > camel-spring-boot - Schema generation fails for > Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Task > Components: camel-core >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.16.0 > > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17753) FailOverLoadBalancer does not Load Balance when sticky flag is set to true.
Vincenzo Galluccio created CAMEL-17753: -- Summary: FailOverLoadBalancer does not Load Balance when sticky flag is set to true. Key: CAMEL-17753 URL: https://issues.apache.org/jira/browse/CAMEL-17753 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 3.14.1 Reporter: Vincenzo Galluccio -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17602) camel-aws2-sqs - Camel converts Number.Boolean messageAttribute into string "1" or "0" instead of Boolean
[ https://issues.apache.org/jira/browse/CAMEL-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-17602: --- Assignee: Claus Ibsen > camel-aws2-sqs - Camel converts Number.Boolean messageAttribute into string > "1" or "0" instead of Boolean > - > > Key: CAMEL-17602 > URL: https://issues.apache.org/jira/browse/CAMEL-17602 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.13.0, 3.14.1 >Reporter: Mikołaj Matejko >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.14.3, 3.16.0 > > Attachments: image-2022-02-04-12-07-27-282.png, > image-2022-02-04-12-10-04-707.png > > > Sqs2Producer turns Boolean header into messageAttribute with > dataType=Number.Boolean, stringValue="0" or stringValue="1" > !image-2022-02-04-12-07-27-282.png|width=505,height=103! > However Sqs2Consumer seems to incorrectly convert messageAttribute into > header while constructing Exchange - instead of turning the "1" -> true, "0" > -> false it leaves the values as "1", "0" strings. Shouldn't it convert it > directly to Boolean (true, false)? > !image-2022-02-04-12-10-04-707.png|width=601,height=148! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17613) camel-sql - Race condition in AggregateProcessor with Jdbc Repository
[ https://issues.apache.org/jira/browse/CAMEL-17613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17613: Fix Version/s: 3.17.0 (was: 3.16.0) > camel-sql - Race condition in AggregateProcessor with Jdbc Repository > - > > Key: CAMEL-17613 > URL: https://issues.apache.org/jira/browse/CAMEL-17613 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-sql >Affects Versions: 3.11.2 >Reporter: Benjamin BONNET >Priority: Major > Fix For: 3.17.0 > > Attachments: CAMEL-17613-log.txt, Spring_jdbc_transactions.log > > > Hi, > using aggregate with a JdbcAggregationRepository, we are encountering a race > condition that may leave a completed exchange in completed table even after > that completed exchange has been sent. Unfortunately, that leads to > duplicates since recovery task will eventually try and recover it. > Normally, when the exchange completes, it is deleted from repo exchange table > and inserted into repo completed exchange table. Then exchange is sent and > deleted from repo completed exchange table. > But, due to the fact those two actions are run by different threads (and in > different transactions) that order may vary. > > Here is a normal sequence : > AggregateProcessor.doProcess > doAggregation > doAggregationComplete > onCompletion > JdbcAggregationRepository.remove : => INSERT ... INTO _completed > onSubmitCompletion > AggregateOnCompletion.onComplete (via executorService) > JdbcAggregationRepository.confirm : => DELETE FROM _completed > With the use of executorService, confirm is run by another thread and may > commit before remove commits. Eventually, when that occurs, one can check > that DELETE statement returns 0 (number of deleted rows) instead of 1. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17718) REST DSL RestSecuritiesDefinition cleanup
[
https://issues.apache.org/jira/browse/CAMEL-17718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17718.
-
Fix Version/s: 3.16.0
Resolution: Fixed
> REST DSL RestSecuritiesDefinition cleanup
> -
>
> Key: CAMEL-17718
> URL: https://issues.apache.org/jira/browse/CAMEL-17718
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.16.0
>
>
> 1. RestDefinition has property securit{*}y{*}Definition{*}s{*} of type
> RestSecurit{*}ies{*}Definitio{+}n{+}
> 2. RestSecurit{*}ies{*}Definitio{+}n{+} has metadata in
> securit{*}y{*}Definition{*}s{*}.json
> 3. RestSecurit{*}ies{*}Definitio{+}n{+} has only one property
> securit{*}y{*}Definition{*}s{*} of type List >{+}
> Issues:
> # There is no metadata for RestSecurit{*}y{*}Definitio{+}n{+}
> # Could we remove intermediate RestSecurit{*}ies{*}Definitio{+}n{+} if it
> has only one property
> # Could we sync plural/singular filenames and Definitions
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17748) camel-any23 - Upgrade to 2.7
[ https://issues.apache.org/jira/browse/CAMEL-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17748: Fix Version/s: (was: 3.14.3) > camel-any23 - Upgrade to 2.7 > > > Key: CAMEL-17748 > URL: https://issues.apache.org/jira/browse/CAMEL-17748 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
