[jira] [Resolved] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20724.
-
Fix Version/s: 4.4.3
4.6.0
(was: 4.x)
Assignee: Denis Istomin
Resolution: Fixed
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Assignee: Denis Istomin
>Priority: Minor
> Fix For: 4.4.3, 4.6.0
>
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/;);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842524#comment-17842524 ] Dylan Piergies commented on CAMEL-18276: Personally, I would be inclined to prioritise further improvements to unit testing for the component over this. We don't have any use case for sessions within my org at present, so I'm in no rush to implement it. Perhaps it could happen if I find myself at a loose end one weekend. ;) If another developer can find time to implement this feature, please go ahead. I'll update this ticket if I start working on it. > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.6.0 > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20680) camel-kafka: reduce KafkaBreakOnFirstErrorSeekIssueIT test duration
[
https://issues.apache.org/jira/browse/CAMEL-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842487#comment-17842487
]
JV Singh commented on CAMEL-20680:
--
Turns out, the timeout failures with these tests are quite random.
In my case, this particular test succeeded
{code:java}
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.03 s
-- in
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorReplayOldMessagesIT
[INFO] Running
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorSeekIssueIT
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 457.6 s
-- in
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorSeekIssueIT{code}
but a few other random ones failed with a similar error:
{code:java}
[INFO] Running
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorWithBatchUsingAsyncCommitManagerIT
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 38.90 s
<<< FAILURE! -- in
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorWithBatchUsingAsyncCommitManagerIT
[ERROR]
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorWithBatchUsingAsyncCommitManagerIT.kafkaBreakOnFirstErrorBasicCapability
-- Time elapsed: 5.010 s <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression
in
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorWithBatchUsingAsyncCommitManagerIT
was not fulfilled within 3 seconds.{code}
I think it is quite likely for the elapsed times of these tests to vary based
on CI / build server spec, network speed etc.
> camel-kafka: reduce KafkaBreakOnFirstErrorSeekIssueIT test duration
> ---
>
> Key: CAMEL-20680
> URL: https://issues.apache.org/jira/browse/CAMEL-20680
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
>Affects Versions: 4.4.1, 4.5.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> The test KafkaBreakOnFirstErrorSeekIssueIT takes a very long time to run.
> This consumes unnecessary resources from ASF CI. We should investigate how to
> improve it to it runs quickly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842482#comment-17842482
]
Denis Istomin commented on CAMEL-20724:
---
Made a PR with unit-test and a fix itself
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Minor
> Fix For: 4.x
>
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/;);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[
https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842474#comment-17842474
]
JV Singh commented on CAMEL-20722:
--
Many (but not all) KafkaBreakOnFirst*IT integration tests fail with this or a
similar error: ... _was not fulfilled within 3 seconds._
{code:java}
[ERROR]
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorWithBatchUsingSyncCommitManagerIT.kafkaBreakOnFirstErrorBasicCapability
-- Time elapsed: 5.782 s <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression
in
org.apache.camel.component.kafka.integration.KafkaBreakOnFirstErrorWithBatchUsingSyncCommitManagerIT
was not fulfilled within 3 seconds.{code}
> camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
> ---
>
> Key: CAMEL-20722
> URL: https://issues.apache.org/jira/browse/CAMEL-20722
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
>Affects Versions: 4.4.1, 4.5.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the
> CI. They fail often, sometimes in multiple archs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20728) camel-aws2s3 Stream Producer should support multipart loading
Benjamin BONNET created CAMEL-20728: --- Summary: camel-aws2s3 Stream Producer should support multipart loading Key: CAMEL-20728 URL: https://issues.apache.org/jira/browse/CAMEL-20728 Project: Camel Issue Type: New Feature Components: camel-aws Affects Versions: 4.5.0 Reporter: Benjamin BONNET AWS2S3 Producer comes in two flavours: AWS2S3Producer and AWS2S3StreamUploadProducer. * AWS2S3Producer supports S3 multipart upload: exchange data will be chunked into parts, parts will be sent separately to S3 and will be aggregated into one file. * AWS2S3StreamUploadProducer supports message streaming: incoming messages are aggregated into a buffer that will be sent as one file to S3, as soon as some condition is true (number of messages / size /timeout). Unfortunately, AWS2S3StreamUploadProducer, although it is able to break a huge flow of messages into parts (which is great for some use cases), is not able to manage S3 multipart upload. So if you need to aggregate lots of messages into one big file on S3 side, that means the producer will have to send that message batch in one request (actually, a single part multipart request if you look at implementation). If the volume is huge, that will blow up jvm heap. So we propose to add multi-part support to AWS2S3StreamUploadProducer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-15279) Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header
[ https://issues.apache.org/jira/browse/CAMEL-15279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15279. - Resolution: Fixed Thanks Jono for your work on camel-as2 > Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header > > > Key: CAMEL-15279 > URL: https://issues.apache.org/jira/browse/CAMEL-15279 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Affects Versions: 3.4.0 >Reporter: Benson Chan >Assignee: Jono Morris >Priority: Minor > Labels: help-wanted > Fix For: 4.6.0 > > Attachments: image-2020-07-08-12-36-50-232.png > > > # add an option to allow as2 producer to set the "Receipt-Delivery-Option" > header > ## both in routing and also when using AS2ClientManager.send methods > # when receiving a MDN message, the HttpMessageUtils.extractEdiPayload will > throw an exception saying invalid content type 'multipart/report' > !image-2020-07-08-12-37-58-469.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-15279) Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header
[ https://issues.apache.org/jira/browse/CAMEL-15279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15279: Fix Version/s: 4.6.0 > Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header > > > Key: CAMEL-15279 > URL: https://issues.apache.org/jira/browse/CAMEL-15279 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Affects Versions: 3.4.0 >Reporter: Benson Chan >Assignee: Jono Morris >Priority: Minor > Labels: help-wanted > Fix For: 4.6.0 > > Attachments: image-2020-07-08-12-36-50-232.png > > > # add an option to allow as2 producer to set the "Receipt-Delivery-Option" > header > ## both in routing and also when using AS2ClientManager.send methods > # when receiving a MDN message, the HttpMessageUtils.extractEdiPayload will > throw an exception saying invalid content type 'multipart/report' > !image-2020-07-08-12-37-58-469.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20727) camel-azure - Data lake upload should not read content into memory
[ https://issues.apache.org/jira/browse/CAMEL-20727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20727: Fix Version/s: 4.4.3 > camel-azure - Data lake upload should not read content into memory > -- > > Key: CAMEL-20727 > URL: https://issues.apache.org/jira/browse/CAMEL-20727 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.3, 4.6.0 > > > The upload operation does not need the file length, but can use the input > stream as-is. Its only the append that needs to know the offset to append > from and therefore the length. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842362#comment-17842362 ] Andrea Cosentino commented on CAMEL-18276: -- [~dylan.piergies] if you time and want to try to implement that, go for it. > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.6.0 > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842361#comment-17842361 ] Dylan Piergies commented on CAMEL-18276: There's a general overview of the Service Bus feature with links to the documentation on how to use it with the Java API here: https://learn.microsoft.com/en-us/azure/service-bus-messaging/message-sessions. > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.6.0 > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20652) camel-rest - Contract First - Make it possible to build response from example data
[ https://issues.apache.org/jira/browse/CAMEL-20652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20652: --- Assignee: Claus Ibsen > camel-rest - Contract First - Make it possible to build response from example > data > -- > > Key: CAMEL-20652 > URL: https://issues.apache.org/jira/browse/CAMEL-20652 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > If you have "mock" as missing operation then we attempt to load responses > from file system. But if none is found, we should build an empty response > based on the contract and verb. > In the contract we can find "example" for various fields such as for Pet > where there are examples for name, tag and whatnot. We can grab them from the > contract and automatic put on the response object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
