[jira] [Resolved] (CAMEL-12806) Camel-Slack: Add a check on the messages list while consuming
[ https://issues.apache.org/jira/browse/CAMEL-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12806. -- Resolution: Fixed > Camel-Slack: Add a check on the messages list while consuming > - > > Key: CAMEL-12806 > URL: https://issues.apache.org/jira/browse/CAMEL-12806 > Project: Camel > Issue Type: Improvement > Components: camel-slack >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.23.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12806) Camel-Slack: Add a check on the messages list while consuming
Andrea Cosentino created CAMEL-12806: Summary: Camel-Slack: Add a check on the messages list while consuming Key: CAMEL-12806 URL: https://issues.apache.org/jira/browse/CAMEL-12806 Project: Camel Issue Type: Improvement Components: camel-slack Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.23.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12807) Avoid to use endpoint attribute when MqttConnectOptions is declared once
Fabrizio Spataro created CAMEL-12807: Summary: Avoid to use endpoint attribute when MqttConnectOptions is declared once Key: CAMEL-12807 URL: https://issues.apache.org/jira/browse/CAMEL-12807 Project: Camel Issue Type: Bug Components: camel-paho Affects Versions: 2.22.2 Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Hello, In my system i have a default MqttConnectOptions declared into spring context and some other camel consumers/producers connected to others mqtt servers. So today i cannot use endpoint parameters without declare an another mqttConnectOptions class because the endpoint code suppose that use ALWAYS MqttConnectOptions (if it is declared once) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12807) Avoid to use endpoint attribute when MqttConnectOptions is declared once
[ https://issues.apache.org/jira/browse/CAMEL-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613511#comment-16613511 ] ASF GitHub Bot commented on CAMEL-12807: GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/2521 CAMEL-12807 Avoid to use endpoint attribute when MqttConnectOptions i… …s declared once Hello, this is my propose patch to camel-paho endpoint Note is backward compatible! You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-12807 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2521.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2521 commit a962be45274d37d7610c6dd3bdfb90365b4a0d42 Author: Fabrizio Spataro Date: 2018-09-13T13:37:45Z CAMEL-12807 Avoid to use endpoint attribute when MqttConnectOptions is declared once > Avoid to use endpoint attribute when MqttConnectOptions is declared once > > > Key: CAMEL-12807 > URL: https://issues.apache.org/jira/browse/CAMEL-12807 > Project: Camel > Issue Type: Bug > Components: camel-paho >Affects Versions: 2.22.2 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Major > > Hello, > In my system i have a default MqttConnectOptions declared into spring context > and some other camel consumers/producers connected to others mqtt servers. > So today i cannot use endpoint parameters without declare an another > mqttConnectOptions class because the endpoint code suppose that use ALWAYS > MqttConnectOptions (if it is declared once) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12807) Avoid to use endpoint attribute when MqttConnectOptions is declared once
[ https://issues.apache.org/jira/browse/CAMEL-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613510#comment-16613510 ] ASF GitHub Bot commented on CAMEL-12807: Fabryprog opened a new pull request #2521: CAMEL-12807 Avoid to use endpoint attribute when MqttConnectOptions i… URL: https://github.com/apache/camel/pull/2521 …s declared once Hello, this is my propose patch to camel-paho endpoint Note is backward compatible! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Avoid to use endpoint attribute when MqttConnectOptions is declared once > > > Key: CAMEL-12807 > URL: https://issues.apache.org/jira/browse/CAMEL-12807 > Project: Camel > Issue Type: Bug > Components: camel-paho >Affects Versions: 2.22.2 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Major > > Hello, > In my system i have a default MqttConnectOptions declared into spring context > and some other camel consumers/producers connected to others mqtt servers. > So today i cannot use endpoint parameters without declare an another > mqttConnectOptions class because the endpoint code suppose that use ALWAYS > MqttConnectOptions (if it is declared once) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12808) Add support for PK Chunking in Salesforce Bulk API
Dhiraj Bokde created CAMEL-12808: Summary: Add support for PK Chunking in Salesforce Bulk API Key: CAMEL-12808 URL: https://issues.apache.org/jira/browse/CAMEL-12808 Project: Camel Issue Type: New Feature Components: camel-salesforce Affects Versions: 2.22.1 Reporter: Dhiraj Bokde Salesforce supports chunking primary keys in queries for tables with a large number of records as described at [1]. This reduces the number of records returned in Batch results, by adding more batches to jobs. This helps reduce the amount of data that has to be buffered in the Salesforce component's Jetty client response buffer. [1] https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/async_api_headers_enable_pk_chunking.htm -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12620) CompletionAwareAggregationStrategy onCompletition method null exchange.
[
https://issues.apache.org/jira/browse/CAMEL-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613780#comment-16613780
]
Viral Gohel commented on CAMEL-12620:
-
Hi [~luismospinam], Do you have a reproducer application which you can attach ?
It will be helpful to narrow down the issue and investigate.
> CompletionAwareAggregationStrategy onCompletition method null exchange.
> ---
>
> Key: CAMEL-12620
> URL: https://issues.apache.org/jira/browse/CAMEL-12620
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Luis Miguel
>Priority: Major
>
> Hello.
>
> We have a camel project to process some Csv files, we created a class
> implementing "CompletionAwareAggregationStrategy" in order to aggregate each
> row processed and we override the methods "aggregate" and "onCompletion" from
> it.
> The way we process the Csv file is parallelized with the "parallelProcessing"
> and indicating an "executorService" with 8 concurrently threads.
>
> We are having a weird issue that rarely happens, and is that in the middle of
> the process of the file, the method "onCompletion" is being called (even when
> the file is not complete yet) and it sets the argument "Exchange" as NULL so
> the whole camel route is messed up.
> As I said this rarely happens when we try to reprocess the file the error is
> gone.
>
>
>
> Here's the main route that process the CSV file, notice that for the split
> process we create an instance of "CsvAggregationStrategy"
>
> {code:java}
> @Qualifier("executorServicePublicationItemCsv")
> @Autowired
> private ExecutorService executorService;
> @Override
> public void configure() throws Exception {
> String[] header = Arrays.stream(PublicationItemCsvFields.values())
> .map(PublicationItemCsvFields::getText).toArray(String[]::new);
> Map csvFieldsByEntityAttribute = new HashMap<>();
> mapFields(csvFieldsByEntityAttribute);
> //@formatter:off
> from("file:publicationItemData?delete={{routes.push-csv-to-service.delete-source-file}}")
> .streamCaching()
> .routeId("push-publication-item-csv-to-service")
> .onException(Exception.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error in publication item route, sending an email:
> ${exception.message} ${exception.stacktrace}")
> .to("direct:sendImportErrorReport")
> .end()
> .log(LoggingLevel.INFO, "Beginning to import publication item CSV:
> ${file:onlyname}")
> .unmarshal(new CsvDataFormat()
> .setSkipHeaderRecord(true)
> .setNullString(EMPTY)
> .setLazyLoad(true))
> .split(body(), new CsvAggregationStrategy())
> .streaming()
> .parallelProcessing().executorService(executorService)
> .to("direct:publication-item-splitter")
> .end()
> .choice()
> .when(simple("${exchangeProperty.aggregationError} != null"))
> .log("An error occurred when aggregating exchanges, sending an email with the
> error.")
> .setProperty("original_body", body())
> .to("direct:sendAggregationErrorEmail")
> .setBody(exchangeProperty("original_body"))
> .end()
> .choice()
> .when(simple("${exchangeProperty.badCsvData.size()} > 0"))
> .setBody(simple("${exchangeProperty.badCsvData}"))
> .marshal(new CsvDataFormat().setHeader(header))
> .setProperty("badRowsBody").simple("${body}")
> .end()
> .choice()
> .when(simple("${exchangeProperty.successfulRecords.size()} > 0"))
> .setBody(simple("${exchangeProperty.successfulRecords}"))
> .marshal(new CsvDataFormat().setHeader(header))
> .setProperty("successfulRowsBody").simple("${body}")
> .end()
> .to("direct:sendImportReport").end()
> .log("Completed import for publication item CSV: '${file:onlyname}'");
> from("direct:publication-item-splitter")
> .streamCaching()
> .routeId("push-publication-item-splitter")
> .onException(PublicationItemImportException.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error importing publication item data:
> ${exception.message} ${exception.stacktrace}")
> .end()
> .onException(HttpHostConnectException.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error connecting to publication item service host:
> ${exception.host}. Request body: ${body}")
> .end()
> .onException(HttpOperationFailedException.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error received from publication item service: HTTP
> ${exception.statusCode}. Response body: ${exception.responseBody}. Request
> body: ${body}")
> .end()
> .onException(Exception.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error: ${exception.message}
> ${exception.stacktrace}")
> .end()
> .setProperty("csvRowData").simple("${body}", List.class)
> .setProperty("csvFieldsByEntityAttribute").constant(csvFieldsByEntityAttribute)
> .bean(publicationItemCSVDataHandler)
> .marshal().json(JsonLibrary.Jackson)
> .setHeader(HttpHeaders.AUTHORIZATION, simple("Basic
>
[jira] [Assigned] (CAMEL-12783) camel-spring-ws - Should support HeaderFilterStrategy
[ https://issues.apache.org/jira/browse/CAMEL-12783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viral Gohel reassigned CAMEL-12783: --- Assignee: Viral Gohel > camel-spring-ws - Should support HeaderFilterStrategy > - > > Key: CAMEL-12783 > URL: https://issues.apache.org/jira/browse/CAMEL-12783 > Project: Camel > Issue Type: New Feature > Components: camel-spring-ws >Reporter: Claus Ibsen >Assignee: Viral Gohel >Priority: Major > > We should add support for HeaderFilterStrategy like some of the other > components do, so you can more easily filter headers in request vs response > use-cases. > Asked on SO: > https://stackoverflow.com/questions/52188019/how-to-filter-http-headers-for-apache-camel-spring-ws-services -- This message was sent by Atlassian JIRA (v7.6.3#76005)
